frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

PC Gamer recommends RSS readers in a 37mb article that just keeps downloading

https://stuartbreckenridge.net/2026-03-19-pc-gamer-recommends-rss-readers-in-a-37mb-article/
408•JumpCrisscross•9h ago•197 comments

The gold standard of optimization: A look under the hood of RollerCoaster Tycoon

https://larstofus.com/2026/03/22/the-gold-standard-of-optimization-a-look-under-the-hood-of-rolle...
257•mariuz•8h ago•85 comments

The future of version control

https://bramcohen.com/p/manyana
449•c17r•12h ago•255 comments

Reports of code's death are greatly exaggerated

https://stevekrouse.com/precision
303•stevekrouse•16h ago•235 comments

Intuitions for Tranformer Circuits

https://www.connorjdavis.com/p/intuitions-for-transformer-circuits
26•cjamsonhn•2h ago•2 comments

Why I love NixOS

https://www.birkey.co/2026-03-22-why-i-love-nixos.html
236•birkey•10h ago•160 comments

GoGoGrandparent (YC S16) is hiring Back end Engineers

https://www.ycombinator.com/companies/gogograndparent/jobs/2vbzAw8-backend-engineer
1•davidchl•24m ago

I Reverse-Engineered the TiinyAI Pocket Lab from Marketing Photos

https://bay41.com/posts/tiiny-ai-pocket-lab-review/
51•davidklemke•3d ago•11 comments

Project Nomad – Knowledge That Never Goes Offline

https://www.projectnomad.us
385•jensgk•15h ago•120 comments

Migrating the American Express Payment Network, Twice

https://americanexpress.io/migrating-the-payments-network-twice/
29•madflojo•3h ago•6 comments

Flash-MoE: Running a 397B Parameter Model on a Laptop

https://github.com/danveloper/flash-moe
321•mft_•16h ago•108 comments

GrapheneOS will remain usable by anyone without requiring personal information

https://grapheneos.social/@GrapheneOS/116261301913660830
282•nothrowaways•6h ago•74 comments

They're Vibe-Coding Spam Now

https://tedium.co/2026/02/25/vibe-coded-email-spam/
50•raybb•5h ago•36 comments

MAUI Is Coming to Linux

https://avaloniaui.net/blog/maui-avalonia-preview-1
178•DeathArrow•12h ago•85 comments

Five Years of Running a Systems Reading Group at Microsoft

https://armaansood.com/posts/systems-reading-group/
132•Foe•10h ago•39 comments

Windows native app development is a mess

https://domenic.me/windows-native-dev/
359•domenicd•18h ago•364 comments

What Young Workers Are Doing to AI-Proof Themselves

https://www.wsj.com/economy/jobs/ai-jobs-young-people-careers-14282284
92•wallflower•9h ago•117 comments

LLMs predict my coffee

https://dynomight.net/coffee/
89•surprisetalk•4d ago•37 comments

First and Lego Education Partnership Update

https://community.firstinspires.org/first-lego-education-partnership-update
30•jchin•3d ago•13 comments

How to Attract AI Bots to Your Open Source Project

https://nesbitt.io/2026/03/21/how-to-attract-ai-bots-to-your-open-source-project.html
94•zdw•1d ago•13 comments

Building an FPGA 3dfx Voodoo with Modern RTL Tools

https://noquiche.fyi/voodoo
169•fayalalebrun•14h ago•35 comments

Answer Engine Optimization

https://juliasolorzano.com/blog/2026/03/16/answer-engine-optimization/
5•speckx•3d ago•0 comments

"Collaboration" Is Bullshit

https://www.joanwestenberg.com/collaboration-is-bullshit/
36•mitchbob•2h ago•11 comments

You are not your job

https://jry.io/writing/you-are-not-your-job/
83•jryio•12h ago•118 comments

More common mistakes to avoid when creating system architecture diagrams

https://www.ilograph.com/blog/posts/more-common-diagram-mistakes/
148•billyp-rva•16h ago•53 comments

Show HN: Codala, a social network built on scanning barcodes

https://play.google.com/store/apps/details?id=com.hsynkrkye.codala&hl=en
39•hsynkrkye•4d ago•19 comments

Ordered Dithering with Arbitrary or Irregular Colour Palettes (2023)

https://matejlou.blog/2023/12/06/ordered-dithering-for-arbitrary-or-irregular-palettes/
13•surprisetalk•5d ago•0 comments

Teaching Claude to QA a mobile app

https://christophermeiklejohn.com/ai/zabriskie/development/android/ios/2026/03/22/teaching-claude...
75•azhenley•8h ago•8 comments

25 Years of Eggs

https://www.john-rush.com/posts/eggs-25-years-20260219.html
258•avyfain•4d ago•73 comments

The IBM scientist who rewrote the rules of information just won a Turing Award

https://www.ibm.com/think/news/ibm-scientist-charles-bennett-turing-award
108•rbanffy•16h ago•9 comments
Open in hackernews

"Collaboration" Is Bullshit

https://www.joanwestenberg.com/collaboration-is-bullshit/
36•mitchbob•2h ago

Comments

igor47•1h ago
Strong words. I wonder if the author has PTSD from poorly managed teams and has never had the fortune to work in a high performance well managed collaborative environment. I agree these are rare compared to the other kind, but they exist. Groups of people can produce more than lone wolves. One person didn't build the pyramids, the Linux kernel, or Amazon Web services. Even when responsibility for a top level domain rests with a single person, you still have to coordinate the work of people building the individual components.
ChrisMarshallNY•57m ago
One of the features of my work, these days, is that I work alone. I worked in [pretty high-functioning] teams, for most of my career.

Teams are how you do big stuff. I’m really good at what I do, but I’ve been forced to reduce my scope, working alone. I do much smaller projects, than our team used to do.

But the killer in teams, is communication overhead, and much of that, is imposed by management, trying to get visibility. If the team is good, they often communicate fine, internally.

Most of the examples he gave, are tools of management, seeking visibility.

But it’s also vital for management to have visibility. A team can’t just be a “black box,” but a really good team can have a lot of autonomy and agency.

You need good teams, and good managers. If you don’t have both, it’s likely to be less-than-optimal.

newAccount2025•13m ago
Strong agree. When I started managing there was very little oversight. It wasn’t perfect and we went a bit astray, and we also did phenomenal work and had everyone on the team deeply engaged and moving with autonomy.

On my second team, the visibility theater took over, upper management set and reset and reset and reset our direction, and nobody was happy. In retrospect, I should have said no immediately. Trusting and empowering your people is hard to beat.

icegreentea2•35m ago
It's a provocative title, but I think this section better captures his scope of argument - "Collaboration-as-ideology has made ownership and responsibility feel antisocial, which is a hell of a thing, given that ownership is the only mechanism that gets anything across the finish line.", as well as "But there’s a huge difference between communication and collaboration as infrastructure to support individual, high-agency ownership, and communication and collaboration as the primary activity of an organisation".

I think the author has identified that most organizations both fail at effective collaboration, and also use collaboration to paper over their failures.

I think the author maybe over-corrects by leaning on the idea that "only small teams actually get stuff done", and honestly I don't think anyone should be using SLA Marshall/Men Against Fire as an analogy for like... office work (if nothing else, even if you take his words at face value, then the percentage of US infantry who fired their rifles went up from 15-25% in WW2 to ~50% in Korea due to training improvements), but I can get behind the idea that a lot of organizations are setup to diffuse responsibility.

I also do think it's interesting to think about building the Pyramids. For the vast majority of people involved... I don't think modern audiences would call their work relationship or style "collaborative". Usually we use "collaborative" in opposition (at different times) to "working alone", "working with strict boundaries", and "being highly directed in what to do". Being on a work gang, or even being a team foreman is very much "no working alone", but those were also likely highly directed jobs (you must bring this specific stone to this specific location by this time) with strict boundaries.

stanleykm•33m ago
Agreed. I came in the comments to say something similar. I think the author raises some interesting points worth consideration but their perspective is so incredibly cynical. He mentioned a small team that made the Apollo computer program. Well it took an awful lot more than a computer program to get to the moon. I don’t think anybody would argue that there are people who don’t pull their weight out there but there is so much evidence that people working together actually works that it makes you wonder who hurt the author so much.
gotwaz•22m ago
Depends on the problem being solved. And how frequently the core prob changes. Cuz nothing is static in an ever changing universe.

What organization, skills, leadership is required to explore a jungle for gold is very different from what organization, skills and leadership is required to run a gold mine.

So we get explore-exploit tradeoffs, satisficing vs optimizing choices etc.

scuff3d•12m ago
Not sure men fighting for their lives in WW2 is the best comparison point for dev teams having too many standups and retros.
vielite1310•9m ago
I think the Author might have a lot of bad collaboration experience from working with teams that have low level of competence and agency, and especially in corporate, this highlights and accidentally resonates with me ( as of few months ago)

Laid off from a startup and moved fo corpos did gave me perspective,the first year working with the team works really well, we managed to get a lot of stuff really done and business were very happy.

And there came the Agile Coaches telling us to "Collaborate" while disguising as a need to serve his own agenda ( as he's also a PO for another squad ). So workshops on Collaboration, Explicit Expectation on PM have all authority and controls PO, for 8 freaking months just to get a competent team to work with a junior team with no agency nor even willingness to be mentored or do anything. So somewhat this incidentally aligns perfectly.

Corporate always manage to hire incompetent people, not firing them, and let others over-compensate for their failures, so yeah, its not really obvious but its there.

I believe the good collaboration can happen, but when people actually go of their ego and start listening and actually doing the work.

esfandia•3m ago
Thought-provoking essay. I can see how responsibility and ownership are important to help identify, motivate and reward the high achievers (and conversely, identify and get rid of the "dead wood"). But I can also see how collaboration and the dilution of responsibility and ownership helps better integrate junior members who might otherwise stay on the sidelines for longer than they should. There's also the issue of personnel turnover: what happens if the one person who is responsible for a major piece of a project leaves the company? A collaborative setting is more resilient to churn. There are trade-offs, and possibly a middle ground to be found.
noduerme•2m ago
It's frustrating to pull more weight and take ownership when other people aren't. But what's legitimately soul-killing to an individual and deadly to an organization is the collective impulse to avoid giving those people credit when it's due. Most of those 20% out there pulling more than their weight just want some acknowledgement. Not giving them that is one way to quickly hollow out your company.
cgio•2m ago
What it misses is that the 80% of soldiers who were not firing was still required. Not everyone has the same product, and someone’s product exists at an abstraction layer above the outcome and towards the organisation that builds it, as ugly and inefficient as it may be judged in comparison to an army of perfect contributors that does not exist.