Pretty much all software projects seem to peak, and then decline in quality. There are only a handful of senior devs in the world who are actually good programmers.
Pretty much all software projects seem to peak, and then decline in quality. There are only a handful of senior devs in the world who are actually good programmers.
> Through our software pursuits, the mechanistic myth has spread beyond its academic origins, and is now affecting every aspect of human existence. In just one generation, it has expanded from worthless theories of mind and society (behaviour- ism, structuralism, universal grammar, etc.) to worthless concepts in the field of programming (structured programming, object-oriented pro- gramming, the relational database model, etc.) to worthless software-related activities that we all have to perform.
> What is worse, our mechanistic beliefs have permitted powerful software elites to arise. While appearing to help us enjoy the benefits of software, the elites are in fact preventing us from creating and using software effectively. By invoking mechanistic software principles, they are fostering ignorance in software-related matters and inducing dependence on their systems.
> Increasingly, in one occupation after another, all we need to know is how to operate some software systems that are based on mechanistic principles. But our minds are capable of non- mechanistic knowledge. So, when the elites force us to depend on their software, they exploit us in two ways: by preventing us from creating better, non-mechanistic software; and by preventing us from using the superior, non-mechanistic capabilities of our minds.
> The ultimate consequence of our mechanistic culture, then, is the degradation of minds. If we restrict ourselves to mechanistic performance, our non-mechanistic capabilities remain un- developed. The world is becoming more and more complex, yet we see only its simple, mechanistic aspects. So we cope perhaps with the mechanistic problems, but the complex, non-mechanistic ones remain unsolved, and may eventually destroy us.
Wow, I'm immediately hooked. The book is free online as well to download.
I wonder if he would go on Lex or something.
2 devs on teach team were truly 10x before AI; each has 15-25 yrs of exp on very small teams, great at so many things: code - infra - linux internals - networking - incredible debugging skills - keep up with good practices - great docs - and desire to do things the "right way" - IQ + horsepower.
The other good senior devs may do some of those things.
My title is Senior 2 b/c I negotiated a raise during interview, but am mid-level at best. Now laid off.