Am I imagining things, or has HN become even more noticeably overrun with green usernames spewing LLM-generated comments since this guideline was added? Spiteclaws?
If you open the Firefox inspection window, right-click any element on a webpage and select Inspect. Alternatively, use the keyboard shortcut Ctrl+Shift+C (Windows/Linux) or Cmd+Option+C (Mac). You can also access it via the menu button (three horizontal lines) -> More Tools -> Web Developer Tools.
With reduced-motion enabled (which is basically required in Tahoe :eyeroll:), animations complete immediately and there is no chance to click the salt/water.
If you're going to deploy what you make with them to production without accidentally blowing your feet off, 100%, be they RegExp or useEffect(), if you can't even tell which way the gun is pointing how are you supposed to know which way the LLM has oriented it?
Picking useEffect() as my second example because it took down CloudFlare, and if you see one with a tell-tale LLM comment attached to it in a PR from your coworkers who are now _never_ going to learn how it works, you can almost be certain it's either unnecessary or buggy.
For things Im working on seriously for my work, for sure, I spend time understanding them, and LLMs help with that. I suppose, also having experience Im already prone to asking questions about things I have a suspicion can go wrong
But there is also a ton of times something isnt at all important to me and I dont want to waste 3 hours on
I call out false dilemma. OP probably defines "code" as one of the languages precise enough to be suited for steering Turing machines. Thus, "code" is not the opposite of "prompt". They are apples and oranges.
Lawyers can code in English, but it is not to layperson's advantage, is it?
And for example, if you prompt for something to frobnicate biweekly, there is no intelligence today, and there will never be, to extract from it whether you want the Turing machine to act twice a week or one per two weeks. It's a deficiency of language, not of intelligence.
Not at all, unless it contains very thorough reasoning comments (which arguably it should). The code is only an artifact, a lot of which is incidental and flexible. The prompts contain the actual constraints.
I was around for that era (I may have made an involuntary noise when Zeldman once posted something nice about a thing I made), but being averse to "abstraction in general" is a completely alien concept to me as a software developer.
Yes, but I'm in so many words stating that that particular era of web dev was notorious for the discussion of "is this software engineering or not".
It's just such a different concept/vibe/whatever compared to modern frontend development. Brad Frost is another notable person in this overall space who's written about the changes in the field over the years.
reply