Unable to load image

Calling Yourself an Engineer :marseynerd2:: r/cscareerquestions

https://old.reddit.com/r/cscareerquestions/comments/12mz8b1/calling_yourself_an_engineer

boot campers are not engineers [-2]

:marseylaugh:

Eh, as long as you have a BS in it you're a Computer Scientist imo. Understanding everything from circuits, hardware, Networking and the electrical properties involved in computing is very technical stuff which gets taught to you. Then you add programming, languages, OSses and there is a ton of knowledge specific to the field that separates you from the layman or even casual learner.

Then you get into Data structures, algorithms, calculus, discrete etc. Some specialties go a bit further into other disciplines like physics and various other classical sciences

Ah yes, the barrier to being a scientist is knowing first year calculus and what a hashmap is :marseyrick:

"Software Engineer" is a very common title. I would not call myself just 'engineer' without the 'software' prefix because 'engineer' by itself is just pretty meaningless.

“engineer” by itself means Mechanical/Chemical/Civil/etc in my opinion. Calling yourself an engineer as a software person is a bit much. [-80]

Thank you! Some devs are acting like their code review is the same as the process and responsability that in building a bridge. [-1]

:marseythebuilder:

Software engineer is a valid title and if you‘re working in a company where the only type of engineer that exists is a software engineer, then it makes sense to leave out the “software”. [... the entire post was too long :marseylongpost:]

heckin' valid title

and there's way more threads of :marseynouautism: arguing if they aren't engineers then why are their titles at work software engineer :marseyshapiro:

40
Jump in the discussion.

No email address required.

Eh, as long as you have a BS in it you're a Computer Scientist imo. Understanding everything from circuits, hardware, Networking and the electrical properties involved in computing is very technical stuff which gets taught to you

lol, I don't know a single dev who can actually explain all this shit.

This isn't the 80s anymore.

Jump in the discussion.

No email address required.

I learned all of it but I only remember a small portion of it because I never need to really use any knowledge of circuits, low level language, or networking outside of stuff like http codes.


https://i.postimg.cc/dVgyQgj2/image.png https://i.postimg.cc/d3Whbf0T/image.png

Jump in the discussion.

No email address required.

some of the embedded nerds probably

Jump in the discussion.

No email address required.

nah, they're even more r-slurred than the web dev. trust me on that

Jump in the discussion.

No email address required.

They teach it in CS degrees but I don't think many people remember it for long. We did building a simple processor out of NAND gates (showing how you'd implement a... I forget the name, binary results table thing, using a whole boatload of NAND gates), both physically using ICs and then scaling up using circuit simulation. Then we did very very basic CPU architecture, I think it was the Z80, then onto Z80 assembly.

Was the most interesting part of the course tbh

I'd still never call myself a 'software engineer' if I'd gone into programming. Programmer/Developer is fine. 'SWE' is hideously pretentious. Why do Americans love to abuse the title Engineer so badly? It's meant to really mean something.

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.