llm/122b8d72-a8a3-4fcf-8eca-6a52786d1a8b/batch-2-20e34927-245d-4566-a534-f219044a4481-input.json
The following is content for you to classify. Do not respond to the comments—classify them.
<topics>
1. Lack of Concrete Evidence
Related: Commenters repeatedly criticize the article for providing no examples, code, projects, costs, or specifics about what was actually built, calling it empty hype and platitudes without substance or proof of claims
2. Author Credibility Concerns
Related: Multiple commenters point to the author's previous blog post praising the Rabbit R1 as evidence of poor technical judgment and tendency toward unfounded enthusiasm for new technology
3. AI Coding Tool Limitations
Related: Discussion of how AI tools work well for simple, repetitive, or locally-scoped tasks but fail with complex systems, large codebases, and non-trivial problems requiring significant human guidance
4. Greenfield vs Legacy Projects
Related: Observations that AI coding excels at new projects under 10,000 lines of code but struggles maintaining consistency and avoiding regressions in larger, established codebases
5. Astroturfing Suspicions
Related: Multiple commenters suspect pro-AI posts are marketing campaigns or astroturfing given the billions invested in AI, with some noting suspicious voting patterns and repetitive promotional content
6. AI-Generated Content Detection
Related: Many suspect the blog post itself was written by AI, citing lack of specifics, excessive em-dashes, and generic promotional language characteristic of LLM-generated slop
7. Manager Fantasy Critique
Related: Skepticism about the desire to become a 'super manager' rather than hands-on developer, with some viewing it as CEO cosplay or escapism from actual technical work
8. Productivity Illusion
Related: Discussion of whether AI tools create actual productivity gains or merely the feeling of productivity, with some noting impressive-looking output that lacks substance or quality
9. Security Concerns
Related: Significant worry about OpenClaw's security vulnerabilities, prompt injection risks, and the danger of giving AI agents access to production systems, emails, and sensitive data
10. Skills and Learning Curve
Related: Debate over whether effective AI tool usage requires significant skill development, with some arguing poor results indicate user skill issues while others see fundamental tool limitations
11. Real World Use Cases
Related: Commenters share legitimate use cases including utility scripts, exploring unfamiliar codebases, setup automation, and learning new tools, distinguishing these from transformative claims
12. Cost and Accessibility
Related: Discussion of the financial barriers including expensive subscriptions, Mac Mini hardware, and token costs that contradict claims of democratizing technology
13. AI Hype Cycle
Related: Observations that we're at the apex of AI hype, with predictions the bubble will pop and more realistic assessments will emerge over time
14. Context Window Problems
Related: Technical discussion of how AI agents lose coherence as context grows, with compaction causing confusion and requiring human redirection
15. Testing and Verification
Related: Emphasis on the need for humans to verify AI output, run tests, and maintain quality control since AI cannot reliably check its own work
16. Language-Specific Performance
Related: Observations that AI performs better with some programming languages like Python and JavaScript compared to Java, Scala, or enterprise frameworks
17. Engineering vs Management
Related: Philosophical debate about why engineers want to become managers, whether it's about power, career progression, avoiding obsolescence, or building bigger things
18. Model Selection Matters
Related: Discussion of significant quality differences between AI models, with frontier models like Opus and GPT-5.2 performing notably better than cheaper alternatives
19. Workflow Integration Tips
Related: Practical advice including using AGENTS.md files, breaking tasks into smaller chunks, brainstorming with agents, and having separate contexts for review and implementation
20. Vibe Coding Skepticism
Related: Criticism of fully autonomous AI coding without understanding the output, with warnings about technical debt, logical errors, and unmaintainable code accumulation
0. Does not fit well in any category
</topics>
<comments_to_classify>
[
{
"id": "46937292",
"text": "And I would argue that what you are describing is why we end up in a system where the people who are talented and have in depth knowledge end up in \"dumber ~ managerial\" roles and we end up losing real talent and knowledge because of the incentives you explicitly describe.\n\nIf only the world incentivized ICs with depth of knowledge to stay in those roles for the long haul instead of chopping off our knowledge of specificity at the apex of their depth of knowledge. So many managers have no talent, no depth of knowledge and a passable ability to manage people."
}
,
{
"id": "46937350",
"text": "Many ICs have no talent or depth of knowledge, I don’t think thats a criticism unique to managers."
}
,
{
"id": "46937736",
"text": "> only to have it completely obsoleted a few years later?\n\nThat sure beats having it completely obsoleted a few weeks later, which sometimes feels like the situation with AI"
}
,
{
"id": "46937200",
"text": "Thank you for adding color. This is the exact reason why I want to get in to management. Sadly, I am just not cut out to manage people. Nowadays, my role is more of a hybrid between Principal and EM, which may be awkward at times. If it weren't for excellent PM & PgM, I'd be stretching myself too thin."
}
,
{
"id": "46937452",
"text": "Why aren't you cut out?\n\nIt's a skill that takes practice -coordinating disparate people and groups, creating communication where you notice they're not talking to each other, creating or fixing processes that annoy or cause chaos if they're not there, encouraging people, being a therapist, seeing what's not there and pushing a vision while you get the group to go along, protecting people from management above and pressures around, etc are mostly skills that you learn.\n\nSometimes no one will give you feedback so you have to figure it out yourself (unless you're lucky to get a mentor), so you just have to throw yourself in and give yourself grace to fail and succeed over time.\n\nThe only skill of these I think is possibly genetic or innate, is being able to see the big picture and make strategical decisions. A lot of tech people skew cognitively in narrow areas, and have trouble conceptualizing the world beyond.\n\nOne challenge here is the ubiquitous 'managers just approve vacations and waste space' sentiment on here and in some places. These people are a chore to manage (and sometimes are better not being present in your group)."
}
,
{
"id": "46937364",
"text": "> if you want to build big things, involving many people, you need to be in management.\n\nNo, you don’t.\nYou need some kind of decision making and communication process but a separate management is not necessary."
}
,
{
"id": "46937422",
"text": "How will the widget get built if we don’t have someone stack ranking us?"
}
,
{
"id": "46937485",
"text": "Since when do your line managers choose to stack rank?\n\nDo you know what stank ranking even is and where it comes from? If you have to rate your group from 1 to 5, each individual, and you rate them all 4s and 5s, they crack down and force you to select a 2 and a 3 and only have one 5. Now, would you prefer a CFO, CTO or even a project manager be the one to do it? It's a weird comment."
}
,
{
"id": "46937862",
"text": "Weirder that you think every group has a 2 and exactly one 5. You don't see the problem with that?"
}
,
{
"id": "46938844",
"text": "Re-read and think about what was written - the 2s aren'tcoming from the line managers, you're barking up the wrong tree in the stack ranking process. I just explained that stack ranking gets scaled and adjusted by the brass, and I just in this example rated everyone a 4 and 5.\n\nAgain, as an older manager today, I can see myself in my 20s in the resistance and stubbornness to 'how corporations work' espoused in comments like yours. I sympathize, but I warn you against being naive and ideological, because unfortunately human groups be human groups, and organizations for better or for worse behave in predictable patterns. You might as well know as much as possible so you can deal with it better."
}
,
{
"id": "46938990",
"text": "Do you think every group of people contains someone who is operating at 40%?"
}
,
{
"id": "46939087",
"text": "Nope! In fact I think stack ranking is horrible. But you missed the point I was making (and then re-made). I think you read 40% of what I wrote."
}
,
{
"id": "46937788",
"text": "Weirder that you think software couldn’t get built without a CFO. The GP comment was noting that management is an outcome of capital wanting more control, not because many layers of middle managers is a naturally optimal way to complete software projects"
}
,
{
"id": "46938944",
"text": "CFOs manage budgets and funding and things tech people don't. I hate to parrot your tone but, weirder that you think software can be built in a company without there being a budget of some kind."
}
,
{
"id": "46937577",
"text": "Can you go into more detail?"
}
,
{
"id": "46939177",
"text": "I have worked at organizations where most engineering and many product decisions were made bottom-up, through written RFDs and ADRs, and horizontal conversations between lead, staff and principal engineers. The tradeoff is that it can take weeks, months or years to both agree or schedule work on larger projects, where other (especially small) organizations might take hours to weeks."
}
,
{
"id": "46941549",
"text": "> My guess is that the drive is toward power\n\nNot really for me. Programming is an effort type job. The more effort you put in the more you get out. True in other professions sure but multiplied with dev work. When became a dad everything changed. Solve hard problem or spend time with kid. I couldn't juggle the two. So i made a choice and fortunately had an opportunity to move into management.\n\nAnyway full circle now I'm back to being a dev and this go around couldn't be easier with our ai agents. Point is I went into management because I was forced, not at all for power."
}
,
{
"id": "46937071",
"text": "I actually don’t think the author wants to become a real manager, he wants to play a video game where he sends NPCs around to do stuff.\n\nReal managers deal with coaching, ownership, feelings, politics, communication, consensus building, etc. The people who are good at it like setting other people up to win."
}
,
{
"id": "46938444",
"text": "As a manager who is trying to do all the things you listed well, I would love it to be more like a game sending NPCs around. Ignoring the macro implications of AI, even if very successful at or resistant to it, I’d think there would be very, very few people who are actively seeking people drama. Educating kids can be fun, but educating adults in the business domain is almost always a drag as in any given professional room, you would be very lucky to find one person who is genuinely there out of curiosity rather than obligation or fomo."
}
,
{
"id": "46938984",
"text": "I think you might have missed the point\n\n> I’d think there would be very, very few people who are actively seeking people drama\n\nTheoretically as a manager you get the bump up the power dynamic ladder (and probably pay ladder) because you are taking on the responsibility of \"people drama\". Being a good manager is antithetical to treating living, breathing human beings as NPCs in a game."
}
,
{
"id": "46937949",
"text": "As an engineer, I can never actually let a system write code on behalf of me with the level of complacency I've accumulated over the years. I always have opinionated design decisions, variable naming practices. It's memorable, relatable, repeatable across N projects. Sure, you can argue that you can feed all this into the context, but I've found most models to hallucinate and make things unnecessarily opaque and complex. And then, I eventually have to spend time cleaning up all that mess. OP claims they can tell the model over the phone what to do and it does it. Good for OP, but I've never personally had that level of success with my own product development workflow. It sounds too good to be true if this level of autonomy is even possible today without the AI fucking something up."
}
,
{
"id": "46936815",
"text": "Once you've written enough image caches, I think you often find yourself ready to move on to the higher level architecture of a larger project.\n\nOften too it's the architecture that can cause a grand idea to crash and burn—experienced devs should be moving toward solving those problems."
}
,
{
"id": "46938177",
"text": "Some people want the thing done more than they want to do the thing. That gets to extremes of exploitative parasitic behavior, but it's true at much less obnoxious scales: ever used a programming language's standard library instead of inventing your own _whatever_? Probably a yes.\n\nThat can extend to arbitrary absurdity. You are probably not growing your own food, mining your own ore, forging your own tools, etc etc etc.\n\nIt's all just a matter of where you rely on external tools/abstractions to do parts of the work you don't want to do yourself."
}
,
{
"id": "46937204",
"text": "For me, getting into management was less about feeling bogged down in the specifics, but more about control (directed mostly above). Anyone who’s had a bad manager or bad decisions they need to adhere to might be familiar with the feeling that caused me to dip my toes into management.\n\nLike I’ve been in situations as an IC where poor leadership from above has literally caused less efficient and more painful day-to-day work. I always hoped I could sway those decisions from my position as an IC, but reality rarely aligned with that hope.\n\nI actually love the details, but I just don’t get too deep into them these days as I don’t want to micro-manage.\n\nI do find I have more say in things my team deals with now that I’m a manager."
}
,
{
"id": "46938499",
"text": "Asking as a fellow manager - do you ever wonder some of the people you manage might be thinking of you in the same way? Someone making terrible decisions, making them less efficient? And, have you ever noticed that something you strongly pushed back when you were an IC did not matter, or was actually the right thing in retrospect?"
}
,
{
"id": "46941627",
"text": "I used to be so deeply annoyed with leadership decisions as an IC. When I got into management my attitude completely shifted. Leadership only cares about shipping code. Thinking they care about anything else and you're fooling yourself. So whatever your team cares about your decisions doesn't matter. Are they shipping code? All good. Team dynamics will work itself out as long as you're pushing to main.\n\nNow I'm back to being an IC and I just do the job. Want me to change this variable name so its more readable, in your opinion? No problem. I shall change const foo to const bar."
}
,
{
"id": "46937329",
"text": ">the joy of problem solving\n\nIt's frontier exploration that brings me joy. If a clanker can do something, then it's a solved problem. I use all the tools at my disposal to push the frontier of problems solved. Wasting my time re-inventing the wheel brings me the opposite of joy."
}
,
{
"id": "46938645",
"text": "That's so reductive as to be useless. You might as well replace \"clanker\" with \"computer\" or \"pencil\" or whatever else you want."
}
,
{
"id": "46938174",
"text": "full agree"
}
,
{
"id": "46937929",
"text": "On a similar note, I have never heard the phrase “higher level abstractions” abstractions so much. Everywhere I look, higher level abstractions. It’s becoming one of those phrases I have an instant reaction to. The word “abstraction” used to mean something, man…"
}
,
{
"id": "46936974",
"text": "I don't really want to be a manager of humans, although my role as an engineer is a leadership role that has some overlap.\n\nBut I'm acutely conscious that in the 5+ years that I've been a senior developer, my ability to come up with useful ideas has significantly outstripped the time I have to realize those ideas (and from experience, the same is often true of academics).\n\nAt work, I have the choice between remaining hands-on and limiting what I can get done, or acting more like a manager, and having the opportunity to get more done, but only by letting other people do it, in ways that might not reflect my vision. It's pretty frustrating, to be honest.\n\nFor side projects, it's worse. Most of them just can't be done, because I don't even have the choice."
}
,
{
"id": "46936867",
"text": "It’s more that there’s a career ceiling and ageism is a looming threat. There are far more management jobs than high-level IC and for decades there’s been this thought that older engineers will be replaced with younger ones more aggressively than managers, although the big tech layoffs raise questions about whether that’s still true. I know multiple people who moved into management not because they were enthusiastic about it but because that was the best path for their career."
}
,
{
"id": "46939002",
"text": "It has nothing to do with power. I just want to build bigger, cooler things, faster."
}
,
{
"id": "46937240",
"text": "I became a manager so I could solve bigger problems. Good managers do dive into the details. It's a mistake to think that as a manager, you don't have to concern yourself with the minutia. You still have to do homework and deep thinking. you just don't have to write the code"
}
,
{
"id": "46938081",
"text": "My 15 year old son has been building his own video games with Unreal Engine for a few years..\n\nI was recently looking for mentors to work with him and advance his skills, targeting college aged kids / young 20s..\n\nIt was surprising to me how many people I came across in this field at this young age that are trying to focus on the \"higher level\" game planning aspects and not so much on the lower level implementation specifics."
}
,
{
"id": "46938698",
"text": "I highly recommend the Handmade Hero series to folks in his situation. Casey has put up an absurd amount of material for everyone for free.\n\nhttps://www.youtube.com/playlist?list=PLnuhp3Xd9PYTt6svyQPyR...\n\nhttps://guide.handmadehero.org/hmcon/\n\nhttps://guide.handmadehero.org/\n\nhttps://handmade.network/forums"
}
,
{
"id": "46936427",
"text": "I don't think it's about power. I feel more empowered as an engineer than I would as an engineering manager. As an engineer I have the power over all the intricate details of how systems work. As an engineering manager if I am lucky I would get to decide whom to fire if my team's budget gets a cut.\n\nI think it's that there is only that much demand for solving really complex problems, and doing the same thing over and over is boring, so management is the only way forward for many people"
}
,
{
"id": "46936452",
"text": "It's human nature.\n\nhttps://en.wikipedia.org/wiki/The_Stonecutter"
}
,
{
"id": "46936956",
"text": "I liken it to being an author.\n\nYou want to write a book about people's deepest motivations. Formative experiences, relationships, desires. Society, expectations, disappointment. Characters need to meet and talk at certain times. The plot needs to make sense.\n\nYou bring it to your editor. He finds you forgot to capitalise a proper noun. You also missed an Oxford comma. You used \"their\" instead of \"they're\".\n\nHe sends you back. You didn't get any feedback about whether it makes sense that the characters did what they did.\n\nYou are in hell, you won't hear anything about the structure until you fix your commas.\n\nEventually someone invents an automatic editor. It fixes all the little grammar and spelling and punctuation issues for you.\n\nNow you can bring the script to an editor who tells you the character needs more development.\n\nYou are making progress.\n\nYour only issue is the Luddites who reckon you aren't a real author, because you tend to fail their LeetGrammar tests, calling you a vibe author."
}
,
{
"id": "46937215",
"text": "Weird analogy. This makes sense if you liken this automatic editor to a LSP or compiler of the language you're writing in."
}
,
{
"id": "46940815",
"text": "Except that the editor doesn't focus on little things but the structure. It is the job of copy editor to correct all the grammar and bad writing. Copy editor can't be done by AI since it includes fixing logical errors and character names. My understanding is that everybody, including the author, fixes typos when they find them. There is also proofreader at the end to catch typos."
}
,
{
"id": "46938001",
"text": "another way to look at it is that management is a job with a set of skills, challenges, and rewards, just like any other, but as a civilisation we seem to have tied it to power and hierarchy, and made it something you need to be promoted into rather than choosing as a career from the outset (MBAs notwithstanding). maybe a lot of engineers would have gone into the engineering management path if they could have, and engineer was just seen as the more entry-level option."
}
,
{
"id": "46937480",
"text": "i like the aspect of engineering that's building useful or interesting or fun things for people, and i'll always experiment with new tech that facilitates that"
}
,
{
"id": "46936498",
"text": "For many people, code is just a means to an end to solve problems and build. The joy from solving problems doesn't disappear. Would you use traditional (not WebAssembly) assembly to build a web application? Probably not. LLMs make a lot more sense if you think of it as a tool to translate requirements into solutions."
}
,
{
"id": "46938271",
"text": "Engineering, to me, is simply \"the art of compromise.\"\n\nYou can't do that from a high level abstract position. You actually need to stand at the coal face and think about it from time to time.\n\nThis article encodes an entitled laziness that's destructive to personal skill and quality work."
}
,
{
"id": "46938127",
"text": "I think plenty would be willing to be managers if you removed the volatility of human personalities from it. At least for me, it means I get to focus on the more interesting tech work and not worry about writing tests or github actions."
}
,
{
"id": "46936579",
"text": "Software dev has been promoted as a good career path for almost 2 decades now. Naturally you'll have a bunch of people going in only because of money.\n\nA few years ago, when Agile was still the hot thing and companies had an Agile \"facilitor\" or manager for each dev team, the common career path I heard when talking to those people was: \"I worked as a java/cobol/etc in the past, but it just didn't click with me. I'm more of a peoples person, you know, so project management is where I really do my best work!\".\n\nYeah, right..."
}
,
{
"id": "46936776",
"text": "Look I already told you, I deal with the @#$% customers so the engineers don't have to. I have people skills! I am good at dealing with people, can't you understand that? WHAT THE HELL IS WRONG WITH YOU PEOPLE?!"
}
,
{
"id": "46932150",
"text": "> it completely transformed my workflow, whether it’s personal or commercial projects\n\n> This has truly freed up my productivity, letting me pursue so many ideas I couldn’t move forward on before\n\nIf you're writing in a blog post that AI has changed your life and let you build so many amazing projects, you should link to the projects. Somehow 90% of these posts don't actually link to the amazing projects that their author is supposedly building with AI."
}
,
{
"id": "46932195",
"text": "A lot of more senior coders when they actively try vibe coding a greenfield project find that it does actually work. But only for the first ~10kloc. After that the AI, no matter how well you try to prompt it, will start to destroy existing features accidentally, will add unnecessary convoluted logic to the code, will leave benhind dead code, add random traces \"for backwards compatibility\", will avoid doing the correct thing as \"it is too big of a refactor\", doesn't understand that the dev database is not the prod database and avoids migrations. And so forth.\n\nI've got 10+ years of coding experience, I am an AI advocate, but not vibe coding. AI is a great tool to help with the boring bits, using it to initialize files, help figure out various approaches, as a first pass code reviewer, helping with configuring, those things all work well.\n\nBut full-on replacing coders? It's not there yet. Will require an order of magnitude more improvement."
}
]
</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