Thanks. The author touched something there, close to a truth (or deep belief I got ?) about our life, something about the journey mattering more than the destination...
In my opinion, having spent about a year and half working on various coding projects using AI, there are phases to the AI coding lifecycle.
1) Coding projects start out like infants: you need to write a lot of code by hand at first to set the right template and patterns you want the AI to follow going forward.
2) Coding projects continue to develop kind of like garden beds: you have to guide the structure and provide the right "nutrients" for the project, so that the AI can continue to add additional features based on what you have supplied to it.
3) Coding projects mature kind of like children growing up to become adults. A well configured AI agent, starting from a clean, structured code repo, might be mostly autonomous, but just like your adult kid might still need to phone home to Mom and Dad to ask for advice or help, you as the "parent" of the project are still going to be involved when the AI gets stuck and needs help.
Personally, while I can get some joy and satisfaction from manually typing lines of code, most of those lines of code are things I've typed literally hundreds of times over my decades long journey as a developer. There isn't as much joy in typing out the same things again and again, but there is joy in the longer term steering and shaping of a project so that it stays sane, clean, and scalable. I get a similar same sense of joy out of gently steering AI towards success in my projects, that I get from gently steering my own child towards success. There is something incredible about providing the right environment and the right pushes in the right direction, and then seeing something grow and develop mostly on it's own (but with your support backing it up).
Guess I will not be a good parent lol.
Engineering used to be my go-to to enter flow state. Now, I spend a few minutes thinking about what I want and then a lot of time babysitting Claude code -- similar to experiences here.
Has anyone found a way to make the "manager" part feel as engaging and creative as the "craftsman" part used to?
My impression is that artists are even more hostile than the most AI-skeptic of software engineers. In large part, this is likely because the economic argument doesn't hold much sway. For the large majority of artists, it's hard for them to make money with art as is, the bottleneck is not the volume of art they can produce. There's a much clearer path to turning "more code" into "more money", even if it's still not direct.
The industrial scale painting robots work well for painting cars coming off an assembly line, but not for landscapes nor portraits.
Automation (not just AI, but in general) works well for highly structured, repetitious work but not for creative expression.
I'm often accused of letting my skepticism hold me back from really trying it properly, and maybe that's true. I certainly could not imagine going months without writing any code, letting the AI just generate it while I prompt
My work is pushing these tools hard and it is taking a huge toll on me. I'm constantly hearing how life changing this is, but I cannot replicate it no matter what I do
I'm either just not "getting it", or I'm too much of a control freak, or everyone else is just better than I am, or something. It's been miserable. I feel like I'm either extremely unskilled or everyone else is gaslighting me, basically nowhere in between
I have not once had an LLM generate code that I could accept. Not one time! Every single time I try to use the LLM to speed me up, I get code I have to heavily modify to correct. Sometimes it won't even run!
The advice is to iterate, but that makes no sense to me! I would easily spend more time iterating with the LLM than just writing the code myself!
It's been extremely demoralizing. I've never been unhappier in my career. I don't know what to do, I feel I'm falling behind and being singled out
I probably need to change employers to get away from AI usage metrics at this point, but it feels like it's everyone everywhere guzzling the AI hype. It feels hopeless
The untrained temp workers using AI to do the entirety of their jobs aren't producing code of professional quality, it doesn't adhere to best practices or security unless you monitor that shit like a hawk but if you're still engineering for quality then AI is not the first train you've missed.
They will get code into production quicker and cheaper than you through brute force iteration. Nothing else matters. Best practices went the way of the rest of the social contract the instant feigned competence became cheaper.
Even my podunk employer has AI metrics. You won't escape it. AI will eventually gatekeep all expertise and the future employee becomes just a disposable meat interface (technician) running around doing whatever SHODAN tells them to.
Most of my experience has been similar to yours. But yesterday, out of the blue, it spit out a commit that I accepted almost verbatim (just added some line breaks and stuff). I was actually really surprised: not only it followed the existing codebase conventions and variable naming style, but also introduced a couple of patterns that I haven't thought of (and I liked).
But it also charged me $2 for the privilege :) (On a related note, Gemini API has become noticeably more expensive compared to, say, a month ago.)
I find that with Aider managing context (what files you add to it) can make all the difference.
My experience is in one of the areas that people are saying it is most helpful
Which really just adds to the gaslighting effect
But isn't prompting and iterating another way of instructing the computer to do what you want? Perhaps we could view it as a step up in the level of abstraction we work at.
We had similar arguments when high-level languages were introduced. Experienced programmers of that era maintained that they could write better programs in assembly language than in COBOL/FORTRAN/PL-I/Pascal etc. Yet even today we still need core portions of code written in assembler, but not much.
We are operating at the same level of abstraction, just with tools to generate high volumes of inconsistent quality of it for us
Edit: It would have to produce a lot higher quality a lot more consistently for me to seriously consider moving up to the "LLM prompt" abstraction layer permanently. As it is I think I'm just better off writing the code myself
This could be cope but I don't think it is.
I don't think this is it, personally.
The quality of LLM code is consistently average at best, and usually quite bad imo. People say it is like a junior, but if a junior I hired produced such code consistently and never improved I would be recommending the company PIP them out.
Having output like a Junior would be fine, if I didn't have to fix it myself. As it stands, I've never been able to get it to produce code of the quality I want so I have to spend more time fixing it than I would just writing it.
I dunno. It sucks man
I've been pretty deeply into LLMs myself since 2023 and built several small models myself from scratch and (SFT) trained many more so it's not like I'm ignorant of how it works, I'm just not getting the workflow results.
I think I blacked out when my brain tried to process this phrase.
Nothing personal, but I automatically discount all claims like this (something something require extraordinary evidence and all that…).
I couldn't even get Zed hooked up to GitHub Copilot. I use ChatGPT for snippets and search and it's okay but I don't want to bother checking its work on a large scale
I'm guessing you don't care about quality very much, since you are focusing on your output volume
What a weird alternate universe it is that I live in. My managers are somewhat skeptical of AI workflows and keep throwing up roadblocks to deeper and more coordinated use among my colleagues. Probably because there is so much churn, and it’s difficult to replicate the practice from one engineer to another. Some of my colleagues are very resistant to using AI. I use it quite extensively, but rate limits mean that there are occasions when I must pick up where the machine leaves off.
But at least I can now ship (shitty) code a lot faster.
But to get there it might be a good move to code for yourself (and read books).
Then on the other hand coding will not be a fun job anymore...
You mean have a handheld device with a button they can press, which would instantly generate a painting of what it was pointed at?
Agreed, that could never be art.
