llm/c92d54db-e3c8-419f-931f-0c3a686c0e4d/batch-6-bb8fdcfb-6765-4429-8ffd-ca7cee8d19cf-input.json
You are a comment classifier. Given a list of topics and a batch of comments, assign each comment to up to 3 of the most relevant topics.
TOPICS (use these 1-based indices):
1. AI productivity claims skepticism
2. Joy of coding vs results
3. Parent/manager time constraints
4. Vibe coding criticism
5. Web development complexity
6. Learning with AI assistance
7. Code review burden
8. Frontend framework criticism
9. Solo developer challenges
10. AI as skill crutch
11. Hobby project completion
12. Cost of AI tools
13. Pattern recognition experience
14. Management skills transfer
15. Identity crisis for developers
16. Local vs cloud AI models
17. Unnecessary toolchain complexity
18. Code quality concerns
19. Generalist vs specialist debate
20. Mental model building
COMMENTS TO CLASSIFY:
[
{
"id": "46492531",
"text": "To me it seems like for OP development was a means towards an end. The act to developing software as a craft does not seem to be of importance to him while the output is. His post is full of references to productivity and lacking references of improving his skills (as opposed to using LLMs as a crutch) or getting better at writing software. I bet OP would be equally happy if he had AGI that would write everything for him. For many in HN, programming is an end in itself and they would not be happy giving that up just because it makes you finish quicker."
}
,
{
"id": "46492446",
"text": "This is probably the best post i've seen about the whole LLM / vibe coding space at least in relation to web dev. Indeed, as the author states, the code / agent often needs some coralling, but if you know all the gotchyas / things to look for, you can focus 100% on the creativity part! Been loving it as well."
}
,
{
"id": "46489421",
"text": "Turbo C++ Vibe"
}
,
{
"id": "46491814",
"text": "Web development is perhaps \"fun\" again if you consider PHP 4 and jQuery as \"fun\". A \"problem\" arises for those of us who prefer Ruby, Rails, and HotWire. I'm not gonna lie, I use AI every day (in the form of Grammarly). But LLMs and so-called \"agents\" are less valuable to me, even if they would help me to produce more \"output\". It will be interesting to me to discover the outcome of this bifurcation!"
}
,
{
"id": "46488981",
"text": "Not the first time I can't access a link posted here due being blocked in Spain."
}
,
{
"id": "46489090",
"text": "Are you using your ISP DNS? I’m in Spain as well and I can access the link just fine."
}
,
{
"id": "46489309",
"text": "I'm using Cloudflare's. I don't know how this blocking works. A couple minutes ago I could access this link but now I can't. It's happening with another website too. It's like an intermittent blocking today."
}
,
{
"id": "46489468",
"text": "Real Madrid's on today, so it must be LaLiga's bullshit once again. If it helps, 8.8.8.8 is not giving me issues, not sure if it's something other than DNS breaking on your side though."
}
,
{
"id": "46489120",
"text": "Reading this from Tenerife airport and worked fine."
}
,
{
"id": "46491274",
"text": "Couldn’t agree more. Changing anything in oUR react Bootstrap frontend was a visit to the dentist. But Llms really lowered the pain."
}
,
{
"id": "46488913",
"text": "AI is doing the chores while we paint."
}
,
{
"id": "46489007",
"text": "Except to me it feels more like AI is painting while I have to do the chores"
}
,
{
"id": "46492045",
"text": "I feel u!"
}
,
{
"id": "46492544",
"text": "As a solo developer, you can totally program like you did in the php 4 days. PHP and the web platform are both mostly backward compatible, only both have more features that help a lot, including with security, and deprecated or removed mostly bad stuff (yeah, maybe don't use the automagic variables set from the request, and don't rely on magic quotes to avoid SQL injections). You don't need the frameworks and the pipelines and all the complexity. It's a choice you make, and you can make the choices that are easier/more fun for you. You can still mix php and HTML like it's 2005. It won't kill anyone. It still works. Of course, if you don't test your code you risk introducing regressions or shipping broken features. But that was true back then. You can write unmaintainable mess but that was true back then as well. AI is not needed. Just program the way you used to like and find fun back then and it'll be fun now. Of course, if you enjoy some framework, go for it, but you don't need to do"
}
,
{
"id": "46490651",
"text": ">On the frontend, you have build pipelines, bundlers, CSS frameworks with their own toolchains, progressive web apps, Core Web Vitals, SEO, layout shifts, srcset/responsive images... I remember when the biggest challenge was IE6 compatibility. It is not necessary to do this. Server-side rendering is still a thing. I still do a lot of my side projects in ruby on rails, which is maybe not fashionable these days but: - no heavy js means speedy first paint - I just use normal minified css, no sass or other junk - partials means navigation is snappy Plus it containerizes nicely."
}
,
{
"id": "46492761",
"text": "Build pipelines, bundlers, CSS frameworks with their own toolchains, progressive web apps, Core Web Vitals, SEO, layout shifts, and srcset/responsive images have nothing to do with client/server rendering."
}
,
{
"id": "46492975",
"text": "With server-side rendering you don't need a frontend framework at all, is my point. You also don't need a css tool chain at all, irrespective of whether or not you render on the frontend"
}
,
{
"id": "46488989",
"text": "When stuff was getting too complicated, I looked for ways to make things simpler. Developers have spent decades trying to figure out ways to make things simpler, less code the better, only to throw it all out the window because chatbot go brrrrrr."
}
,
{
"id": "46490659",
"text": "In a very real sense, developers efforts to make web development simpler have clearly failed. This is true regardless of the existence of LLMs and/or your opinion of their utility."
}
,
{
"id": "46493578",
"text": "They have been very successful. After we got a hit from security requirements and broke the Microsoft monopoly on browsers, web development have only got more and more potentially simple. If you or some other person don't program in the way that makes it simple, it's not our communitary problem. What matters is that the potential is there."
}
,
{
"id": "46489053",
"text": "It’s because business demand speed and shipping over other concerns. We had to fight hard for proper quality controls in the face of the LLM coding assistance boom where I work. These are great tools but they have limits and can lead to poor engineering hygiene quite quickly. It took a major issue being attributed to having too much trust in these tools before we were able to enforce better hygiene with them"
}
,
{
"id": "46490498",
"text": "Yeah. I love programming. I even love the business side where you solve real problems for people. What I don't love is the constant pressure to just deliver faster and faster. So forcing these chatbots on us fill a need for the CEOs and manager types that just want to DELIVER DELIVER DELIVER, but the benefit for the people that are forced to use them are marginal at best. There are some valid use cases for LLM-based tools, but businesses mostly aren't interested in those because it doesn't make line go up. Streamlining operations? Nah. Shove a Chatbot where it doesn't belong so you can try to get a billion dollar investment? NOW WE ARE COOKING C-suites and managers don't give a shit about quality unless they feel the pain. That's the most important thing I've learned. If you can find a way to push the pain up to the people that make the decisions, the more likely they are incentivised to improve it. It doesn't matter if you see a problem that takes 2 days to fix coming a year away - th"
}
,
{
"id": "46492666",
"text": "Customers don't buy software based on quality first, they buy on features. Until customers in mass, or regulations demand quality, money will be made on deliveries. If your lucky and can program how you want and take the time you need, then you can focus on the attributes you feel best about."
}
,
{
"id": "46493994",
"text": "If you have customers that will put up with things being slow as molasses and crashing al the time, well….can you send some my way because mine won’t STFU about it."
}
,
{
"id": "46490558",
"text": "please, developers are making terrible slop way before AI, look at the javascript infested frameworks in use on the web. they make NO sense. they are not making things simpler"
}
,
{
"id": "46490589",
"text": "And now you can generate javascript infested slop frameworks for $5 per million tokens. Such an improvement. And it's so easy to just ask Claude to make one for you, why even bother standardizing anything when you can just use bespoke slop for anything anymore. Libraries and frameworks? Not needed. Just shove everything into CC/Codex and let it figure it out."
}
,
{
"id": "46490877",
"text": "The financial incentives of the Chatbots are always going to push people towards increased complexity, as well. The tendency will be for frameworks to become more complex, which will lead to increased LLM use, which will increase complexity."
}
,
{
"id": "46490964",
"text": "We need better chatbots to fix the bugs from the current chatbots that fixed the bugs from the previous chatbots when they fixed the bugs from the previous generation of chatbots that….. Just give Sam Altman more and more of your money and he’ll make a more advanced chatbot to fix the chatbot he sold you that broke everything. You don’t even need to own a computer, just install an app on your phone to do it all. It doesn’t matter that regular people have been completely priced out of personal computing when GPT is just gonna do all the computing anymore anyway. Clearly a sustainable way forward for the industry."
}
,
{
"id": "46491035",
"text": "Yes, so what? That's what I basically do, i need a little framework with this and that and API, 15 minutes later I get exactly what I need and want. Not more, not less.as long as it's not Auth, crypto or something like that, I don't see an issue."
}
,
{
"id": "46490871",
"text": "That actually might be an improvement over the JS frameworks..."
}
,
{
"id": "46492739",
"text": "I remember when Hacker News felt smaller. Threads were shorter. Context fit in your head. You could read the linked article, skim the comments, and jump in without feeling like you’d missed a prerequisite course. It probably didn’t feel special at the time, but looking back, it was simpler. The entire conversation space was manageable. If you had a thought, you could express it clearly, hit “reply,” and reasonably expect to be understood. As a single commenter, you could hold the whole discussion in your mind. From article to argument to conclusion. Or at least, it felt that way. I’m probably romanticizing it—but you know what I mean. Now, articles are denser. Domains are deeper. Threads splinter instantly. Someone cites a paper, someone else links a counter-paper, a third person references a decades-old mailing list post, and suddenly the discussion assumes years of background you may or may not have. You’re expected to know the state of the art, the historical context, the common reb"
}
,
{
"id": "46493044",
"text": "Tell the AI to keep your comment shorter next time ;)"
}
,
{
"id": "46489057",
"text": ">>Starting a new project once felt insurmountable. Now, it feels realistic again. Honestly, this does not give me confidence in anything else you said. If you can't spin up a new project on your own in a few minutes, you may not be equipped to deal with or debug whatever AI spins up for you. >>When AI generates code, I know when it’s good and when it’s not. I’v seen the good and the bad, and I can iterate from there. Even with refinement and back-and-forth prompting, I’m easily 10x more productive Minus a baseline, it's hard to tell what this means. 10x nothing is nothing. How am I supposed to know what 1x is for you, is there a 1x site I can look at to understand what 10x would mean? My overall feeling prior to reading this was \"I should hire this guy\", and after reading it my overwhelming thought was \"eat a dick, you sociopathic self-aggrandizing tool.\" Moreover, if you have skill which you feel is augmented by these tools, then you may want to lean more heavily on that skill now if "
}
,
{
"id": "46488842",
"text": "honestly, with LLMs, everything is fun again. embedded dev with a billion toolchains, GPU development with each vendors bespoke API, ffmpeg with its billion parameters - if anything, you could say LLMs bailed us out of the impending ultra-specialization. without LLMs, we might be facing a world where 30% of the workforce is in software dev. i am keeping my eyes peeled on vibe-coding PCB layouts and schematics. a lot of eyes in that direction already but its still early."
}
,
{
"id": "46489037",
"text": "I don't get it. What part of the process do you enjoy? Do you also enjoy hiring a taskrabbit to go hiking for you, taking photos along the way?"
}
,
{
"id": "46491349",
"text": "Seeing the output I want when I describe it, and making changes to get to the vision in my mind. I don't have aphantasia so maybe it's different for those who do, but I can literally see the UI of the app I want to build and of course I can build it by writing code manually too, but I can make it exist much faster with an LLM than without."
}
,
{
"id": "46489831",
"text": "I’m just looking to make pizza not smelt the ore for the oven I’m going to cook it in."
}
,
{
"id": "46490203",
"text": "Why make pizza when you can order it? As far as I can tell, there's not much enjoyment of making being had. Enjoying having is fine too, but let's at least be honest about it. I enjoy looking at photos people took on hikes, but I don't call it hiking."
}
,
{
"id": "46490625",
"text": "Is it hiking if I bought my boots on amazon?"
}
,
{
"id": "46490658",
"text": "Not if you sit at home wearing boots and looking at photos of mountains. If you want to have boots, that's cool. But is replacing walking with ordering boots and photos making hiking fun again? Or were you only interested in the photos anyway? What part of the process of hiking do you enjoy? And why is it so hard to hear what part of the process of programming people enjoy?"
}
,
{
"id": "46491611",
"text": "But you’d agree it’s still hiking even if I didn’t tan the leather for the boots myself."
}
,
{
"id": "46491675",
"text": "Yes, if you go out and walk. The same way I would agree it was programming if you designed the algorithms yourself."
}
,
{
"id": "46490768",
"text": "This is just obtuse. Some folks have fun building their own pizza oven, curing & slicing their own meat, and mixing their own dough. Some folks like to buy mostly pre-made stuff and just play with a few special ingredients. Some folks want to make 5 different pizzas with different flavors. Some folks just order a pizza. Some folks walk out of their house and start hiking. Some folks drive somewhere and then start walking. Some folks take photos from the car. Some folks take a roadtrip. All of these things ask for different effort & commitment with different experiences & results as the payoff. At least be honest about that."
}
,
{
"id": "46490859",
"text": "It's interesting that nobody has actually answered what part of the process they enjoy."
}
,
{
"id": "46491365",
"text": "Like, fine, here's a personal example: I wanted to build a system that posts web links I share to a bot account on the fediverse. That seemed like a fun result to me. I wanted to self-host the links, so I installed Linkding. (I didn't write Linkding.) For the fediverse bot, I installed gotosocial as the service host (I didn't write gotosocial.) From there, a cronjob running a small program using Linkding and gotosocial APIs could do the trick. Decided to do it in golang, because the standalone binaries are easy to deploy. Writing that small program didn't seem like fun - I've already played with those APIs and golang. What I wanted, for my enjoyment, was the completed system. So, I took 10 minutes to write out a quick spec for the program and what I wanted it to do. I loaded that up as context for Claude Code along with some pointers for building CLI apps in golang. I let it rip and, in about 20 minutes, Claude produced a functional tool. It also wrote a decent README based on my origi"
}
,
{
"id": "46491016",
"text": "It's different for everyone, so no one answer would likely satisfy you"
}
,
{
"id": "46491068",
"text": "That's why I used the word \"you\" and not \"I\"."
}
,
{
"id": "46493828",
"text": "Having a product that works is what these people enjoy"
}
,
{
"id": "46488932",
"text": "On a meta level, seems this trajectory follows Alan Kay: first we made the complex things possible, now we make simple things simple."
}
,
{
"id": "46488864",
"text": "I agree with this. I've been able to tackle projects I've been wanting to for ages with LLMs because they let me focus on abstractions first and get over the friction of starting the project. Once I get my footing, I can use them to generate more and more specialized code and ultimately get to a place where the code is good."
}
]
Return ONLY a JSON array with this exact structure (no other text):
[
{
"id": "comment_id_1",
"topics": [
1,
3,
5
]
}
,
{
"id": "comment_id_2",
"topics": [
2
]
}
,
...
]
Rules:
- Each comment can have 0 to 3 topics
- Use 1-based topic indices
- Only assign topics that are genuinely relevant to the comment
- If no topics match, use an empty array:
{
"id": "...",
"topics": []
}
50