I've been calling myself a programmer. That's mostly what I do anyways
this post was submitted on 22 Nov 2023
47 points (89.8% liked)
Programming
17406 readers
111 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
I don't wanna add anything here. You are correct on the idea you already have. Keep going ๐
I typically tell people that engineering is applying physics. If you aren't directly interacting with the physical world, you are most likely a developer.
Working on an app, no matter how complex (or unessarily convoluted) generally makes you a developer. If you aren't thinking about impact of clock cycles, actuation/hardware interfaces or sensing, there is a high chance that the work you do has little to no risk or a chance of failure that is governed by the physical world. As said in other comments, engineers design and sign off on things. There is an implication that there is an unknown constraint, unlike a fully observable software environment.
load more comments
(6 replies)