this post was submitted on 01 Sep 2023
338 points (96.2% liked)
Programming
17492 readers
113 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I just put "software engineer", or "senior programmer". It's all the same to me.
Software Architect is an altogether different thing, although in my career I've had to do a bit of it, it was never a principal task. And these days that job is often driven by "Tech Director" or "Tech Lead" or the 20 other titles that don't mean that much.
After 15 years as a "Programmer", I've done architecture, design, programming, debugging (so much debugging), instrumentation and iteration, integration, build management, team management, and lead/director tasks. Don't care what my title is, just pay me what I'm worth, and let me code.