this post was submitted on 22 Nov 2023
47 points (89.8% liked)

Programming

17031 readers
394 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

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
47
Software Engineer vs Software Developer (programming.dev)
submitted 10 months ago* (last edited 10 months ago) by fogetaboutit@programming.dev to c/programming@programming.dev
64 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
[–] elias_griffin@lemmy.world 2 points 10 months ago* (last edited 10 months ago)

Maybe, postulating, as I consider myself an Engineer and not a Developer.

Tangentially related: https://comeriohomes.com/the-difference-between-a-developer-and-a-home-builder-2/

Brainstorm thoughts dated just now

I guess it's in the conveyance of the word? Engineer seems like fitting a puzzle piece. Creating Software in a vast eco-system of language, OS, Frameworks, Platforms, Networks, and views it's progression in time. For instance planned obsolescence, graceful failure in the "pipeline of things", tolerates network topology changes, etc.

Maybe Engineers build with well designed, graphed/drawn, and planned strategy of the components in interaction with all other systems, including OS failings, local Network failing, Internet failing, Management Failings (workplace), on and on. The more things you can account for the more brilliant an Engineer you are.

Software Developer seems more linear. You take an idea and start with a good program. Then it's built up and up until it becomes a great piece of Software.