this post was submitted on 01 Aug 2023
22 points (100.0% liked)

Programming

13389 readers
128 users here now

All things programming and coding related. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] t3rmit3@beehaw.org 7 points 1 year ago

My tip, "developer empowered" means that the buck stops with Engineering leadership when it comes to dev work. They have to be able to greenlight work, and also red-light it.

That gives engineers the flexibility to build what they see is missing, while still having executive leadership (e.g. "Director of Engineering" etc) in the loop who can rein in rabbithole-development projects.

But the second you allow "Product" teams to dictate dev work, you will lose that developer empowerment, and they will always just be "the ones who build what Product tells them to".