llm/3a862c31-848e-4e32-be93-99402d2b43b6/batch-11-a887ff78-df14-4a23-8a55-0e82d82eea9c-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. Bugs Having Users at Scale
2. Automation Impact on Workers
3. Workplace Politics vs Technical Skills
4. Google's UX Quality Criticism
5. LLM-Assisted Writing Detection
6. Career Advancement and Networking
7. Clarity vs Cleverness in Code
8. User-Focused Engineering Culture
9. Innovation Tokens and Boring Technology
10. Abstraction and Complexity Management
11. Silent Resistance in Debates
12. Glue Work Recognition
13. Performance Optimization Strategies
14. Engineer-Customer Communication Barriers
15. Time vs Money Tradeoffs
16. Psychological Safety in Teams
17. Process and Bureaucracy Critique
18. Code Plagiarism Ethics
19. Big Tech Organizational Dysfunction
20. Goodhart's Law and Metrics Gaming
COMMENTS TO CLASSIFY:
[
{
"id": "46494144",
"text": "Some people think clarity means abandoning language idioms and writing simple code that a first year computer science student could understand and follow.\n\nIf you do this, your team will write verbose, repetitive code, and put more emphasis on procedures instead of data structures and how they change over time.\n\nUse the language features to write powerful concise code that really takes some skill and expertise in the language to understand. Force your team to become more skilled, don’t stoop down to the lowest common denominator. In time, this code will become as easily understood as any other simple program.\n\nAnd when shit breaks down at 2 AM, you do nothing, because your code is clever enough to handle problems itself.\n\nBut don’t obfuscate."
}
,
{
"id": "46490733",
"text": "Seems like the author had lost his personality during that 14 years trying to appease the strange people at the top or figure out the allpermeating bs they force on people."
}
,
{
"id": "46495389",
"text": "17. Your network outlasts every job you’ll ever have.\n\nMaybe you're not allowed a personality after you unlock peak outlasting networking."
}
,
{
"id": "46497285",
"text": "Pluribus effect :)."
}
,
{
"id": "46492053",
"text": "This feels somewhat hypocritical coming from Addy.\n\nAddy Osmani plagiarized my code and 'apologized' years later by publishing an article on his website[1] that he has never linked to from his social media accounts.\n\nI cannot accept his apology until he actually syndicates it with his followers.\n\nSeems relevant to note this behavior in light of points \"6. Your code doesn’t advocate for you. People do.\", \"7. The best code is the code you never had to write.\", and \"14. If you win every debate, you’re probably accumulating silent resistance.\"\n\n1. https://addyosmani.com/an-apology-to-eli/"
}
,
{
"id": "46494611",
"text": "You posted the code to a public blog page, with no attribution in the code or request of attribution from others, no license, and seemingly intended to share it freely with the world.\n\nThen you got an apology, and a second apology.\n\nI'm confused about what you think you're owed?\n\nThe explanation makes perfect sense, the headers were obviously just copied with no malicious intent. What is it that is still bothering you about this?"
}
,
{
"id": "46494829",
"text": "> no license, and seemingly intended to share it freely with the world\n\nNo license means you don’t intend to share it “freely”, since you didn’t share any rights. By default, you don’t own things people shared on the internet just because it’s there.\n\nThat being said I’ve even seen people with licenses in their repos who get mad when people used their code, there’s just no telling and it’s best to just treat random sources of code as anathema."
}
,
{
"id": "46495580",
"text": "Per Eli's own comment here, the original copied code was straight up public domain and thus does not even require attribution.\n\nhttps://github.com/Modernizr/Modernizr/pull/684#issuecomment..."
}
,
{
"id": "46494946",
"text": "I'm curious if you would have the same opinion about code shared on stack overflow?"
}
,
{
"id": "46495041",
"text": "I think GP is referring to the fact that an author’s work is copyright protected by default, and a license is needed to permit others to use freely [1]. StackOverflow posts are licensed under CC BY-SA 4.0 [2].\n\n[1]: https://www.copyright.gov/help/faq/faq-general.html\n\n[2]: https://stackoverflow.com/help/licensing\n\n(Disclaimer: Just commenting on GP’s statement about “no license”, not on the specific disagreement or apology mentioned above which I am unfamiliar with.)"
}
,
{
"id": "46495101",
"text": "It's worth noting that the code in question was also open sourced and permissively licensed by the original author as he stated in the thread[1]. I guess this isn't really about licensing at all, just the original author seems to think it was rude, and also doesn't want to accept any of the apologies that have been offered.\n\n[1]: https://github.com/Modernizr/Modernizr/pull/684#issuecomment..."
}
,
{
"id": "46494094",
"text": "Not to make excuses for plagiarism, I am looking at the code itself and somewhat scratching my head since it seems quite...trivial?\n\nI don't mean to belittle the effort but at least in terms of volume of code and level of effort, I wouldn't recognize it as mine if someone had copied it from my work and passed it off as theirs.\n\nRegarding the charge of plagiarism, is it possible that the PR attribution reflects someone eager to contribute something to a larger effort as opposed to simply trying to \"steal\" someone else's work?\n\nOne could reasonably interpret the PR and attribution as \"I integrated this code into this project thus I am taking credit for it\". In other words there is probably a stronger charge for misguided clout-chasing than plagiarisms."
}
,
{
"id": "46493953",
"text": "That code from your post is fairly standard image load handling, but the notable part is this line:\n\nself.apng_supported = ctx.getImageData(0, 0, 1, 1).data[3] === 0;\n\nUnless I'm misunderstanding, it's basically a \"neat trick\", like using ~~ for rounding or a fast inverse square root.\n\nIs the intent that everyone who makes use of that trick is supposed to link back to your blog?"
}
,
{
"id": "46494676",
"text": "addy rubs me the wrong way more often than not, but you really gotta let this go friend."
}
,
{
"id": "46497651",
"text": "Oh my god. I have never seen an about/bio page even half as gross and cringey as his.\n\nhttps://addyosmani.com/bio/\n\nIt's so obscene that it seems like it's a parody\n\n> Colleagues often remark on Osmani’s humility\n\nLOL! Who writes these things about themselves with a straight face?!\n\nIt also shows that taking credit for others' work is 100% his MO.\n\n> Osmani’s team created Workbox, a set of libraries for generating service worker scripts that handle caching and offline functionality with minimal fuss. Workbox simplified what used to be a complex task of writing low-level code to intercept network requests.\n\nNo, Jeff Posnick (who I suppose technically was on addy's team) created workbox and it has been basically abandonned since he left Google. Or was it Sundar Pichai's team who made workbox? Or does Brendan Eich deserve the credit?\n\nI have to assume the rest of the bio, and his career, has been built off of usurping credit. He always rubbed me the wrong way, and this vindicates that sen"
}
,
{
"id": "46492532",
"text": "FWIW, the actual apology is well written."
}
,
{
"id": "46492629",
"text": "Although little note at the very end explains why:\n\n> This note is in response to emails from Eli Grey to Chrome leadership from October, 2023\n\nIn other words, he wrote this because he was forced to."
}
,
{
"id": "46495178",
"text": "Eli also went back and changed his original 11 years later response from:\n\n> No problem; just remember that modifying someone else's code does not grant you any copyright to that code.\n\nto\n\n> I don't agree with your opinion that inserting existing code into a template (the API) for a framework (Modernizr) warrants a notice of credit, even with a few changes to the code being inserted.\n\nSeems almost a little crazy to hold onto something that long and return to edit your comment 11 years later.\n\nhttps://github.com/Modernizr/Modernizr/pull/684#issuecomment..."
}
,
{
"id": "46495077",
"text": "that's going a bit far, no?"
}
,
{
"id": "46493884",
"text": "If you run it through originality.ai, you'll see that bits of it are his writing, some is mixed and some is just ai. This blog post everyone is discussing is also written with ai."
}
,
{
"id": "46494063",
"text": "And who or what is \"originality.ai\" supposed to be that makes it an authority on AI provenance (an unsolvable problem)?"
}
,
{
"id": "46494746",
"text": "That site happily flags writing older than the modern AI era. It's a worthless grift, which has unfortunately suckered many."
}
,
{
"id": "46494646",
"text": "lol you believe that site for more than a second?"
}
,
{
"id": "46495461",
"text": "15 years on that trivial piece of code man. Reminds me of Dostoyevsky's \"Notes from Underground\"."
}
,
{
"id": "46493991",
"text": "Thanks for sharing, I found the blogpost hypocritical even without knowing about this"
}
,
{
"id": "46494316",
"text": "\"i cannot accept this apology unless..\"\n\nyou got a written apology already, what else do you want?\n\na post of this in all of his socmed accounts? him telling this story to his kids at dinner table and bedtime stories? at his eulogy, obituary, and his grave?\n\nwhat's your life mission now, to post this little drama of yours on each and every content he puts out?\n\nwas that code your best achievement to date? did it stole millions from you and ruined your life?\n\ngrow the fuck up dude"
}
,
{
"id": "46494596",
"text": "Plagiarizing code is kind of a redundant concept nowadays in the era of LLM coding engines. It's a safe bet there's always copilot plagiarizing someone's code on one of its users' machines, both being oblivious to it."
}
,
{
"id": "46495344",
"text": "That's a bit different from knowingly taking a friend or former partner's code and putting \"by Your Name\" on top of it before sharing it with outsiders"
}
,
{
"id": "46492324",
"text": "Jesus, bro.\n\nLet bygones be bygones. How long is this ago? It's just code. And what the code did, is not even fundamental. It's not like you cured cancer."
}
,
{
"id": "46493970",
"text": "I tend to see my code in these terms as well, it's not dear to me. But I'd never presume to tell someone how to feel over having their work stolen (and I'm using that term because that's how I'm sure Mr Grey felt)."
}
,
{
"id": "46494719",
"text": "just because people think or feel things, doesn't make those things valid (and certainly not prudent)"
}
,
{
"id": "46489839",
"text": "Great post, Years following Addy. I wonder know how he manages his time, in addition to being a leader at Google, and writing such a valuable blog."
}
,
{
"id": "46491952",
"text": "Unsure why this comment appears to be downvoted!\n\nI have followed him for a long time and learned a lot too. I always wonder the same thing about the “tech influencers” and I’d love to know more about how they structure their days.\n\nI find it difficult recently to sit down and complete a meaningful piece of work without being distracted by notifications and questions. In the last year this has been exacerbated by the wait time on LLMs completing.\n\nI would love to know how top performers organise their time."
}
,
{
"id": "46490155",
"text": "seems the real lesson would be to not spend 14 years at google"
}
,
{
"id": "46490294",
"text": "I'm sure he made a killing though"
}
,
{
"id": "46491269",
"text": "It isn't just that he made a killing — Osmani helped conceive a broader vision of blogging as a fusion of human in the center writing and AI agents."
}
,
{
"id": "46492321",
"text": "Or to say it in his own words: \"Few individuals have done as much to push the web forward while uplifting its developers, and that legacy will be felt for a long time to come.\" source: https://addyosmani.com/bio/"
}
,
{
"id": "46497579",
"text": "Oh my god. I have never seen an about/bio page even half as gross and cringey as this. It's so obscene that it reads like a parody\n\n> Colleagues often remark on Osmani’s humility\n\nLOL! Who writes these things about themselves with a straight face?!\n\nIt also shows that taking credit for others' work is 100% his MO.\n\n> Osmani’s team created Workbox, a set of libraries for generating service worker scripts that handle caching and offline functionality with minimal fuss. Workbox simplified what used to be a complex task of writing low-level code to intercept network requests.\n\nNo, Jeff Posnick (who I suppose technically was on addy's team) created workbox and it has been basically abandonned since he left Google.\n\nI have to assume the rest of the bio, and his career, has been built off of usurping credit. He always rubbed me the wrong way, and this vindicates that sense.\n\nWhat a psychopath!"
}
,
{
"id": "46495933",
"text": "it's a bit weird to talk about yourselves in third person"
}
,
{
"id": "46492885",
"text": "> and that legacy will be felt for a long time to come\n\nyes, the legacy of polluting the internet with unlimited \"AI\" slop to the point it became useless"
}
,
{
"id": "46492318",
"text": "I don't quite understand how that is your take away. Could you clarify?"
}
,
{
"id": "46489620",
"text": "The writing is excellent.\n\nVery correlated with the quality of the message I'd imagine."
}
,
{
"id": "46490090",
"text": "It is very heavily filled with LLM-isms. The writing is bland AI output."
}
,
{
"id": "46490481",
"text": "how do you know?\n\nin the first item, LLMs don't use incomplete sentence fragments?\n\n> It’s seductive to fall in love with a technology and go looking for places to apply it. I’ve done it. Everyone has. But the engineers who create the most value work backwards: they become obsessed with understanding user problems deeply, and let solutions emerge from that understanding.\n\nI suppose it can be prompted to take on one's writing style. AI-assisted, ok sure, but hmm so any existence of an em-dash automatically exposes text as AI-slop? (ironically I don't think there are any dashes in the article)\n\nEDIT: ok the thread below, does expose tells. https://news.ycombinator.com/item?id=46490075 - yep there's definitely some AI tells. I still think it's well written/structured though.\n\n> It's not X... it's Y.\n\nThat one I can't unsee."
}
,
{
"id": "46490831",
"text": "And have a look at the bio: https://addyosmani.com/bio/\n\n> His story isn’t just about writing code, but about inspiring a community to strive for a better web. And perhaps the most exciting chapter is still being written, as he helps shape how AI and the web will intersect in the coming decade. Few individuals have done as much to push the web forward while uplifting its developers, and that legacy will be felt for a long time to come."
}
,
{
"id": "46490225",
"text": "The blog-post is AI generated or at least AI assisted."
}
,
{
"id": "46490293",
"text": "many of the replies in this Hacker News thread read like AI replies too. I think the internet is dead as we know it. ~100% of content will be bots writing for ~100% audience of bots"
}
,
{
"id": "46490744",
"text": "This is a good list. Original, evidence to me that the author is the real deal."
}
,
{
"id": "46490912",
"text": "There's hardly anything original here. These are regurgitated points you'd see in any article of this type. In fact, your favorite LLM can give you the same \"lessons\" from its training data."
}
,
{
"id": "46494604",
"text": "Your favorite LLM can probably reproduce this entire discussion thread so what’s the point, right?"
}
]
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