Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A field guide to the modern front end for developers who hand-wrote HTML

davidpoblador.com

Post reply on HN
Print view View original

31–40 of 45 posts

Re: A field guide to the modern front end for developers who hand-wrote HTML

#31

Post by JimDabell »

nhod wrote: post #8
poly2it wrote: post #2

For some reason I find Claude's writing often has an oddly condescending tone when it tries to be empathetic.

“Every tool is scar tissue over a real wound. Follow the wounds, and the map draws itself. THE ONE IDEA THAT UNLOCKS EVERYTHING” uh-huh I have noticed myself having a visceral reaction to the AI tells now, somewhere between disgust and anger. And I am not an angry man and I like AI! There is just something about the voice that is incredibly off-putting, like a know-it-all friend who just ripped a giant fart. It is an…

It sounds like an overly earnest TEDx talker leaning over you talking about something inconsequential as if it’s the most mic-droppingly insightful thing in the world.

Re: A field guide to the modern front end for developers who hand-wrote HTML

#32

Post by alwa »

p4bl0 wrote: post #5

This is too oddly written to read in its entirety and I don't get the point. I mostly still do things like it says it worked in 2008. The difference with the "modern" workflow with 1400 packages and a build system is that web pages I put online just work, unlike most modern website which are horribly bug ridden and take ages to load and render.

They had me at “scar tissue grown over a real wound.”

Re: A field guide to the modern front end for developers who hand-wrote HTML

#33

Post by camillomiller »

mhitza wrote: post #15
memjay wrote: post #3

Reading this hurt so much. Please just write articles by hand. I don’t care about perfect grammar and I don’t care about your article sounding „native“ or not. But I do care about not having to read the word „genuinely“ a hundred times just because Claude likes it so much.

I don't think only their writing is AI, I suspect the site as well. With modern frontend GenAI renditions it is more common for me to find sites that stutter during scroll, as this site does.

Not a suspect, it's a certainty.

https://www.newyorker.com/culture/infinite-scroll/the-ai-des...

Re: A field guide to the modern front end for developers who hand-wrote HTML

#36

Post by nirvanis »

tantalor wrote: post #35

[Metapost] Can we unflag this? It's a good resource and shouldn't be suppressed just because some people don't like the tone.

Hi, OP here. Thanks for this.

I don’t seem to have cracked the Hacker News writing formula yet. A few years ago I got similar feedback, but for the opposite reason: people complained that my English felt awkward because I’m not a native speaker. This time I asked an LLM to smooth out the wording, and it seems I accidentally outsourced my personality too.

The content and research are mine. I spent a few hours trying to collect all the moving pieces into something I wish I’d had as someone returning to frontend after many years away. It was just meant to save a few fellow dinosaurs from opening 47 tabs and wondering why they suddenly need seven package managers.

Re: A field guide to the modern front end for developers who hand-wrote HTML

#37

Post by add-sub-mul-div »

tantalor wrote: post #35

[Metapost] Can we unflag this? It's a good resource and shouldn't be suppressed just because some people don't like the tone.

No, there's no reason for slop to be posted here. If we wanted it we could just generate it ourselves.

Re: A field guide to the modern front end for developers who hand-wrote HTML

#38

Post by ashleyn »

JimDabell wrote: post #28

> In 2008 you saved a file called index.html, dragged it onto an FTP client, and watched a little progress bar crawl to the right. When I was first learning web development in the 90s, after a couple of sites, I switched to a hosting provider that offered a bit more control over the hosting environment. I discovered that they supported SCP and SFTP but not FTP. When I asked them why, they told me it was because FTP w…

I writhe in pain when I try to find a frontend dev guide for a newbie to learn off, and one of the later chapters is some shit like setting up a kubernetes cluster

Re: A field guide to the modern front end for developers who hand-wrote HTML

#39

Post by rubinlinux »

nirvanis wrote: post #36
tantalor wrote: post #35

[Metapost] Can we unflag this? It's a good resource and shouldn't be suppressed just because some people don't like the tone.

Hi, OP here. Thanks for this. I don’t seem to have cracked the Hacker News writing formula yet. A few years ago I got similar feedback, but for the opposite reason: people complained that my English felt awkward because I’m not a native speaker. This time I asked an LLM to smooth out the wording, and it seems I accidentally outsourced my personality too. The content and research are mine. I spent a few hours trying t…

I work with claude every day, and instantly recognized its voice; but at the same time, as a web dev from the late 90s who traveled kicking and screaming through all of these ages, I really enjoyed the article anyway. I don't have a visceral disgust with claude's tone as some others here seem to. I'm glad you wrote it and I plan to share it with a friend.

Re: A field guide to the modern front end for developers who hand-wrote HTML

#40

Post by re »

nirvanis wrote: post #36
tantalor wrote: post #35

[Metapost] Can we unflag this? It's a good resource and shouldn't be suppressed just because some people don't like the tone.

Hi, OP here. Thanks for this. I don’t seem to have cracked the Hacker News writing formula yet. A few years ago I got similar feedback, but for the opposite reason: people complained that my English felt awkward because I’m not a native speaker. This time I asked an LLM to smooth out the wording, and it seems I accidentally outsourced my personality too. The content and research are mine. I spent a few hours trying t…

Like others here, the content is something that I'm interested in, but I too have a reaction to the LLM-isms. I think part of it is that, once I recognize I'm reading LLM output, I have no way of knowing if it wrote the whole post based on a one-or-two sentence prompt or not, and if it did, how much can I really trust the output to not be hallucinated. If I'm going to read LLM output, I'd rather do so in the context of my own chat with it so I can understand the inputs to it and ask follow-up questions.

Can you put the pre-LLM version of your post on your site somewhere? I (and presumably many others) would be much more interested in reading that, even if the English is a bit awkward.

Post reply on HN