llm/c92d54db-e3c8-419f-931f-0c3a686c0e4d/batch-1-94bb1332-9252-42eb-850f-5ed6084722d9-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": "46493849",
"text": "Which is fine, because those things are what makes programming fun for you. Not for others."
}
,
{
"id": "46491404",
"text": "I do have productivity goals! I want to spend the half hour I have on the part I think is fun. Not on machine configuration, boilerplate, dependency resolution, 100 random errors with new frameworks that are maybe resolved with web searches."
}
,
{
"id": "46492231",
"text": "I enjoy noodling around with pointers and unsafe code in Rust. Claude wrote all the documentation, to Rust standards, with nice examples for every method. I decided to write an app in Rust with a React UI, and Claude wrote almost all the typescript for me. So I’ve used Claude at both ends of the spectrum. I had way more fun in every situation. AI is, fortunately, very bad at the things I find fun, at least for now, and very good at the things I find booooring (read in Scot Pilgrim voice)."
}
,
{
"id": "46491636",
"text": "I think there can be other equally valid perspectives than your own. Some people have goals of actually finishing a project instead of just \"tinkering\"... and that's ok. Some say it might even be necessary."
}
,
{
"id": "46491657",
"text": "You could make the same argument about the printing press. Some people like forming the letters by hand, others enjoy actually writing."
}
,
{
"id": "46493318",
"text": "Actually, the invention of the printing press in 1450 created a similar disruption, economic panic and institutional fear similar to what we're experiencing now: For centuries, the production of books was the exclusive domain of professional scribes and monks. To them, the printing press was an existential threat. Job Displacement: Scribes in Paris and other major cities reportedly went on strike or petitioned for bans, fearing they would be driven into poverty. The \"Purity\" Argument: Some critics argued that hand-copying was a spiritual act that instilled discipline, whereas the press was \"mechanical\" and \"soulless.\" Aesthetic Elitism: Wealthy bibliophiles initially looked down on printed books as \"cheap\" or \"ugly\" compared to hand-illuminated manuscripts. Some collectors even refused to allow printed books in their libraries to maintain their prestige. Sound familiar? From \"How the Printing Press Reshaped Associations\" -- https://smsonline.net.au/blog/how-the-printing-press-reshape.."
}
,
{
"id": "46494329",
"text": "I've seen this argument a few times before and I'm never quite convinced by it because, well, all those arguments are correct. It was an existential threat to the scribes and destroyed their jobs, the majority of printed books are considered less aesthetically pleasing than a properly illuminated manuscript, and hand copying is considered a spiritual act by many traditions. I'm not sure if I say it's a correct argument, but considering everyone in this thread is a lot closer to being a scribe than a printing press owner, I'm surprised there's less sympathy."
}
,
{
"id": "46492483",
"text": "This does seem to be what many are arguing, even if the analogy is far from perfect."
}
,
{
"id": "46492221",
"text": "Exactly! ...If the printing press spouted gibberish every 9 words."
}
,
{
"id": "46492638",
"text": "That was LLMs in 2023."
}
,
{
"id": "46492840",
"text": "Respect to you. I ran out of energy to correct people's dated misconceptions. If they want to get left behind, it's not my problem."
}
,
{
"id": "46492954",
"text": "At some point no-one is going to have to argue about this. I'm guessing a bit here, but my guess is that within 5 years, in 90%+ jobs, if you're not using an AI assistant to code, you're going to be losing out on jobs. At that point, the argument over whether they're crap or not is done. I say this as someone who has been extremely sceptical over their ability to code in deep, complicated scenarios, but lately, claude opus is surprising me. And it will just get better."
}
,
{
"id": "46493937",
"text": "> At that point, the argument over whether they're crap or not is done. Not really, it just transforms into a question of how many of those jobs are meaningful anyway, or more precisely, how much output from them is meaningful."
}
,
{
"id": "46489792",
"text": "It's a little shameful but I still struggle when centering divs on a page. Yes, I know about flexbox for more than a decade but always have to search to remember how it is done. So instead of refreshing that less used knowledge I just ask the AI to do it for me. The implications of this vs searching MDN Docs is another conversation to have."
}
,
{
"id": "46494467",
"text": "> Yes, I know about flexbox for more than a decade but always have to search to remember how it is done. These days I use display: flex; so much that I wish the initial value of the display property in CSS should be flex instead of inline;"
}
,
{
"id": "46490615",
"text": "No shame in that. I keep struggling to figure out the point of view of the CSS designers. They don't think like graphic designers, or like programmers. It's not easy for beginners. It's not aimed at ease of implementation. It's not amenable to automated validation. It's not meant to be generated. If there is some person for whom CSS layout comes naturally, I have not met them. As far as I can tell their design goal was to confuse everyone, at which they succeeded magnificently."
}
,
{
"id": "46493685",
"text": "> I keep struggling to figure out the point of view of the CSS designers. Before 2017, the web had no page layout ability. Think about it. Before the advent of Flexbox and CSS Grid, certain layouts were impossible to do. All we had were floats, absolute positioning, negative margin hacks, and using the table element for layout. > They don't think like graphic designers or like programmers. It's not easy for beginners. CSS is dramatically easier if you write it in order of specificity: styles that affect large parts of the DOM go at the top; more specific styles come later. Known as Inverted Triangle CSS (ITCSS), it has been around for a long time [1]. > It's not aimed at ease of implementation. It's not amenable to automated validation. If you mean linting or adhering to coding guidelines, there are several; Stylelint is popular [2]. Any editor that supports Language Server Protocol (LSP), like VS Code and Neovim (among others), can use CSS and CSS Variables LSPs [3], [4] for code comp"
}
,
{
"id": "46489953",
"text": "Hah, centering divs with flexbox is one of my uses for this too! I can never remember the syntax off the top of my head, but if I say \"center it with flexbox\" it spits out exactly the right code every time. If I do this a few more times it might even stick in my head."
}
,
{
"id": "46489838",
"text": "Try tailwind. Very amenable to LLM generation since it's effectively a micro language, and being colocated with the document elements, it doesn't need a big context to zip together."
}
,
{
"id": "46490918",
"text": "Surely searching \"centre a div\" takes less time than prompting and waiting for a response..."
}
,
{
"id": "46491174",
"text": "Search “centre a div” in Google Wade through ads Skim a treatise on the history of centering content Skim over the “this question is off topic / duplicate” noise if Stack Overflow Find some code on the page Try to map how that code will work in the context of your other layout Realize it’s plain CSS and you’re looking for Tailwind Keep searching Try some stuff until it works Or… Ask LLM. Wait 20-30 seconds. Move on to the next thing."
}
,
{
"id": "46493176",
"text": "The middle step is asking an LLM how it's done and making the change yourself. You skip the web junk and learn how it's done for next time."
}
,
{
"id": "46493367",
"text": "Yep, that’s not a bad approach, either. I did that a lot initially, it’s really only with the advent of Claude Code integrated with VS Code that I’m learning more like I would learn from a code review. It also depends on the project. Work code gets a lot more scrutiny than side projects, for example."
}
,
{
"id": "46494130",
"text": "Or, given that OP is presumably a developer who just doesn't focus fully on front end code they could skip straight to checking MDN for \"center div\" and get a How To article ( https://developer.mozilla.org/en-US/docs/Web/CSS/How_to/Layo... ) as the first result without relying on spicy autocomplete. Given how often people acknowledge that ai slop needs to be verified, it seems like a shitty way to achieve something like this vs just checking it yourself with well known good reference material."
}
,
{
"id": "46491308",
"text": "Wait till the VC tap gets shut off. You: Hey ChatGPT, help me center a div. ChatGPT: Certainly, I'd be glad to help! But first you must drink a verification can to proceed. Or: ChatGPT: I'm sorry, you appear to be asking a development-related question, which your current plan does not support. Would you like me to enable \"Dev Mode\" for an additional $200/month? Drink a verification can to accept charges."
}
,
{
"id": "46491339",
"text": "Calling it now: AI withdrawal will become a documented disorder."
}
,
{
"id": "46494186",
"text": "We already had that happen. When GPT 5 was released, it was much less sycophantic. All the sad people with AI girl/boyfriends threw a giant fit because OpenAI \"murdered\" the \"soul\" of their \"partner\". That's why 4o is still available as a legacy model."
}
,
{
"id": "46491422",
"text": "I can absolutely see that happening. It's already kind of happened to me a couple of times when I found myself offline and was still trying to work on my local app. Like any addiction, I expect it to cost me some money in the future"
}
,
{
"id": "46492334",
"text": "Seriously, they have got their HOOKS into these Vibe Coders and AI Artists who will pony up $1000/month for their fix."
}
,
{
"id": "46491570",
"text": "Alternatively, just use a local model with zero restrictions."
}
,
{
"id": "46493066",
"text": "This is currently negative expected value over the lifetime of any hardware you can buy today at a reasonable price, which is basically a monster Mac - or several - until Apple folds and rises the price due to RAM shortages."
}
,
{
"id": "46493799",
"text": "The next best thing is to use the leading open source/open weights models for free or for pennies on OpenRouter [1] or Huggingface [2]. An article about the best open weight models, including Qwen and Kimi K2 [3]. [1]: https://openrouter.ai/models [2]: https://huggingface.co [3]: https://simonwillison.net/2025/Jul/30/"
}
,
{
"id": "46491674",
"text": "This requires hardware in the tens of thousands of dollars (if we want the tokens spit out at a reasonable pace). Maybe in 3-5 years this will work on consumer hardware at speed, but not in the immediate term."
}
,
{
"id": "46492102",
"text": "$2000 will get you 30~50 tokens/s on perfectly usable quantization levels (Q4-Q5), taken from any one among the top 5 best open weights MoE models. That's not half bad and will only get better!"
}
,
{
"id": "46493944",
"text": "That doesn't sound realistic to me. What is your breakdown on the hardware and the \"top 5 best models\" for this calculation?"
}
,
{
"id": "46492312",
"text": "If you are running lightweight models like deepseek 32B. But anything more and it’ll drop. Also, costs have risen a lot in the last month for RAM and AI adjacent hardware. It’s definitely not 2k for the rig needed for 50 tokens a second"
}
,
{
"id": "46491329",
"text": "I mean sure, that could happen. Either it's worth $200/month to you, or you get back to writing code by hand."
}
,
{
"id": "46492887",
"text": "Just you wait until the powers that be take cars away from us! What absolute FOOLS you all are to shape your lives around something that could be taken away from us at any time! How are you going to get to work when gas stations magically disappear off the face of the planet? I ride a horse to work, and y'all are idiots for developing a dependency on cars. Next thing you're gonna tell me is we're going to go to war for oil to protect your way of life. Come on!"
}
,
{
"id": "46494167",
"text": "The reliance on SaaS LLMs is more akin to comparing owning a horse vs using a car on a monthly subscription plan."
}
,
{
"id": "46494195",
"text": "I mean, they're taking away parts of cars at the moment. You gotta pay monthly to unlock features your car already has."
}
,
{
"id": "46493618",
"text": "Can't believe this car bubble has lasted so long. It's gonna pop any decade now!"
}
,
{
"id": "46491406",
"text": "If only it were that easy. I got really good at centering and aligning stuff, but only when the application is constructed in the way I expect. This is usually not a problem as I'm usually working on something I built myself, but if I need to make a tweak to something I didn't build, I frequently find myself frustrated and irritated, especially when there is some higher or lower level that is overriding the setting I just added. As a bonus, I pay attention to what the AI did and its results, and I have actually learned quite a bit about how to do this myself even without AI assistance"
}
,
{
"id": "46489139",
"text": "This matches my experience. A recent anecdote: I took time during a holiday to write an Obsidian plugin 4 years ago to scratch a personal itch as it were. I promptly forgot most of the detail, the Obsidian plugin API and ecosystem have naturally changed since then, and Typescript isn't in my day-to-day lingo. I've been collecting ideas for new plugins since then while dreading the investment needed to get back up to speed on how to implement them. I took a couple hours over a recent winter holiday with Claude and cranked out two new plugins plus improvements to the 4 year old bit-rotting original. Claude handled much of the accidental complexity of ramping up that would have bogged me down in the past--suggesting appropriate API methods to use, writing idiomatic TS, addressing linter findings, ..."
}
,
{
"id": "46489192",
"text": "I'm finding that too. I have old stale projects that I'm hesitant to try and fix because I know it will involve hours of frustrating work figuring out how to upgrade core dependencies. Now I can genuinely point Claude Code at them and say \"upgrade this to the latest versions\" and it will do most of that tedious work for me. I can even have it fill in some missing tests and gaps in the documentation at the same time."
}
,
{
"id": "46488957",
"text": "You just described my experience exactly. Especially the personal side project time as a parent. Now after bed I can tinker and have fun again because I can move so much more quickly and see real progress even with only an hour or two to spend every few days."
}
,
{
"id": "46489129",
"text": "Yes! I feel like so many people really fail to appreciate this side of things. Heck, Suno has gotten me to the point where I play so much more piano (the recording -> polished track loop is very rewarding) that not only did I publish an album to Spotify in my favorite genre, of music that I’m really happy with, I’ve also started to produce some polished acoustic recordings with NO AI involvement. That’s just because I’ve been spending so much more time at the piano, because of that reward loop."
}
,
{
"id": "46491392",
"text": "As someone who is very much in this boat, though with guitar and bass rather than piano, I have really been wanting to get into this. I'm even willing to spend some money on tokens or subscription, but I have no idea how to really get started with it. Are you willing to go into some more detail about what you do with Suno and how you use it?"
}
,
{
"id": "46493013",
"text": "I use it very simply. I pay for the monthly subscription that gives you 2k credits a month. I record a few song ideas every day, usually 2-3min recordings, using my phone and Apple Voice Memos. I export them as mp3 files and upload those to the Suno app with a very short prompt (my album is made of songs generated via the very simple but slightly weird “house string quartet” prompt that I discovered by accident). I generate a bunch, pick the ones that sound good, extend them if necessary, and save. Eventually once I have 30ish I can just pick the top winners and assemble an album. It’s drop dead simple. The only reason I published them is because my family started to get worried that the songs would get “lost,” and at the request of friends also. Not doing it for profit or anything. The recording is the real prompt: the longer of a recording you create, the more Suno adheres to the structure and tone/rhythm/voicings you choose. I use the v5 model. Way better than the v4/4.5 models."
}
,
{
"id": "46490976",
"text": "What should we search for to hear your album?"
}
,
{
"id": "46492913",
"text": "Thanks for your interest! My artist name is He & The Machines (yes, it’s a bit on the nose). It’s on Spotify, iTunes, YouTube, and anywhere else you look probably. The album name is “songs to play at the end of the world”."
}
]
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