Re:Requirements volatility is the core problem of software e...
by ausimian on Saturday February 22, 2020 @07:18AM
(#22390630)
Nicely put. In my nearly three decades of software development, the most successful of my various colleagues have been the ones motivated by understanding the problem and its wider context, rather than the tech/process/language _de jour_.
This is a multiplier because it allows them to detect and ignore non-problems and work on problems whose solutions _will_ deliver value.
The problem with missing business requirements are that developers often are either to focused on writing the code instead of actually understanding the business.
You cannot build something you do not understand.
Understand small and expand your understanding. Code is not the goal, it never is. It's a means to a goal.
Another thing about software is, that a lot of it should never ever be written. It's the last thing you do, is write code for overcoming a challenge, because rarely you really need it.