Feeling Sad about AI

TEXT START: This video doesn't contain any code: feel free to skip it if you like, but either way I'm going to try to keep it short, so see you on the other side :-).

The Dissection

This is a grief-management essay disguised as labor-market reassurance. The author correctly identifies the wound: AI is not merely threatening a paycheck; it is attacking programming as proof of intelligence, craft, usefulness, and deserving respect.

The proposed remedy separates three domains: private meaning, hobbyist continuity, and career value. The first two are defensible. The third is asserted, not demonstrated.

The Core Fallacy

The text confuses society still needing code with society still needing large numbers of human programmers. Those are not the same. Under P1, AI can increase code output and system complexity while reducing the labor required to produce, debug, document, and maintain it. Demand for the product can rise while demand for its human producers collapses.

The compiler analogy fails at scale. Compilers preserved narrow expert niches while eliminating or abstracting away entire categories of labor. The existence of compiler engineers proves only that specialists survive; it does not preserve programming as a broad career ladder.

Systems thinking may remain cognitively valuable while becoming economically cheap. Useful is not equivalent to scarce, and employable is not guaranteed by intellectual merit. The article’s most honest claim is that employers want to replace programmers with an imitation. It then tries to neutralize that fact psychologically.

Hidden Assumptions

• Code demand will expand fast enough to offset AI’s labor efficiency.
• Human understanding will remain a bottleneck rather than a layer AI increasingly absorbs.
• Employers will keep paying for human comprehension when verification and delegation are automated.
• Technical depth will create bargaining power instead of becoming a premium skill controlled by a small ownership class.
• Universities can train students for a stable programming career decades out.
• Surviving specialist roles will be numerous enough to support today’s aspiring programmers.
• Personal value can be separated from market value without the loss of income and status damaging people’s lives.

Social Function

Primary classification: partial truth, ideological anesthetic, and transition management.

The text gives threatened programmers a way to retain dignity by relocating value from employment to intrinsic love. It also encourages learners to keep investing in programming. That may be psychologically humane, but it individualizes a structural rupture: if the career promise fails, the learner is left with the claim that the knowledge was useful while the labor market has already discarded its bargaining power.

This is not straightforward propaganda. The author’s grief is sincere, and sincerity matters personally. It does not alter the text’s social function: helping people metabolize obsolescence without confronting the possibility that mass programming becomes a thin labor layer around AI capital.

The Verdict

The article is right that the labor market cannot confiscate a person’s love of programming. It is wrong to turn that private permanence into evidence of public employability. Coding may survive as a hobby, cultural practice, elite specialty, and substrate of AI systems while programming as a mass route to income and status collapses.

This is a humane lullaby at the bedside of a profession losing its bargaining power. It protects identity; it does not defeat P1, P2, or P3. The career reassurance is not a survival plan. It is hope attached to a niche.