Reasons to dislike AI coding | Structure and Interpretation of Computer Programmers  (https://gmpg.org/xfn/11)  (../../../wp-content/themes/twentyten/style.css@ver=20260819.css)  (https://www.sicpers.info/xmlrpc.php)  (https://www.sicpers.info/)  (Structure and Interpretation of Computer Programmers » Feed) (https://www.sicpers.info/feed/)  (Structure and Interpretation of Computer Programmers » Comments Feed) (https://www.sicpers.info/comments/feed/)  (Structure and Interpretation of Computer Programmers » Reasons to dislike AI coding Comments Feed) (https://www.sicpers.info/2026/10/reasons-to-dislike-ai-coding/feed/)  (oEmbed (JSON)) (https://www.sicpers.info/wp-json/oembed/1.0/embed?url=https%3A%2F%2Fwww.sicpers.info%2F2026%2F10%2Freasons-to-dislike-ai-coding%2F)  (oEmbed (XML)) (https://www.sicpers.info/wp-json/oembed/1.0/embed?url=https%3A%2F%2Fwww.sicpers.info%2F2026%2F10%2Freasons-to-dislike-ai-coding%2F&format=xml)  (../../../wp-content/themes/twentyten/blocks.css@ver=20250220.css)  (https://www.sicpers.info/wp-json/)  (JSON) (https://www.sicpers.info/wp-json/wp/v2/posts/3535)  (RSD) (https://www.sicpers.info/xmlrpc.php?rsd)    (index.html)  (https://www.sicpers.info/?p=3535)   (Podcast RSS feed) (https://www.sicpers.info/feed/podcast)   (https://fosstodon.org/@leeg)  (ActivityPub (JSON)) (https://www.sicpers.info/?p=3535)  (../../../wp-content/uploads/2026/08/cropped-sicpers_logo_precision-32x32.jpg)  (../../../wp-content/uploads/2026/08/cropped-sicpers_logo_precision-192x192.jpg)  (https://www.sicpers.info/wp-content/uploads/2026/08/cropped-sicpers_logo_precision-180x180.jpg)    (index.html#content) Skip to content (https://www.sicpers.info/) Structure and Interpretation of Computer Programmers   Writing code is hard. Software engineering is much harder. (Structure and Interpretation of Computer Programmers)   (https://www.sicpers.info/) Home  (https://www.sicpers.info/blog/) Blog  (https://www.sicpers.info/contact/) Contact  (https://www.sicpers.info/archives/) Post Archives  (https://www.sicpers.info/privacy-statement/) Privacy Statement  (https://www.sicpers.info/agency/) Software Craftsmanship’s Consulting Detective: Fixing Complex Systems.  (https://www.sicpers.info/software-portfolio/) Software Portfolio       (https://www.sicpers.info/2026/09/ai-adoption-engineering-process-and-documentation-consultancy/) ← AI adoption, engineering process, and documentation consultancy    Reasons to dislike AI coding Posted on (index.html) (15:12) 2026-10-06  by (https://www.sicpers.info/author/admin/) (View all posts by Graham) Graham   Code as Art I covered this before in (https://www.sicpers.info/2026/03/art-or-tool/) Art or tool? If you think of software as artistic output then generated software isn’t real because it doesn’t have the creative ineffability that’s a sign of true art. There’s no argument against this one except that the people who want software typically aren’t paying for artworks, they’re paying for outcomes. And the outcomes of using a given artefact are the same regardless of how the artefact is made. That also means there’s no argument for this one, unless you accept as axiomatic the ideas that things that can be considered art should only be made by people, and that using this particular set of tools is too big a separation between the person and the work when no other historical set of tools was too big a separation between the person and the work. AI as Employment Thief I covered this one before too, in (https://www.sicpers.info/2026/03/on-working-machines/) On working machines . If you think of typing in code as the thing you get paid for, and the employers now have access to a machine that can do the typing, then the machine “stole your jobs”. Except that the job was never to type code, it was to deliver valuable software. People who can still do that can still get paid by organisations that need that to be done. And, as I said in the linked post, demand only increases as application becomes more efficient. Humans as Meat Proxies If you think that software creation is an interpersonal endeavour, then taking task descriptions generated by software and turning them into prompts that the software uses to generate more software is a dehumanising experience. This has been the trajectory of society for centuries. Here’s a quote from the (https://thenewobjectivity.com/pdf/marx.pdf) Fragment on Machines : …once adopted into the production process of capital, the means of labour passes through different metamorphoses, whose culmination is the machine,  or rather, an automatic system of machinery  (system of machinery: the automatic  one is merely its most complete, most adequate form, and alone transforms machinery into a system), set in motion by an automaton, a moving power that moves itself; this automaton consisting of numerous mechanical and intellectual organs, so that the workers themselves are cast merely as its conscious linkages. […] The accumulation of knowledge and of skill, of the general productive forces of the social brain, is thus absorbed into capital, as opposed to labour, and hence appears as an attribute of capital, and more specifically of fixed capital,  in so far as it enters into the production process as a means of production proper.  This passage, written by Karl Marx in about 1857-1858, shows that both mechanical and intellectual work was always intended to be replaced by machinery (in predicting the alienation of intellectual work, Marx probably relied on his knowledge of contemporary mathematician Charles Babbage). In this situation it isn’t the technology that takes the job, it’s the mode of production. And given that programming is intellectual work, the means of production is literally our heads, we ought to be able to seize those. Software Engineering as Rules Motivated by Bertrand Meyer’s (https://www.ai-for-smarties.com) AI for Smarties , if you believe that software engineering is the careful application of the mysterious knowledge of software engineers, encapsulated in rules like the SOLID principles, “prefer composition over inheritance”, “(https://www.destroyallsoftware.com/talks/useing-youre-types-good) use you’re type’s good “, the Law of Demeter and so on, then AI can’t possibly write software because it doesn’t apply those rules, it just generates text that happens to compile. Never mind that much of the history of computing involves people taking an empiricist approach to software: copying it from Stack Overflow and tweaking it until it works; writing it out from a listing in Numerical Recipes or Sinclair User and tweaking it until it works; writing macros to automate the copying phase, and so on. AI Companies as Bad Actors If you believe that the big AI companies is run by people who don’t have humanity’s best interests at heart (further reading: all the Karl Marx writings I didn’t already quote above), then AI coding is bad because it supports those companies. As long as you don’t allow for the creation of other companies, the use of non-corporate models like academic or community models, and so on.  ()   About Graham  I make it faster and easier for you to create high-quality code. (https://www.sicpers.info/author/admin/) View all posts by Graham →     This entry was posted in (https://www.sicpers.info/category/ai/) AI . Bookmark the (index.html) (Permalink to Reasons to dislike AI coding) permalink .   (https://www.sicpers.info/2026/09/ai-adoption-engineering-process-and-documentation-consultancy/) ← AI adoption, engineering process, and documentation consultancy    Leave a Reply Your email address will not be published. Required fields are marked *   Comment *    Name *  ()   Email *  ()   Website ()   (Post Comment)  (3535)  (0)   (a38a8d5eb8)   Δ  (13)     This site uses Akismet to reduce spam. (https://akismet.com/privacy/) Learn how your comment data is processed.     (https://patreon.com/chironcodex) (The Chiron Codex logo: a centaur holding a book and a tablet computer.)   Chiron Codex: helping software engineers become centaurs.   OOP the Easy Way (https://leanpub.com/ooptheeasyway) Object-Oriented Programming the Easy Way : a manifesto for reclaiming OOP from three decades of confusion and needless complexity.  APPropriate Behaviour The book about all the things software writers do that aren't writing software. (http://leanpub.com/appropriatebehaviour)     APPosite Concerns (https://leanpub.com/appositeconcerns) A collection of essays on being a programmer, on doing programming, and on thinking about programmers.       (https://www.sicpers.info/) Structure and Interpretation of Computer Programmers   (https://wordpress.org/) (Semantic Personal Publishing Platform) Proudly powered by WordPress.