llm/fa6df919-50f4-440a-804d-6a9d3e9721d8/batch-5-a22c60b2-4656-4bd2-ae8b-c13ddb763a35-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": "46489266",
"text": "The difference is that the head chef can cook very well and could do a better job of the dish than the trainee."
}
,
{
"id": "46489310",
"text": "\"head chef\" is a managerial position but yes often they can and do cook."
}
,
{
"id": "46489219",
"text": "To differentiate him from the \"cook\", which is what we call those who carry out the actual act of cooking."
}
,
{
"id": "46489236",
"text": "Well, don’t go around calling me a compiler!"
}
,
{
"id": "46489304",
"text": "If that's what you do, then the name is perfectly apt. Why shy away from what you are?"
}
,
{
"id": "46491075",
"text": "They're not moving back into development. They're adopting a new approach of producing software, which has nothing to do with the work that software developers do. It's likely that they \"left\" the field because they were more interested in other roles, which is fine.\n\nSo now that we have tools that promise to offload the work a software developer does, there are more people interested in simply producing software, and skipping all of that \"busy work\".\n\nThe idea that this is the same as software development is akin to thinking that assembling IKEA furniture makes you a carpenter."
}
,
{
"id": "46491562",
"text": "That IKEA analogy is pretty good, because plenty of people use IKEA furniture to solve the \"I need a bookshelf\" problem - and often enjoy the process - without feeling like they should call themselves a carpenter.\n\nI bet there are professional carpenters out there who occasionally assemble an IKEA bookshelf because they need something quick and don't want to spend hours building one themselves from scratch."
}
,
{
"id": "46493248",
"text": "Definitely. I'm not disparaging the process of assembling IKEA furniture, nor the process of producing software using LLMs. I've done both, and they have their time and place.\n\nWhat I'm pushing back on is the idea that these are equivalent to carpentry and programming. I think we need new terminology to describe this new process. \"Vibe coding\" is at the extreme end of it, and \"LLM-assisted software development\" is a mouthful.\n\nAlthough, the IKEA analogy could be more accurate: the assembly instructions can be wrong; some screws may be missing; you ordered an office chair and got a dining chair; a desk may have five legs; etc. Also, the thing you built is made out of hollow MDF, and will collapse under moderate levels of stress. And if you don't have prior experience building furniture, you end up with no usable skills to modify the end result beyond the manufacturer's original specifications.\n\nSo, sure, the seemingly quick and easy process might be convenient when it works. Though I've found that it often requires more time and effort to produce what I want, and I end up with a lackluster product, and no learned skills to show for it. Thus learning the difficult process is a more rewarding long-term investment if you plan to continue building software or furniture in the future. :)"
}
,
{
"id": "46492964",
"text": "Little bit of a sweeping generalization there. There are a huge range of ways in which LLMs are being leveraged for software development.\n\nUsing a drill doesn’t make you any less of a carpenter, even if you stopped using a screwdriver because your wrists are shot."
}
,
{
"id": "46491327",
"text": "It's called being a systems analyst or product manager. Upskill into these roles (while still accepting individual contributor pay) or get left behind."
}
,
{
"id": "46494792",
"text": "Do you see any reason why AI and software will not soon take over system analyst or product manager roles? If we can go from natural language prompt to working code, it seems like not too big of a step to set up a system that goes straight from user feedback to code changes."
}
,
{
"id": "46491518",
"text": "I'm sorry, \"upskill\"? The roles you mentioned don't require any more advanced skills than those required for software development—just a different set of skills.\n\nAnd an IC is not \"left behind\" if those roles don't interest them. What a ridiculous thing to say. A systems analyst or product manager is not a natural progression for someone who enjoys software development."
}
,
{
"id": "46489115",
"text": "I was just getting pretty sick and tired of programming, instead now AI can write the code down while I do the fun things of figuring out how shit works and general device hacking + home projects"
}
,
{
"id": "46491983",
"text": "What do LLM's have to do returning to coding?\n\nJust...\n\n...write the code. Stop being lazy."
}
,
{
"id": "46493068",
"text": "Yes, people who were at best average engineers and those that atrophied at their skill through lack of practice seem to be the biggest AI fanboys in my social media.\n\nIt's telling, isn't it?"
}
,
{
"id": "46490981",
"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.\n\nYou only have those things if you choose to use them.\n\nI've been building websites for 25 years. I use the same core technologies today that I did when I started. Sure, I make use of modern improvements to the languages themselves, but I have never permanently adopted any of the \"hot new trends\" and feel I am better - or at least saner - for it.\n\nNo, your marketing or e-commerce website almost certainly doesn't need a JS bundling toolchain. It almost certainly doesn't need a CSS preprocessor or even a CSS boilerplate/framework. It almost certainly doesn't need an enterprise-class PHP framework; or a dependency manager; or a CI/CD pipeline."
}
,
{
"id": "46491165",
"text": "Those technologies don't just solve tech issues, they solve organizational issues. If one or two people manage a website, going without fancy tooling is completely fine. When 1000 people are managing a product with complex business logic across multiple platforms, you need fancy tooling to ensure everyone can work at a reasonable level of productivity."
}
,
{
"id": "46494327",
"text": "> you need fancy tooling to ensure everyone can work at a reasonable level of productivity.\n\nIf you have a thousand people working on a single product, yes, but you also have the resources to have dedicated tool support teams at that level. In my experience, if you’re under multiple dozens of developers or not everyone works on all of your projects, the tools fragment because people aren’t combining or configuring them the same way and there’s enough churn in the front-end tool space that you’ll hit various compatibility issues which lower the effectiveness of sharing across projects. This is especially true if you’ve hired people who self-identify as, say, Next or Tailwind developers rather than web developers and lack the understanding of the underlying technology to fix complex problems."
}
,
{
"id": "46491854",
"text": "The article is about developing as a solo developer."
}
,
{
"id": "46493435",
"text": "> build pipelines, bundlers, CSS frameworks with their own toolchains, progressive web apps, Core Web Vitals, SEO, layout shifts, srcset/responsive images\n\nBuild pipelines are purely a technical decision. Bundlers are purely a technical decision (TBH, a non-brainer if you decide to have a build pipeline, but it's not an organizational helper). Those help one do some things, not several people to organize.\n\nI'm still waiting for any person to claim they made CSS maintainable by adopting a framework. It's an almost purely organizational decision with no upsides at all.\n\nPWAs are a product decision, not technical or organizational. The same applies to Core Web Vitals, SEO, layout shifts and srcset, those are all product decisions.\n\nYou can escape the technical and organizational decisions. You can't escape the product ones."
}
,
{
"id": "46497948",
"text": "This is why web development stopped being fun: developers that cannot manage or train people and instead hope garbage like jQuery will simply act as a surrogate parent."
}
,
{
"id": "46491029",
"text": "What are you using? If you don't mind me asking."
}
,
{
"id": "46491136",
"text": "It's so weird to see this take repeated over and over. I have to assume you have never written a large scale project for the web? The only part where I agree is that you don't need PHP or server-side rendering in general."
}
,
{
"id": "46492209",
"text": "Nowhere he talked about large scale projects and the article neither btw. I am sure his choices are different when working on a large scale project."
}
,
{
"id": "46496175",
"text": "> I have to assume you have never written a large scale project for the web?\n\nCan I ask, what classifies as large scale project for the web?\n\nI previously created and exited a trading platform that did billions in transactions via our servers with thousands of users streaming real time data. It's certainly more complicated and \"larger\" than 99.9% of things you'll ever do. So does that qualify?\n\nIf so, I can tell you that I did it with PHP and no JS frameworks. Hosted on a couple of VPS servers from digital ocean. From idea to execution to exit in ~9 months.\n\nYou know what the weird part is? I see your take repeated over and over by \"shovel peddlers\" and grifters. And every single time it comes with 0 substance or merit."
}
,
{
"id": "46496277",
"text": "> I can tell you that I did it\n\nThe 'I' here reveals that this is indeed not a large scale project, though perhaps impressive. When working on a piece of software with tens of people, using more tooling really does makes sense."
}
,
{
"id": "46496458",
"text": "'I' here reveals that it is on topic in context of posted article. Which is purpose of this thread.\n\nSorry I do not want to sound like a dick re-stating the obvious but threads often are going off the rails and I find it bit absurd."
}
,
{
"id": "46501358",
"text": "I've tried to parse your comment from various perspectives, but can't seem to make sense of it.\n\nA 9-person-month project is just not a large scale project by any definition."
}
,
{
"id": "46499919",
"text": "Congrats to you, but yeah the other comments have already said it.\n\nI'm talking about projects that have a lot of people working together across multiple teams where not everyone is even a dev. This is routine with e-commerce. The build will have assets from design teams, copywriters, analytics scripts, etc. and a CMS isn't always the correct or even scalable solution for that. The original commenter I was replying to seems to be stuck in the past. These days it can all be done with a simple CI script, but yeah ultimately that means build tools.\n\nAbove all else, like I said in another comment, there cannot be server-side rendering because it deploys to a CDN for hosting. These are projects that require huge amounts of content, but need to stay responsive. The final build result and upload is many files, but the initial load for the site is minimal JS and HTML to render for the user.\n\n> billions in transactions via our servers with thousands of users streaming real time data. It's certainly more complicated and \"larger\" than 99.9% of things you'll ever do.\n\nLarge scale doesn't have to be complicated, but it does need some way to coordinate the effort which means there's a build and there will be requirements that are beyond any one person's control and expected for the modern web.\n\nI want to also point out the obvious that there's insane money being made in e-commerce since it's now the default way to shop for everyone. It's a very common type of web project and if the typical HN web dev is getting paid a decent salary it's likely that the sites they maintain have several orders of magnitude more users than what you're talking about."
}
,
{
"id": "46491361",
"text": "I used to think the same about server-side rendering until I more closely looked at React SSR.\n\nI think it makes a lot of sense and allows for faster initial rendering of the page while automatically setting up the JS and interactivity in the background."
}
,
{
"id": "46499594",
"text": "React has always supported server-side rendering and there have been many tools over the years to \"rehydrate\" data from the server to the client for when the client-side React application \"takes over\"."
}
,
{
"id": "46491566",
"text": "Couldn't you just static render the parts that you're using SSR for?\n\nI am not trying to be dismissive, but a common strict requirement is static hosting from a CDN, embedded environments, etc."
}
,
{
"id": "46492574",
"text": "If you static render, it won't be an interactive application.\n\nWith React SSR you get the best of both: stream static HTML chunks immediately, and rehydrate with JS later, prioritizing components the user interacts with.\n\nIt should load quicker compared to traditional React apps where the browser loads the HTML, then loads the JS bundle, and only then renders a loading skeleton while likely triggering more requests for data."
}
,
{
"id": "46494275",
"text": "> It should load quicker compared to traditional React apps where the browser loads the HTML, then loads the JS bundle, and only then renders a loading skeleton while likely triggering more requests for data.\n\nThen your JS bundle is broken.\n\nPromises exist. Modules exist. HTTP/2+ exists. You can load data while you are loading a small amount of JS required to render that data while you are loading other parts of your JS.\n\nIf everything is sequential: load giant JS bundle -> fetch -> render, that's because someone architected it like that. Browsers give you all the tools you need to load in parallel, if you don't use them then it's not the browser's fault.\n\nYou do not need SSR or rehydration. That's just Vercel propaganda. They saw that people are doing a stupid thing and decided to push a complex solution to it. Why? It makes them money."
}
,
{
"id": "46496744",
"text": "You cannot load any data in a regular React application before you loaded both React and your React components that trigger the fetch.\n\nIf you use code splitting, your initial bundle size can be smaller, yes. That's about it.\n\nI guess in theory you can hack together static loading skeletons that you then remove when React loaded your initial bundle, but that's certainly far from a common approach. By that standard, the vast majority of JS bundles would be \"broken\"."
}
,
{
"id": "46493308",
"text": "You seem to be confused about your terms, both SSR and SSG can rehydrate and become interactive, you only need SSR if you have personalized content that must be fetched on an actual user request, and with frameworks like astro introducing island concept it even let's you mix SSG and SSR content on a single page."
}
,
{
"id": "46496856",
"text": "That depends on how you interpret \"static render\".\n\nI did not interpret that as React SSG. SSG is the default behavior of NextJS unless you dynamically fetch data, turning it into SSR automatically.\n\nWhat I thought of is React's \"renderToString()\" at build time which will produce static HTML with event handlers stripped, in preparation for a later \"hydrateRoot()\" on the client side."
}
,
{
"id": "46503188",
"text": "> That depends on how you interpret \"static render\".\n\nIt only depends if you interpret it incorrectly."
}
,
{
"id": "46492855",
"text": "Static rendering has nothing to do with interactivity in a web app.\n\nI guess if you're already so deeply entrenched in writing all your application logic on the server side you need React SSR, but that sounds miserable."
}
,
{
"id": "46489004",
"text": "I remember those times, and it was a lot of fun, but there's really nothing stopping you from running a LAMP stack today, writing PHP without frameworks and with manual SQL queries.\n\nIn fact, it's a lot more fun for me to approach this today. Modern PHP is a joy. MariaSQL is very much MySQL (and switching to Postgres isn't exactly a bump in complexity). It's way easier to write code that won't get injected.\n\nIf you want to slice your designs in Photoshop (ehem, the real OGs used Fireworks) go ahead and use Dreamweaver, go ahead. That said, HTML5 makes not having to use tables for layout easy, not more complex and VS Code has all the good parts of Dreamweaver (trust me, you don't need or want the WYSIWG... if you must, just use inspect elements and move the changes over to the HTML file).\n\nI guess all this is to say that web dev is simpler, not more complex for solo devs today. There exists more complicated tooling, but if you're solo-dev'ing something for fun, skip it!\n\nEDIT: Also, phpMyAdmin was fun to use but also the best way to get your box popped. Today, something like DBeaver suits me just fine."
}
,
{
"id": "46495851",
"text": "> ehem, the real OGs used Fireworks\n\nMan I missed Macromedia Fireworks. Such a great time! I think I had the last bundle before the Adobe buy-out, Macromedia Studio I think it was called? So good!"
}
,
{
"id": "46496203",
"text": "I still write vanilla PHP with SQL queries. And with all the modern PHP features, things have never been faster or more joyful to work with.\n\nI honestly feel bad for people who fall victims to complexity. It burns you out when all you need is to keep things simple and fun. Life is too short for anything else."
}
,
{
"id": "46497000",
"text": "> but also the best way to get your box popped\n\nwhat do you mean? why?"
}
,
{
"id": "46499566",
"text": "https://www.cve.org/CVERecord/SearchResults?query=phpmyadmin\n\nSort by oldest to newest"
}
,
{
"id": "46490902",
"text": "> Even with refinement and back-and-forth prompting, I’m easily 10x more productive\n\nDevelopers notoriously overestimate the productivity gains of AI, especially because it's akin to gambling every time you make a prompt, hoping for the AI's output to work.\n\nI'd be shocked if the developer wasn't actually less productive."
}
,
{
"id": "46496339",
"text": "For personal projects, 10x is a lower bound. This year alone I got several projects done that had been on my mind for years .\n\nThe baseline isn't what it would have taken had I set aside time to do it.[1] The baseline is reality . I'm easily getting 10x more projects done than in the past.\n\nFor work, I totally agree with you.\n\n[1] Although it's often true even in this case. My first such project was done in 15 minutes. Conceptually it was an easy project. Had I known all the libraries, etc out would have taken about an hour. But I didn't, and the research alone would have taken hours.\n\nAnd most of the knowledge acquired from that research would likely be useless."
}
,
{
"id": "46490979",
"text": "I accept there are productivity gains, but it's hard to take \"10x\" seriously. It's such a tired trope. Is no one humble enough to be a meager 2.5x engineer?"
}
,
{
"id": "46491027",
"text": "Even 2.5x is absurd. If they said 1.5x I might believe them."
}
,
{
"id": "46491149",
"text": "I'm building an AI agent for Godot, and in paid user testing we found the median speed up time to complete a variety of tasks[0] was 2x. This number was closer to 10x for less experienced engineers\n\n[0] tasks included making games from scratch and resolving bugs we put into template projects. There's no perfect tasks to test on, but this seemed sufficient"
}
,
{
"id": "46494591",
"text": "Have you evaluated the maintainability of the generated code? Becuause that could of course start to count in the negative direction over time.\n\nSome of the AI generated I've seen has been decent quality, but almost all of it is much more verbose or just greater in quantity than hand written code is/would be. And that's almost always what you don't want for maintenance..."
}
]
</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