One of my greatest frustrations is watching developers try to implement "requirements" that make no sense or are technically flawed.

Dev: "I want to do X".
Me: "X is impossible, but you can achieve your goal with Y."
Dev: "I can't; my requirement is to do X".

· · Web · 1 · 0 · 0

Leadership should empower their engineers to bring their expertise to bear as part of a conversation about how to build their systems.

One-way flows of information tend to produce silos that are inimical to good, well-rounded, and effective output.

I'm proud that my organization and my team do really well at this. But it's sad to see people having a tough time in settings where those conversations don't happen, and I shudder to think of the software that comes out of it.

Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!