←back to thread

413 points martinald | 2 comments | | HN request time: 0s | source
Show context
tangotaylor ◴[] No.46204312[source]
> Engineers need to really lean in to the change in my opinion.

I tried leaning in. I really tried. I'm not a web developer or game developer (more robotics, embedded systems). I tried vibe coding web apps and games. They were pretty boring. I got frustrated that I couldn't change little things. I remember getting frustrated that my game character kept getting stuck on imaginary walls and kept asking Cursor to fix it and it just made more and more of a mess. I remember making a simple front-end + backend with a database app to analyze thousands of pull request comments and it got massively slow and I didn't know why. Cursor wasn't very helpful in fixing it. I felt dumber after the whole process.

The next time I made a web app I just taught myself Flask and some basic JS and I found myself moving way more quickly. Not in the initial development, but later on when I had to tweak things.

The AI helped me a ton with looking things up: documentation, error messages, etc. It's essentially a supercharged Google search and Stack Overflow replacement, but I did not find it useful letting it take the wheel.

replies(9): >>46204550 #>>46205027 #>>46206045 #>>46206421 #>>46206931 #>>46210894 #>>46211263 #>>46211291 #>>46216142 #
r_lee ◴[] No.46204550[source]
These posts like the one OP made is why I'm losing my mind.

Like, is there truly an agentic way to go 10x or is there some catch? At this point while I'm not thrilled about the idea of just "vibe coding" all the time, I'm fine with facing reality.

But I keep having the same experience as you, or rather leaning more on that supercharged Google/SO replacement

or just a "can you quickly make this boring func here that does xyz" "also add this" or for bash scripts etc.

And that's only when I've done most of the plumbing myself.

replies(19): >>46204630 #>>46204766 #>>46204828 #>>46204843 #>>46204925 #>>46205328 #>>46205478 #>>46205659 #>>46205781 #>>46205890 #>>46205913 #>>46205924 #>>46205931 #>>46206330 #>>46207518 #>>46209875 #>>46214153 #>>46214479 #>>46214591 #
itgoon ◴[] No.46204925[source]
Like another reply says: practice.

How many hours have you spent writing code? Thousands? Tens of thousands? Were you able to achieve good results in the first hundred hours?

Now, compare it to how much time you've spent working with agents. Did you dedicate considerable time to figuring out how to use them? Do you stop using the agent and do things manually when it isn't going right, or do you spend time figuring out how to get the agent to do it?

replies(2): >>46204957 #>>46204996 #
1. crowbahr ◴[] No.46204996{3}[source]
You can't really compare those 2. Agents a re non-deterministic. I can tell Clod to go update my unit test coverage and it will choke itself, burn 200k tokens and then loudly proclaim "Great! I've updated unit test coverage".

I'll kill that terminal, open it again and run the exact same command. 30k tokens, actually adds new tests.

It's hard to "learn" when the feedback cycle can take 30 minutes and result in the agent sitting in the corner touching itself and crooning about what a good boy it is. It's hard to _want_ to learn when you can't trust the damn thing with the same prompt twice.

replies(1): >>46205011 #
2. funkydata ◴[] No.46205011[source]
That comment made my day. I actually had an intern like that!