>>11487789It depends. There's a difference between plain old software development and software engineering. If you're writing basic code to handle boilerplate databases and making websites, then no you're not an engineer. If you're doing backend, embedded, cryptosystems, HPC, scientific computing, numerical methods, compression, etc, etc. then it's clear to anyone there are longstanding standards (i mean read anything in the IEEE specifications to see), best practices and judicious use of traditional techniques hailing from blackboxing, etc., actual rigor involved, and so on. It's hard to say these jobs aren't engineering - the only basis one has is to see that not everyone in these fields has a degree that has engineering in the title.
>aren't engineersMost EE's don't have their PE while civil's do. The actual professional engineering license is relevant to public safety work, not whether you're a 'real' engineer. Loads of actually useful shit came out of engineering that wasn't concerned with accreditation
>Computer Science degrees without accreditationI have nothing to say about codemonkeying degrees in the average to worse-than-average universties. But at top universities, ie top 25ish, you'll find that it's either CS degrees are taught in the same tradition as math and physics, that is less about labs and practicum and more about core principles and laying down the foundations for further study (which systems classes inbetween and applied classes that are hot in industry right now), or they're CSE / EECS programs. If we're actually comparing software engineering jobs worth a damn, you'll find they're a mix of CS, EE, EECS, CSE, CE, math, physics, etc. majors who did well in interviews and were trained how to engineer on the job, and most of them came from top 50 schools in their subject. Your degree isn't as important as the direction of your career, whether that's academic or in the industry.
