I think it depends

Publicado às 30/10/2026 12:33 • #ai #claude #llm #programming

(Originally posted in /r/admincraft)

I've been using Claude Code since December 2025, and I have worked in software development since 2014, which, funningly enough, I started learning programming because I wanted to write Bukkit plugins (and 12 years later... I'm still writing Bukkit plugins).

LLMs are VERY useful for software development, especially for research. Letting an agent (like Claude Code or Codex) write a project for you DOES WORK, however the code is... not great. Yes, you CAN review the code and tell it to fix the issues, but in my experience sometimes you can only feel that the code is bad when you are deep into the weeds.

It is also a trap, because you can make projects in areas that you don't know about and it will make you feel like you are understanding it, like creating a game with LWJGL when you don't know OpenGL. Because you don't know OpenGL you don't know if Claude is doing the right thing, so you don't know if you should push Claude back or not because you don't have the necessary knowledge. So it becomes a snowball where you start offloading everything to Claude because you don't know how it works. And when the model starts spinning their wheels in the mud not knowing how to fix a specific issue, and you don't know how to fix the issue because you don't have the knowledge, what will you do? You end up trading speed for knowledge, and how far can you go without the knowledge? And yes, this has happened to me even with State of The Art™ models.

Even some basic things Claude still gets wrong, for example: Claude really loves using legacy color codes (§) instead of using the Adventure API, and if you never worked with the Paper API you wouldn't know to push back Claude.

I feel like you only understand the problem in depth when you are actually coding hands on. Claude may do a solution, but you aren't sure if that's the best solution or not because you didn't code it, so you haven't iterated on the problem to "brainstorm" what works and what doesn't.

I did experiments with trying to build something with "agentic engineering" (only reviewing Claude's output, intervening and writing code manually only when needed) and trying to use Claude only for research purposes or to do mundane things while forcing me to write the bulk of the code. The project that I was more hands on I learned way more than from what I was able to do while doing it the "agentic engineering" way, and with that newly acquired knowledge I forwarded it to the original project to improve and rewrite and prettify and make it actually GOOD (and there's a lot of other things that can be improved!)

However, if you are working in a area that you already have the knowledge in, using LLMs can speed up your project. Which is why I think agents work pretty well on non-greenfield projects, because you already have a "framework" of how you work, and Claude ends up mimicking the code you already wrote for the new features/bug fixes that it is writing and, because you already have the knowledge, you can glance at the generated code to know if it is correct or not instead of needing to "reverse engineer" what Claude wrote to understand the code.

I don't know what the future holds, maybe in the future we'll not need to read any code whatsoever (contrary to what some people say on Twitter where they don't even read the code anymore, I still think that it is pretty useful to read and understand what you are doing), but at that point software engineering will be truly dead.