Understanding software architecture, adaptability, risk assessment, and writing readable code.
There is a harmful myth that a developer’s job is solely about writing code in an endless eat-sleep-code-repeat cycle. In reality, typing out instructions accounts for no more than 40% of working hours on average. The remaining time is filled with tasks that have very little to do with actual “coding.”
Analyzing and refining requirements eats up to 25% of the time, while verification, testing, and debugging take another 30%. On top of that, there is planning and documentation, without which team insights evaporate into fleeting “tribal knowledge.” These stages are critical because gaps in analysis or a lack of testing introduce costs that cannot be fixed by fast coding or any LLM.
The most Lindy-proof aspects of our work are not elite proficiency in a specific programming language or framework, but rather a firm grasp of software architecture fundamentals, adaptability, risk assessment, and the ability to write code that others can easily understand. These competencies remain constant, regardless of current technology hype or the project management framework you operate in.
Unfamiliar with the Lindy Effect?
If you haven’t had a chance to explore it yet, take a look here:
[Medium: The Lindy Effect in IT](https://medium.com/@nejczew/who-or-what-exactly-is-this-lindy-69aafe46ce4d)
[Article: The Lindy Effect in IT](https://nejczew.com/en/articles/the-lindy-effect-in-it/)