Requirements volatility is the core problem of software engineering
“Start by accepting that change is inevitable. (…) As a consequence of this, software is never finished, only abandoned. (…) This means that no software product is ever exactly, perfectly satisfactory.”
- from
- Engineering Team Management
- added
- 2026-10-10
- likes
- 0
similar
-
The art of destroying software youtube.com
Greg Young described a good way to deal with requirements volatility: optimize from the beginning to be able to delete your code, and structure your code so that any part of it is no bigger than 1 week's worth of coding. So that any part can be re-written in 1 week.
-
-
Avoiding burnout as an ambitious developer stackoverflow.blog
“Be willing to say no; Know what you don't want; Use your energy level realistically; Be kind to your future self”.
-
Developers can't fix bad management iism.org
“Why do so many software projects fail? Software development is much closer to creating a new factory than running an existing factory. (…) Software development is made up of many unknown duration tasks, this fundamentally unpredictable nature makes traditional management's…
-
The product roadmap is dead: welcome to the age of problem roadmaps medium.com
“Fall in love with your problems and not with your solutions.”
-
sacrificial lamb product x.com
a massive unpopular re-architecture required to pave the way for future innovative release. That's the cautionary tale of why you should be ready for intense criticism and adversity, if by chance or fate your wander down the path of monumental changes in a business software.
Engineering Team Management › Project Management > Specifications: ““Start by accepting that change is inevitable. (…) As a consequence of this, software is never finished, only abandoned. (…) This means that no software product is ever exactly, perfectly satisfactory.””