top | item 45616203

(no title)

appapapp | 4 months ago

Very concerning the author is ok with saying “I don’t know how to do this, and I don’t want to learn so I let Claude do it”.

I think a lot of LLM speedups boil down to this (from personal and read experience). Which is fine in some limited use cases, but also the antithesis of a good developer. Your job is to learn how things work if it’s work you’re putting your name behind.

Using LLMs to shortcut the blank page in these scenarios and get you learning faster is the way to go (though sometimes it’ll send you in the absolute wrong direction initially).

> Since then, I have vibecoded every single feature … now, this has lead to a number of hilarious failures

When I was a junior dev I wouldn’t read every line of a PR. Eventually you learn you should be reading lines that aren’t changed in a PR as well as every line that is. The author seems like a smart guy but more of a researcher than somebody I’d pay to build reliable software.

discuss

order

fhd2|4 months ago

Oh you're gonna learn how things work, if you stick around long enough. The decision you get to make is whether you'll learn one thing at a time while you're building, or everything all at once under pressure at 2am.