llm/0c2f997f-ee88-4da1-8587-79dca97bbc3f/batch-1-f39f6be0-9441-4182-aa12-e0abb0c0ae14-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. 24/7 Work Culture Concerns
2. Labor Union Organization
3. Work-Life Balance Boundaries
4. Alternative Mobile Coding Setups
5. Git Worktrees Parallel Development
6. Push Notification Systems
7. Tailscale VPN Security
8. LLM Productivity Claims Skepticism
9. Capitalism and Worker Exploitation
10. Code Quality Without Review
11. Terminal Apps for Mobile
12. Session Persistence with Tmux
13. Anthropic Marketing Suspicions
14. Cloud VM Cost Efficiency
15. Cognitive Effects of LLM Use
16. Vibe Coding Quality Concerns
17. Open vs Proprietary AI Models
18. Future of Software Engineering Jobs
19. Multi-Agent Orchestration Tools
20. Voice Input for Mobile Coding
COMMENTS TO CLASSIFY:
[
{
"id": "46493231",
"text": "Part of being in a union tends to be lawyering up and \"nailing down\" exactly what everyone's duties in detail and what fair compensation might be, and what terms / conditions might be etc.\n\nPersonally I don't think they're a great fit for the software industry where the nature of the job and the details are continuously changing as technology evolves."
}
,
{
"id": "46493468",
"text": "That's not an intrinsic part of being in a union, just a particular way they have been implemented in US.\n\nThe fundamental point of the union is to be able to negotiate as a group. That is valuable regardless of the industry."
}
,
{
"id": "46494644",
"text": "But what are you negotiating about? What do all tech workers have in common that wouldn't be better addressed with top level regulations like \"right to disconnect\"?"
}
,
{
"id": "46494673",
"text": "- maternity leave\n\n- paternity leave\n\n- overtime\n\n- not having to answer a call or email outside of work hours\n\n- workman’s comp / short/long-term disability for issues with my back or wrists or eyes or…\n\n- about 100 more things"
}
,
{
"id": "46494833",
"text": "The outsized pay for software engineers in the US takes into account a lot of this stuff. Would you trade those 100 things for, say, a salary of $75k a year for a senior software engineer, like they have in Europe?"
}
,
{
"id": "46495672",
"text": "Meh. The rest of the world also doesn't have big salaries for software devs. The US is the outlier.\n\nIt's not just the labor regulations holding Europe back, it's the lack of funding due to not having a unified European digital market.\n\nNetflix Europe needs to have 20+ licensing deals. Selling across Europe at a large scale requires interactions with 20+ legal teams. Language and cultural barriers kill a lot of things.\n\nHow do US giants thrive in Europe, then?\n\nBecause they come in directly giant-sized based on growth in the US. They either ignore European legal compliance until sued or pay peanuts for them to handle all the legal aspects."
}
,
{
"id": "46494707",
"text": "All those sorts of protections seem like they make sense for every worker rather than being \"tech\" specific. I do understand that collective bargaining could help with carving out sector-specific deals, though.\n\nI wonder if there is a difference in context that explains why we might disagree. I'm in Australia where I think it's politically easier to \"add\" broad top level protections for all workers than it would be in the US."
}
,
{
"id": "46494918",
"text": "tech unions should be pushing for condemnation, which is the process of getting employees seats on the corporate board"
}
,
{
"id": "46496023",
"text": "So 105 reasons for management to move as many jobs to AI as possible, as soon as possible. Got it."
}
,
{
"id": "46492837",
"text": "Two things:\n\n1. Like most labor organizing, I think this would be beneficial for software engineers, but not long-term beneficial for the world at large. More software that is easier to make is better for everybody.\n\nWould you still want to live in a world where your elevator stops working when the elevator operator is sick, or where overseas Whatsapp calls cost $1 per minute, because they have to be connected by a chain of operators?\n\n2. Software engineering is a lot easier to move than other professions. If you want to carry people from London to New York, you need to cater to the workers who actually live in London or New York. If you want to make software... Silicon Valley is your best bet right now, but if SV organizes and other places don't, it may not be your best bet any more. That would make things even worse for SV than not organizing. Same story applies to any other place.\n\nSure, companies won't more overnight, but if one place makes it too hard for AI to accelerate producti"
}
,
{
"id": "46493483",
"text": "The \"world at large\" mostly consists of workers, so things that are beneficial to workers are also beneficial to it.\n\n> your elevator stops working when the elevator operator is sick\n\nCan you point somewhere outside of US where this is the case with unions?"
}
,
{
"id": "46493082",
"text": "So do you believe that the gains from this technology will be broadly distributed? Or will capital capture the majority of those gains?"
}
,
{
"id": "46493169",
"text": "what technologies has \"capital\" captured the majority of gains from?"
}
,
{
"id": "46493572",
"text": "This would potentially be true for a lot of tech in the last five decades or so. When it gets cheaper to make the things people need and want without those needs and wants changing, you can get away with paying people a lower real wage for the same productivity. Couple that with the fact that the workers themselves also have typically grown more productive from the same tech, allowing companies to undercut competitors and capture more market share until everyone else catches on. I figure capital has benefited enormously from recent tech, very possible it captured the majority of the excess money produced."
}
,
{
"id": "46493655",
"text": "name something so we can look into it and figure out if its true!"
}
,
{
"id": "46494001",
"text": "I don't think that's possible to analyze for most technologies. How could we determine the effect of, say, OLED technology specifically on workers' real wages across the economy? Even doing the same for a particular seller's margin, say LG, would be difficult and wouldn't tell the full story. If you have an idea of how to do that for something let me know."
}
,
{
"id": "46494147",
"text": "Well, that's part of the problem isn't it? Do we just assume the worst, or what's the solution?"
}
,
{
"id": "46494282",
"text": "We'd probably want to use a measure of worker productivity itself as a proxy for technological improvements and look at various measures like real wages in relation to it rather than restricting our analysis to any one technology."
}
,
{
"id": "46493798",
"text": "Does Musk's trillion dollar bonus count?"
}
,
{
"id": "46495694",
"text": "Small newspapers full of classified ads used to be available locally around the world, creating local employment. Google and Meta ravaged that and sucked the money out to a handful of shareholders and tens of thousands of highly paid tech workers. That's just one market."
}
,
{
"id": "46495465",
"text": "Yes, labour unions are immoral. Curtailing growth (especially in industries where it can prevent unnecessary death) for your personal needs is plain evil. I say that as someone who is both very stressed by pressure to sustain my family while cushy life is slipping away."
}
,
{
"id": "46493541",
"text": "The ownership class sure did a number on the white collar working class.\n\n“I don’t need a union, I can negotiate my wages and working conditions just fine on my own”"
}
,
{
"id": "46494944",
"text": "“I’m a special rockstar guru ninja 10x dev, being held to the standards of the normals will just hold me back from my true potential”"
}
,
{
"id": "46492827",
"text": "I wish I knew which union to pitch. All I can say is what I know which is if you are dispirited with this state of affairs a great way to figure out where to go with it is to connect with your local democratic socialists of america branch, or maybe the joint union dsa effort:\n\nhttps://workerorganizing.org/"
}
,
{
"id": "46495163",
"text": "The difference here is, you type a command into your phone at 3pm. Put it down to go play with your kid for 3hours. Type a new one in at 9pm before bed where you’ve been binging your wife’s favorite show. Then you wake up at 10am to a holistic transformation in your business that would’ve taken months previously in your career. But whatever, another command and it’s off to 11am frisbee."
}
,
{
"id": "46495390",
"text": "More like you'll manage 20 agents and will be reading, reviewing and testing in between builds. Race to the bottom."
}
,
{
"id": "46492567",
"text": "That sounds more like the fault of shitty managers who would find a way to make you work 24/7, with or without Claude Code \"On-the-Go\"."
}
,
{
"id": "46492812",
"text": "One of these is immutable (shitty managers) one of these is new. I personally am all here for the brief human funtime before we all get paperclipped and whatever, been having a ton of fun with CC/Codex, been pushing my own startup forward... but ... You do see the issue here right?\n\nIt's the power imbalance. Shitty managers still control your means to eat."
}
,
{
"id": "46494498",
"text": "> It won't matter if I'm washing the dishes, walking the dog, driving to the supermarket, picking up my kids from school. I'll always be switched on, on my phone, continuously talking to an LLM, delivering questionable features and building meaningless products, destroying in the process the environment my kids are going to have to grow in.\n\nI remember hearing similar criticisms of continuous delivery. On one end of the spectrum people who had to wait months to get changes out now got them out relatively quickly. On the other end of the spectrum, some person was going to push changes at midnight.\n\nA decade on forward I've never actually worked at a shop that at scale did continuous delivery in its truest sense where changes go straight to production. Simply, nothing beats a human in the loop; it's always about balancing the costs of automation and a lower barrier to entry. I imagine this kind of thing, if it ever actually takes hold and can be adopted by a larger subset of engineers, w"
}
,
{
"id": "46493922",
"text": "The answer is boundaries\n\nIf I get emails outside of work hours and they're not urgent - I reply during work hours. This is no different\n\nBurnt out workers are far less productive so win-win for everyone"
}
,
{
"id": "46497149",
"text": "Hum, I already have a phone with Slack / Email on. And it's only switched on during work hours. No messaging outside of that window. Why would that be different?"
}
,
{
"id": "46492520",
"text": "Did they say the same when Email took over? Or Slack?"
}
,
{
"id": "46492656",
"text": "Are you suggesting that workers are NOT already more constantly \"on the clock\" with mobile phones/email/slack/text than before those things?\n\n(I'm not really sure LLMs will make it that much worse here, but all those things have been harmful to workers already.)"
}
,
{
"id": "46492543",
"text": "Well yes, they did... For example: https://news.ycombinator.com/item?id=29201917"
}
,
{
"id": "46492848",
"text": "Remember \"Crackberry\"?"
}
,
{
"id": "46494569",
"text": "No thanks. I'm so glad I'm getting closer to retirement age. From a young age, all I wanted to do was program computers. _I_ wanted to do it. Not have some tool do it for me. There's no fun or interest or ... anything that comes from that. I want to solve the problems. I want to write the code. It's what I am good at and it's incredibly enjoyable to me. Why the fuck would I ever give that up?\n\nBut, the world is changing. Y'all can have it... in a few short years. ;)"
}
,
{
"id": "46492932",
"text": ">But the cognitive dissonance I feel when I think about what this means over a longer time horizon is really painful.\n\nExcluding work (where granted, some companies are dictating the use of llms) and trying not to sound uncaring or disrespectful, but have you thought about not using llms for everything and using the old grey cells? Not having answers to every whimsical thought might be a good thing.\n\nIt's very easy to relax the brain (and be lazy tbh) with llms and it's scary to think what will happen in the next 4 years in terms of personal cognitive ability (or as a society).\n\ne.g. I've noticed (and probably most have here) that the world is full of zombies glued to their phones. Looking over their shoulder (e.g. on a train, yeah it's a bit rude but I'm the curious type), they are doom scrolling or playing waste-time games (insert that boomer meme in Las Vegas with slot machines [0]). I try to use my phone as little as possible (especially for dog walks) and feel better for it, allow"
}
,
{
"id": "46493778",
"text": "There is evidence that LLM usage is actually making people dumber. I'm not sure if they've figured out the cause/effect or not but that's enough evidence for me to avoid them if I can. They can be useful for some stuff but I found myself offloading my thinking a little too frequently.\n\nAnyways if we do get to the point where you need to use LLMs to write code, I can make a decision then, but for now I don't feel the need to adopt agentic workflows and I think the people who don't will be better cognitively positioned in the future."
}
,
{
"id": "46492508",
"text": "The LLMs have successfully domesticated humans."
}
,
{
"id": "46493255",
"text": "\"We shape our buildings; thereafter they shape us.\" - Winston Churchill"
}
,
{
"id": "46492553",
"text": "Poison Fountain: https://rnsaffn.com/poison3/"
}
,
{
"id": "46492881",
"text": "> Small quantities of poisoned training data can significantly damage a language model.\n\nIs this still accurate?"
}
,
{
"id": "46493028",
"text": "Probably always be true, but also probably not effective in the wild. Researchers will train a version, see results are off, put guards against poisoned data, re-train and no damage been done to whatever they release."
}
,
{
"id": "46493256",
"text": "How would they put guards against poisoned data ? How would they identify poisoned data if there are a lot/obfuscated ?"
}
,
{
"id": "46492886",
"text": "Had the same feeling many moons ago when they gave me an office smartphone where email from the company was available 24/7. At the beginning was answering emails at midnight, nowadays couldn't care less. Just wait until work hours.\n\nYou'll likely get used to this new thing too."
}
,
{
"id": "46495466",
"text": "That reminds me of my father calling the mobile phone and laptop issued to him as the \"dunce kit\", so he could work at home as well. He used to say that since the 90s, ahaha."
}
,
{
"id": "46493010",
"text": "You can do that if you want. Ill refuse. Ill take a manual labor job doing basically anything else for 40 hours a week over what your describing."
}
,
{
"id": "46493615",
"text": "An LLM send may send the work ticket or work order lol but i get your point"
}
,
{
"id": "46493661",
"text": "Are there really that many “things to do” that anyone, let alone everyone, will need to work that way?"
}
,
{
"id": "46493204",
"text": "Seems more likely that that won't happen"
}
]
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