←back to thread

Nobody knows how to build with AI yet

(worksonmymachine.substack.com)
526 points Stwerner | 2 comments | | HN request time: 0.436s | source
Show context
lordnacho ◴[] No.44616832[source]
I'm loving the new programming. I don't know where it goes either, but I like it for now.

I'm actually producing code right this moment, where I would normally just relax and do something else. Instead, I'm relaxing and coding.

It's great for a senior guy who has been in the business for a long time. Most of my edits nowadays are tedious. If I look at the code and decide I used the wrong pattern originally, I have to change a bunch of things to test my new idea. I can skim my code and see a bunch of things that would normally take me ages to fiddle. The fiddling is frustrating, because I feel like I know what the end result should be, but there's some minor BS in the way, which takes a few minutes each time. It used to take a whole stackoverflow search + think, recently it became a copilot hint, and now... Claude simply does it.

For instance, I wrote a mock stock exchange. It's the kind of thing you always want to have, but because the pressure is on to connect to the actual exchange, it is often a leftover task that nobody has done. Now, Claude has done it while I've been reading HN.

Now that I have that, I can implement a strategy against it. This is super tedious. I know how it works, but when I implement it, it takes me a lot of time that isn't really fulfilling. Stuff like making a typo, or forgetting to add the dependency. Not big brain stuff, but it takes time.

Now I know what you're all thinking. How does it not end up with spaghetti all over the place? Well. I actually do critique the changes. I actually do have discussions with Claude about what to do. The benefit here is he's a dev who knows where all the relevant code is. If I ask him whether there's a lock in a bad place, he finds it super fast. I guess you need experience, but I can smell when he's gone off track.

So for me, career-wise, it has come at the exact right time. A few years after I reached a level where the little things were getting tedious, a time when all the architectural elements had come together and been investigated manually.

What junior devs will do, I'm not so sure. They somehow have to jump to the top of the mountain, but the stairs are gone.

replies(15): >>44616871 #>>44616935 #>>44617102 #>>44617254 #>>44618137 #>>44618793 #>>44621101 #>>44621200 #>>44621741 #>>44621995 #>>44622452 #>>44622738 #>>44623119 #>>44624925 #>>44624959 #
zwnow ◴[] No.44616871[source]
So you are relaxing and the AI is coding? Neat! Way to replace yourself, hope you won't cry after your job once it is gone.
replies(3): >>44616920 #>>44616930 #>>44617503 #
lubujackson ◴[] No.44616920[source]
What you miss is the constant need to refine and understand the bigger picture. AI makes everyone a lead architect. A non-coder can't do this or will definitely get lost in the weeds eventually.
replies(2): >>44617314 #>>44617557 #
jon-wood ◴[] No.44617557[source]
It doesn’t make everyone a lead architect, it just makes everyone think they’re a lead architect. What makes people a lead architect is a decade or two of experience in designing software and learning what works and doesn’t.
replies(1): >>44622698 #
LtWorf ◴[] No.44622698[source]
What makes people a lead architect in my experience is an abnormal amount of arrogance and no capability to admit mistakes.
replies(1): >>44625544 #
1. actionfromafar ◴[] No.44625544[source]
That just gives the title. To be really successful, they need to let someone else, knowledgeable, actually make the architecture decisions.
replies(1): >>44627964 #
2. LtWorf ◴[] No.44627964[source]
Yeah that's the actual senior developers who just ignore everything the architect architects.