Programming

17303 readers

73 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Software Engineer vs Software Developer (programming.dev)

submitted 11 months ago* (last edited 11 months ago) by fogetaboutit@programming.dev to c/programming@programming.dev

53 comments fedilink hide all child comments

In your opinion what's the difference between the two? In my opinion both terms are frequently used interchangeably in the workplace.

But I'd like to consider myself as an engineer, because although I don't consider myself to be good at it, I think I cares about the software that I worked on, its interaction with other services, the big picture, and different kinds of small optimizations.

I mean, what is even engineering?

you are viewing a single comment's thread
view the rest of the comments

[–] ShrimpsIsBugs@programming.dev 4 points 11 months ago (1 children)

As a former civil engineer who now works in software, "software engineer" irks me. "Engineer" means you're supposed to be licensed

This really depends on the country you live in. In some countries you need a license, some need you to have some kind of university degree and others don't care at all. So we cannot really use that measure as a definition.

[–] lysdexic@programming.dev 3 points 11 months ago (1 children)

This really depends on the country you live in.

Not really. There are two aspects to this problem: one is how people assign arbitrary and meaningless titles to themselves, and another is regulatory requirements by jurisdictions to be able to legally assume a role.

I can call myself senior dubstep engineer, and that's perfectly fine. I can't call myself a civil engineer and sign off on a construction project or a permit. No one cares if I'm actually a senior dubstep engineer or if I'm junior at best. In the meantime, you will get in trouble if you try to sign off on a construction project, no matter of how stubborn you are with regards to calling yourself an engineer.

[–] ShrimpsIsBugs@programming.dev 1 points 11 months ago (1 children)

another is regulatory requirements by jurisdictions to be able to legally assume a role.

This is exactly what I mean with "this depends on the country you live in". Different countries have vastly different regulatory requirements. Taking UK as an example, you can call yourself civil engineer all day long without having to worry any legal consequences because there simply is no such thing as a licensing system for engineers.

[–] lysdexic@programming.dev 1 points 11 months ago (1 children)

Taking UK as an example, you can call yourself civil engineer all day long without having to worry any legal consequences because there simply is no such thing as a licensing system for engineers.

Britain's Engineering Council disagrees.

https://www.engc.org.uk/international-activity/access-to-practise-in-the-uk/

[–] ShrimpsIsBugs@programming.dev 1 points 11 months ago

Well idk the details in that specific case, this was just the first example I found. My point is, that different countries, states and institutions disagree on this matter. There is no universal rule that defines what you need to have achieved to call yourself an engineer.