Why I don't use AI for just the easy things

Brett, a software developer, chooses to stop using AI for coding due to its negative emotional impact, ethical concerns, and the belief that relying on AI undermines deep learning and craftsmanship in software development. He advocates for a human-centered, environmentally conscious approach that values quality, understanding, and collaboration over speed and convenience, reaffirming his commitment to coding without AI despite industry trends.

Brett, a software developer, shares his decision to stop using AI for coding at work after 18 months of reliance on it. He explains that this choice was driven by negative emotional effects and a desire to regain enjoyment and satisfaction in his work. Since quitting AI-assisted coding, he feels happier and more engaged, emphasizing that happy engineers produce better quality work. Brett also highlights that his decision is ethical, considering the broader environmental, economic, and emotional costs of AI technology, comparing it to his long-term commitment to veganism as a moral stance.

He addresses common suggestions to use AI only for tedious or boilerplate coding tasks, explaining why he rejects even limited use. Brett argues that tedious parts of programming encourage deeper understanding and better code quality, as they motivate developers to solve underlying problems and improve code structure. He worries that relying on AI for these tasks fosters laziness and diminishes the craft of software engineering. Additionally, he expresses concern that AI shortcuts the learning process, preventing developers from gaining a thorough understanding by simply providing ready-made answers.

Brett also discusses the use of AI as a learning tool, acknowledging that some find it helpful for personalized assistance, especially when traditional learning resources or community support are lacking. However, he remains skeptical, believing that true learning requires grappling with problems and understanding solutions deeply, which AI may undermine. He values traditional methods like reading documentation and source code, which foster a more profound grasp of programming concepts and skills.

Drawing from his experience in game development, Brett shares how the negative reception of AI-generated art and code in that community influenced his perspective. He notes that many creative professionals strongly oppose AI due to concerns about intellectual property and the devaluation of human creativity. He also points to local resistance against data centers supporting AI infrastructure, highlighting the environmental and social costs of AI expansion. These insights reinforce his ethical stance against using AI in his work, despite uncertainties about his career future.

Finally, Brett responds to views that AI empowers rapid prototyping and iteration, arguing that such capabilities existed long before AI. He stresses the importance of human collaboration and thoughtful design processes over speed and quantity of output. Brett advocates for a humanist and environmentally conscious approach to technology, prioritizing quality, sustainability, and care for people over maximizing efficiency or profit. He concludes by reaffirming his commitment to coding without AI, feeling confident in his decision and hopeful about sharing his journey with others.