Developer-Business Divide

Most the time the only thing devs are allowed to interact with on the business side is a product/feature proposal with all assumptions already made.If devs do not know the customers/users nor interact with them then they can't really argue about the proposal's assumptions, it defacto becomes a demand.With experience devs see such proposals with skepticism. A significant amount of our output ends up being useless, no matter how fast or well it was built.If you want de

Why would a business want to prioritize the experience of its developers over its users?

in my experience many developers want to be bricklayers (not to discount bricklaying, there's an art to it, but they're focused on the individual bricks, not the other aspects of the building). They get annoyed when they're asked to think about the bigger picture and just want to focus on the code, the architecture, and whatever is new and shiny. It is largely due to these sorts of developers that we've developed all the ritual around sprints/product owners/etc to p

Because it empowers developers instead of salespeople?

Most developers care. Most product managers don’t.

My largest frustration with technology and specifically software developers is that they don't exist to code but most in the field seem to forget that simple fact.They exist to solve real world problems for people, using software as a tool. I don't know how anyone can possibly do that even if they don't actively engage their user base and proactively solve workflow issues the end-users may not even know are technically possible.Very frustrating to watch entire teams spend y

It's a typical developer vs business mindset. They rarely sit on the same page for a good reason.

I too met many such developers.Very often some tech lead or head of could spot them and put them on tasks where they could be autonomous (generally technical but important aspects that bogs down several teams or products: pipelines, tooling, api design, performance, etc).Some could also be involved in features involving business logic but the lead/PM would make sure to put more details or streamline any feedback/questions through jira.Also, there's even more developers ou

the real problem is the design team doesn't give two shits about neither users nor developers of the product... developers aren't treated as customers by design teams and then everybody is confused why the thing doesn't work. (hint: maybe it's stupid hard to make it work if you are actively prevented to be able to work on it?)

Developers are terrible at writing software that solve business problems. Developers are better at writing software the solves problems for other developers