![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
vit_r[********] introduction (draft)
I have written source code in different programming languages more than twenty years and I have dug different kinds of source code which had lived twenty years in production. My experience shows that there are language paradigms and coding styles that help to understand what the code does and there are language paradigms and coding styles that help to understand what the code does wrong.
The difference is in one word but it changes everything. It determines if the code will please management and then be disposed off or if the code will be strong enough to survive decades of error free work and many adjustments.
It seems, this is the main pitfall of functional programming and Agile church.
Maybe the source of problems is that software developers learn new concepts and new languages and afterwards try to live in real world with the things that are optimized for education purposes and short explanations. Most programmers and almost all books favor the first goal: if you (think you have) understand it, the work is done.
Modern git-culture is an one-day show. Everything is written to boast about creativity and disappear in cycles of permanent changes.
I have written source code in different programming languages more than twenty years and I have dug different kinds of source code which had lived twenty years in production. My experience shows that there are language paradigms and coding styles that help to understand what the code does and there are language paradigms and coding styles that help to understand what the code does wrong.
The difference is in one word but it changes everything. It determines if the code will please management and then be disposed off or if the code will be strong enough to survive decades of error free work and many adjustments.
It seems, this is the main pitfall of functional programming and Agile church.
Maybe the source of problems is that software developers learn new concepts and new languages and afterwards try to live in real world with the things that are optimized for education purposes and short explanations. Most programmers and almost all books favor the first goal: if you (think you have) understand it, the work is done.
Modern git-culture is an one-day show. Everything is written to boast about creativity and disappear in cycles of permanent changes.
