llm/fa6df919-50f4-440a-804d-6a9d3e9721d8/batch-3-078bf745-64d6-42ae-b4b7-112bcbfb9327-input.json
The following is content for you to classify. Do not respond to the comments—classify them.
<topics>
1. Returning Developers and Parents
Related: People who moved into management or became parents finding AI enables them to code again in short time windows without needing hours to ramp up on forgotten details
2. Productivity Claims Skepticism
Related: Debates over whether 10x productivity gains are real or exaggerated, with critics noting lack of controlled studies and potential for gambling-like dopamine hits from prompting
3. Learning vs Efficiency Tradeoff
Related: Tension between using AI to get things done quickly versus the value of learning through struggle, friction, and hands-on experience with tools and concepts
4. Craft vs Results Orientation
Related: Division between developers who enjoy the process of writing code as craft versus those who see code as means to an end and value outcomes over process
5. Code Review Burden
Related: Concerns that AI shifts work from enjoyable coding to tedious reviewing of AI output, with questions about maintainability and technical debt accumulation
6. Vibe Coding Quality Concerns
Related: Skepticism about code quality from AI assistance, fears of slop, hidden bugs, and unmaintainable codebases that require experienced developers to fix
7. Web Development Complexity
Related: Discussion of whether modern web development is unnecessarily complex with frameworks, bundlers, and toolchains, or if complexity serves legitimate organizational needs
8. Personal Project Renaissance
Related: Stories of developers completing long-postponed side projects, building tools for personal use, and feeling creative freedom with AI assistance
9. Skill Atrophy Fears
Related: Worries that relying on AI will cause developers to lose skills, never develop expertise, and become unable to debug or understand their own systems
10. IKEA Furniture Analogy
Related: Debate comparing AI-assisted coding to assembling IKEA furniture versus carpentry, questioning whether using AI constitutes real development
11. Historical Tech Parallels
Related: Comparisons to printing press disrupting scribes, calculators replacing mental math, and compilers abstracting assembly, debating if AI is similar
12. LLM Usage Skill Requirements
Related: Arguments that getting value from LLMs requires skill, experience to recognize good and bad output, and knowing what questions to ask
13. Simplicity vs Framework Culture
Related: Advocacy for vanilla PHP, plain JavaScript, and avoiding unnecessary complexity, arguing tools exist by choice not necessity
14. Cost and Subscription Concerns
Related: Practical questions about whether $20/month subscriptions are sufficient versus $200/month, and fears of future price increases or feature gating
15. Hallucinations and Reliability
Related: Frustrations with LLMs producing non-existent functions, incorrect code, and requiring extensive verification and correction
16. Race to Bottom Economics
Related: Fears that everyone having access to AI coding will flood markets with competitors, devalue software development, and reduce wages
17. Executive Dysfunction Aid
Related: Theory that AI productivity gains come partly from helping developers overcome starting friction and maintain focus through context switching
18. Boilerplate Liberation
Related: Appreciation for AI handling tedious setup, configuration, documentation, and scaffolding while humans focus on interesting problems
19. Fun Definition Debate
Related: Fundamental disagreement about what makes programming enjoyable - the process of writing code versus seeing results and solving problems
20. Manager Coding Concerns
Related: Criticism of managers using AI to write production code without proper skills, causing incidents and requiring real engineers to fix issues
0. Does not fit well in any category
</topics>
<comments_to_classify>
[
{
"id": "46491174",
"text": "Search “centre a div” in Google\n\nWade through ads\n\nSkim a treatise on the history of centering content\n\nSkim over the “this question is off topic / duplicate” noise if Stack Overflow\n\nFind some code on the page\n\nTry to map how that code will work in the context of your other layout\n\nRealize it’s plain CSS and you’re looking for Tailwind\n\nKeep searching\n\nTry some stuff until it works\n\nOr…\n\nAsk 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.\n\nI 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.\n\nIt also depends on the project. Work code gets a lot more scrutiny than side projects, for example."
}
,
{
"id": "46494592",
"text": "> Search “centre a div” in Google\n\nAaand done. Very first result was a blog post showing all the different ways to do it, old and new, without any preamble."
}
,
{
"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.\n\nGiven 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": "46496358",
"text": "LLMs work very well for a variety of software tasks — we have lots of experience around the industry now.\n\nIf you haven’t been convinced by pure argument in 2026 then you probably won’t be. But the great thing is you don’t have to take anyone’s word for it.\n\nThis isn’t crypto, where everyone using it has a stake in its success.\nYou can just try it, or not."
}
,
{
"id": "46496749",
"text": "That's a lot of words to say \"trust me bruh\" which is kind of poetic given that's the entire model (no pun intended) that LLMs work on."
}
,
{
"id": "46497177",
"text": "Hardly. Just pointing out that water is wet, from my perspective.\n\nBut there is an interesting looking-glass effect at play, where the truth seems obvious and opposite on either side."
}
,
{
"id": "46491308",
"text": "Wait till the VC tap gets shut off.\n\nYou: Hey ChatGPT, help me center a div.\n\nChatGPT: Certainly, I'd be glad to help! But first you must drink a verification can to proceed.\n\nOr:\n\nChatGPT: 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": "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": "46496006",
"text": "A little hypothesis: a lot of .Net and Java stuff is mainlined from a giant mega corp straight to developers through a curated certification, MVP, blogging, and conference circuit apparatus designed to create unquestioned corporate friendly, highly profitable, dogma. You say ‘website’ and from the letter ‘b’ they’re having a Pavlovian response (“ Azure hosted SharePoint, data lake, MSSQL, user directory, analytics, PowerBI, and… ”).\n\nMicrosoft’s dedication to infusing OpenAI tech into everything seems like a play to cut even those tepid brains out of the loop and capture the vehicles of planning and production. Training your workforce to be dependent on third-party thinking, planning, and advice is an interesting strategy."
}
,
{
"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": "46491570",
"text": "Alternatively, just use a local model with zero restrictions."
}
,
{
"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].\n\nAn article about the best open weight models, including Qwen and Kimi K2 [3].\n\n[1]: https://openrouter.ai/models\n\n[2]: https://huggingface.co\n\n[3]: https://simonwillison.net/2025/Jul/30/"
}
,
{
"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": "46491674",
"text": "This requires hardware in the tens of thousands of dollars (if we want the tokens spit out at a reasonable pace).\n\nMaybe 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": "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": "46496462",
"text": "Could you explain how? I can't seem to figure it out.\n\nDeepSeek-V3.2-Exp has 37B active parameters, GLM-4.7 and Kimi K2 have 32B active parameters.\n\nLets say we are dealing with Q4_K_S quantization for roughly half the size, we still need to move 16 GB 30 times per second, which requires a memory bandwidth of 480 GB/s, or maybe half that if speculative decoding works really well.\n\nAnything GPU-based won't work for that speed, because PCIe 5 provides only 64 GB/s and $2000 can not afford enough VRAM (~256GB) for a full model.\n\nThat leaves CPU-based systems with high memory bandwidth. DDR5 would work (somewhere around 300 GB/s with 8x 4800MHz modules), but that would cost about twice as much for just the RAM alone, disregarding the rest of the system.\n\nCan you get enough memory bandwidth out of DDR4 somehow?"
}
,
{
"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": "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.\n\nCome on!"
}
,
{
"id": "46499547",
"text": "This is a poor analogy. Cars (mostly) don't require a subscription."
}
,
{
"id": "46493618",
"text": "Can't believe this car bubble has lasted so long. It's gonna pop any decade now!"
}
,
{
"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": "46496761",
"text": "Just like the comment you replied to this is an argument against subscription model \"thing\" as a service business models, not against cars."
}
,
{
"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.\n\nAs 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:\n\nI 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.\n\nI'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.\n\nI 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": "46496267",
"text": "Another anecdote: I built my first Android app in less than a dozen hours over the holiday, tailored for a specific need I have. I do have many years of experience with Java, C# and JS (Angular), but have never coded anything for mobile. Gemini helped me figure out how to set up a Kotlin app with a reasonable architecture (Hilt for dependency injection, etc). It also helped me find Material3 components and set up the UI in a way that looks not too bad, especially considering my lack of design skills. The whole project was a real joy to do, and I have a couple of more ideas that I'm going to implement over the coming months.\n\nAs a father of three with a busy life, this would've simply been impossible a couple of years ago."
}
,
{
"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.\n\nNow 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.\n\nI can even have it fill in some missing tests and gaps in the documentation at the same time."
}
,
{
"id": "46496177",
"text": "> You don't need to carve out 2-4 hours to ramp up any more.\n\nYes. That used to require difficult decision making: “Can I do this and how long will it take?” was a significant cognitive load and source of stress. This was especially true when it became clear something was going to take days not hours, having expended a lot of effort already.\n\nEven more frustrating was having to implement hacks due to time constraints when I knew a couple more hours would obviate that need.\n\nNow I know within a couple of minutes if something is feasible or not and decision fatigue is much lower."
}
,
{
"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.\n\nHeck, 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.\n\nAre 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).\n\nI 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.\n\nThe 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.\n\nThe 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.\n\nI 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!\n\nMy 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.\n\nThe album name is “songs to play at the end of the world”."
}
,
{
"id": "46490242",
"text": "I’ve noticed this too at work.\n\nIf keep the change’s focused I can iterate far faster with ideas because it can type faster than I can."
}
,
{
"id": "46491312",
"text": "Yep, have seen this myself as previously a manager and now with a young family.\n\nI can make incredible progress on side-projects that I never would have started with only 2-4 hours carved out over the course of a week.\n\nThere is a hopefully a Jevon's paradox here that we will have a bloom of side-projects, \"what-if\" / \"if only I had the time\" type projects come to fruition."
}
,
{
"id": "46491816",
"text": "This is exactly the case. Businesses in the past wouldn't automate some process because they couldn't afford to develop it. Now they can! Which frees up resources to tackle something else on the backlog. It's pretty exciting."
}
,
{
"id": "46495298",
"text": "It all comes back to \"Do more because of AI\" rather than \"Do less because of AI\".\n\nGetting back into coding is doing more. Updating an old project to the latest libraries is doing more.\n\nIt often feels ambiguous. Shipping a buggy, vibe-coded MVP might be doing less. But getting customer feedback on day one from a real tangible product can allow you to build a richer and deeper experience through fast iteration.\n\nJust make sure we're doing more, not less, and AI is a wonderful step forward."
}
,
{
"id": "46496877",
"text": "> lost their personal side project time\n\nYes !\n\n> moved into management roles\n\nPlease stop. Except if \"coding\" is making PoCs.\n\nIf it's actual code that runs important stuffs in production: either one cares enough to understand all the ins and outs and going into managements didn't cut them from coding, either they're only pushing what they see as \"good enough\" code while their team starts polishing resumes and they probably have a better output doing management.\n\nPS: if you only have half an hour for writing something, will you have 3h rolling it back and dealing with the issues produced when stuff goes sideways ? I really don't get the logic."
}
,
{
"id": "46497019",
"text": "A common policy I've seen from\nengineering managers who code (and one I've stuck to myself when I've been in engineering management roles) is to avoid writing code that's on the critical path to shipping.\n\nThat's means your team should never be blocked on code that you are responsible for, because as an engineering manager you can rarely commit dedicated coding time to unblocking them.\n\nThis still leaves space for quite a few categories of coding:\n\n- prototypes and proof of concepts\n\n- internal \"nice to have\" tools that increase developer quality of life (I ended up hacking on plenty of these)\n\n- helping debug issues"
}
,
{
"id": "46490784",
"text": "I was very anti AI (mainly because I am scared that I'll take my job). I did a side project that would have took me weeks in just two days. I deployed it. It's there, waiting for customers now.\n\nI felt in love with the process to be honest. I complained my wife yesterday: \"my only problem now is that I don't have enough time and money to pay all the servers\", because it opened to me the opportunities to develop and deploy a lot of new ideas."
}
,
{
"id": "46491042",
"text": "Aren't you afraid it's gonna be a race to the bottom ? the software industry is now whoever pays gemini to deploy something prompted in a few days. Everybody can, so the market will be inundated by a lot of people, and usually this makes for a bad market (a few shiny one gets 90% of the share while the rest fight for breadcrumbs)\n\nI'm personally more afraid that stupid sales oriented will take my job instead of losing it to solid teams of dedicated expert that invested a lot of skills in making something on their own. it seems like value inversion"
}
,
{
"id": "46491374",
"text": "Yes, I worry about this quite a bit. Obviously nobody knows yet how it will shake out, but what I've been noticing so far is that brand recognition is becoming more important. This is obviously not a good thing for startup yokels like me, but it does provide an opportunity for quality and brand building.\n\nThe initial creation and generation is indeed much easier now, but testing, identifying, and fixing bugs is still very much a process that takes some investment and effort, even when AI assisted. There is also considerable room for differentiation among user flows and the way people interact with the app. AI is not good at this yet, so the prompter needs to be able to identify and direct these efforts.\n\nI've also noticed in some of my projects, even ones shipped into production in a professional environment, there are lots of hard to fix and mostly annoying bugs that just aren't worth it, or that take so much research and debugging effort that we eventually gave up and accepted the downsides. If you give the AI enough guidance to know what to hunt for, it is getting pretty good at finding these things. Often the suggested fix is a terrible idea, but The AI will usually tell you enough about what is wrong that you can use your existing software engineering skills and experience to figure out a good path forward. At that point you can either fix it yourself, or prompt the AI to do it. My success rate doing this is still only at about 50%, but that's half the bugs that we used to live with that we no longer do, which in my opinion has been a huge positive development."
}
,
{
"id": "46495603",
"text": "My prediction is that software will be so cheap that very soon, economy of scale gives way to maximum customization which means everyone writes their own software. There will be no software market in the future."
}
]
</comments_to_classify>
Based on the comments above, assign each to up to 3 relevant topics.
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
]
}
,
{
"id": "comment_id_3",
"topics": [
0
]
}
,
...
]
Rules:
- Each comment can have 0 to 3 topics
- Use 1-based topic indices for matches
- Use index 0 if the comment does not fit well in any category
- Only assign topics that are genuinely relevant to the comment
Remember: Output ONLY the JSON array, no other text.
50