this post was submitted on 29 Nov 2024
121 points (80.4% liked)

Technology

59772 readers
3191 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] TheRagingGeek@lemmy.world 5 points 4 days ago (1 children)

Seems to be a trend, my boss was telling me that the VP's in our org think we need more lead devs and less solutions architects, though they would functionally be doing largely the same role, meetings, planning, design, interfacing with teams they are dependent on, annual technology reviews etc. I think it's going to bite them in the end

[–] sugar_in_your_tea@sh.itjust.works 3 points 4 days ago (1 children)

I imagine hiring will be an issue. Devs want to dev, and naming an architect role a "dev" role doesn't communicate the role properly.

[–] TheRagingGeek@lemmy.world 3 points 4 days ago

Yep, they talked about it a bit during my hiring what I wanted my title to be since they are paid the same and do the same tasks(in addition to some coding expectations). I'm glad I chose architect, but ultimately they squeezed me out of that with RTO mandates for architects and above.