←back to thread

119 points lsharkey602 | 1 comments | | HN request time: 0.452s | source
Show context
reedf1 ◴[] No.44423223[source]
I think it is possible that the widespread introduction of ChatGPT will cause a brief hiatus on hiring due to the inelasticity of demand. For the sake of argument, imagine that ChatGPT makes your average developer 4x more productive. It will take a while before the expectation becomes that 4x more work is delivered. That 4x more work is scheduled in sprints. That 4x more features are developed. That 4x more projects are sold to clients/users. When the demand eventually catches up (if it exists), the hiring will begin again.
replies(9): >>44423267 #>>44423282 #>>44423301 #>>44423329 #>>44423440 #>>44423459 #>>44423688 #>>44423878 #>>44424258 #
TSiege ◴[] No.44423440[source]
I am not asking this as a gotcha, but a genuine curiosity for you or other people who find AI is helping them in terms of multiples. What is your workflow like? Where do you lean on AI vs not? Is it agentic stuff is tab by cursor?

I find AI helpful but no where near a multiplier in my day to day development experience. Converting a csv to json or vis-versa great, but AI writing code for me has been less helpful. Beyond boiler plate, it introduces subtle bugs that are a pain in the ass to deal with. For complicated things, it struggles and does too much and because I didn't write it I don't know where the bad spots are. And AI code review often gets hung up on nits and misses real mistakes.

So what are you doing and what are the resources you'd recommend?

replies(8): >>44423484 #>>44423651 #>>44423715 #>>44423749 #>>44423843 #>>44423996 #>>44424208 #>>44424679 #
1. SatvikBeri ◴[] No.44423996[source]
I get very good results from Claude Code, something like a 3x. It's enough that my cofounders noticed and commented on it, and has had a lot of measurable results in terms of saving $ on infrastructure.

The first thing I'll note is that Claude Code with Claude 4 has been vastly better than everything else for me. Before that it was more like a 5-10% increase in productivity.

My workflow with Claude Code is very plain. I give it a relatively short prompt and ask it to create a plan. I iterate on the plan several times. I ask it to give me a more detailed plan. I iterate on that several times, then have Claude write it down and /clear to reset context.

Then, I'll usually do one or more "prototype" runs where I implement a solution with relatively little attention to code quality, to iron out any remaining uncertainties. Then I throw away that code, start a new branch, and implement it again while babysitting closely to make sure the code is good.

The major difference here is that I'm able to test out 5-10 designs in the time I would normally try 1 or 2. So I end up exploring a lot more, and committing better solutions.