frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Soldier files whistleblower complaint over Iran strike that killed 6 U.S. troops

https://www.cnn.com/2026/11/15/politics/army-soldier-whistleblower-complaint
1•firefax•23s ago•0 comments

Oxide: Micron Memory and Storage

https://oxide.computer/blog/oxide-micron-second-generation-cloud-computer
1•tosh•1m ago•0 comments

CockroachDB Moves to Private Source Code Development

https://www.cockroachlabs.com/blog/source-code-protection/
2•recursiveranter•2m ago•0 comments

Show HN: Bozzetto – a Place to Align on Engineering Decisions

https://bozzetto.dev
1•cirrasphere•2m ago•0 comments

The Active Directory Era Is Finally Over

https://infisical.com/blog/active-directory-machine-identity
1•FinnLobsien•2m ago•0 comments

Show HN: SketchProbe – decode Apache DataSketches binaries, runs via WebAssembly

https://yadavan88.github.io/sketchprobe/
1•yadavan88•3m ago•0 comments

Show HN: Coral – Open-source gateway where agents write their own tools

https://github.com/withcoral/coral
10•jcs•3m ago•1 comments

Fable 5.2 plans and reviews, Opus builds cheaper

https://blog.hagebols.com/posts/fable-plans-and-reviews-opus-builds-cheaper/
1•decide1000•3m ago•0 comments

Google: AI agent turned a security patch into a exploit with no human help

https://www.theregister.com/research/2026/11/16/google-ai-agent-turned-a-security-patch-into-a-wo...
2•sshah03•4m ago•2 comments

SpaceX's landing reminds us even extraordinary technology will be reinvented

https://www.theatlantic.com/technology/2026/11/spacex-starship-catch/689453/
1•fortran77•4m ago•1 comments

Show HN: Neoma P-CAM – Sub-millisecond physical equilibrium and 64-spin Ising

https://github.com/neoma-pcam/pcam-live
1•neoma001•5m ago•0 comments

Dialing the current internet from Mac OS 9 (mostly)

https://julienblanchard.com/posts/dial-tcp-and-tls-for-mac-os-9.html
1•freediver•5m ago•0 comments

The Icarus Files: AI labs are aggressively diversifying away from Nvidia

https://am.jpmorgan.com/us/en/asset-management/institutional/insights/market-insights/eye-on-the-...
2•Betelbuddy•6m ago•0 comments

Number of new international college students in the U.S. drops 18 percent

https://www.washingtonpost.com/education/2026/11/16/number-new-international-college-students-us-...
1•bookofjoe•6m ago•1 comments

OffensiveCon26 Tokyo

https://www.youtube.com/playlist?list=PLAjhuVo0QY-Q
1•heljara•7m ago•1 comments

Challenges for human oversight in detecting AI-assisted diagnostic malfunctions

https://www.nature.com/articles/s41746-026-03410-x
1•amirmc•7m ago•0 comments

A simple prep tool for cutting

https://www.cutting-studio.com/
1•prozense•10m ago•0 comments

Show HN: Storm - self-hosted assistant that builds apps and waits for your OK

https://github.com/realentity/realentity-storm
1•trayanm•10m ago•0 comments

Risk of nuclear accident in UA increasing this winter, safety regulators say

https://www.reuters.com/business/energy/risk-nuclear-accident-ukraine-increasing-this-winter-atom...
4•gvieri•12m ago•0 comments

US cracks down on third-country loophole that allowed China to use Nvidia chips

https://www.cnbc.com/2026/11/16/nvidia-commerce-china-lutnick.html
2•flowerlad•13m ago•0 comments

A step toward defining the Standard Model on a lattice

https://openai.com/index/step-toward-defining-the-standard-model/
1•droidjj•13m ago•0 comments

Algorithms Every Programmer Should Know

https://photonlines.substack.com/p/visual-focused-algorithms-cheat-sheet
1•photon_lines•14m ago•0 comments

Scar-Native Neural Architecture and ScarCodec with Physical Signal Proofs

https://zenodo.org/records/24282028
1•thetod•17m ago•0 comments

Slam on Microduck with an 8×8 depth sensor

https://pollen-robotics.com/microduck/blog/microduck-slam/
1•surprisetalk•18m ago•1 comments

AltFile Explorer

https://github.com/h3rb/AltFile
1•alvintheliche•18m ago•1 comments

AI-driven scientific progress threatened by an obsession

https://www.unite.ai/ai-driven-scientific-progress-threatened-by-a-strange-obsession/
2•50kIters•18m ago•0 comments

Reverse-Engineering Kevin J. Lang's Lost OCaml Code in Apache DataSketches

https://www.tisonkun.io/posts/ai-repair-program/
1•tison•19m ago•0 comments

Dear DeepSeek Engineer

https://critisticuffs.org/texts/dear-deepseek-engineer
1•critisticuffs•19m ago•0 comments

A 'living' wall could help buildings breathe easier

https://news.yale.edu/2026/11/12/living-wall-could-help-buildings-breathe-easier
1•rdmuser•21m ago•0 comments

Show HN: Neuronte – small neural nets as a font

https://github.com/itsmygithubacct/neuronte-v2
1•gropo2•22m ago•0 comments
Open in hackernews

I Replaced My Devs with Agents – Part 2: What Happened to the Team

https://easylab.ai
2•buzzbyjool•1y ago

Comments

buzzbyjool•1y ago
Follow-up to Part 1, where I explained how we rebuilt our dev process around LLM agents at Easylab AI and stopped writing most code by hand.

The original post sparked a lot of questions — the most common being:

“Okay, but how did your developers react?”

Here’s a breakdown of what actually happened inside the team — who stayed, who didn’t, and what new skills emerged.

⸻

Some embraced it. Some left. That’s okay.

When we committed to building with agents — not just using LLMs for autocompletion, but making them first-class executors of logic — not everyone was thrilled.

Some engineers were fascinated. They saw the shift coming and wanted to be ahead of it. They became architects of multi-agent workflows, prompt designers, QA strategists, validators.

Others didn’t want to work that way. They liked writing every line, owning every detail, and were (understandably) uncomfortable giving up control to a system that feels less deterministic.

They moved on. We didn’t push them.

Like every evolution in software tooling, this one came with a natural selection effect. Not better or worse. Just different skillsets, different energy.

⸻

This isn’t no-code. It’s new-code.

Some assumed we were just automating CRUD. That’s not what happened.

The tools we use today — Claude 3.7, DeepSeek, bolt.new, role-based agents, memory stacks — aren’t trivial macros. They’re a new level of abstraction. They reason. They refactor. They test. They fail with style.

You don’t “ask the AI to do it.” You engineer constraints, context, fallbacks, tooling, and create robust systems through language.

At Easylab AI, we use context protocols, Redis-based memory layers, and model routing logic based on latency and task weight. It’s not less technical — it’s just built differently.

⸻

Did their skills atrophy?

Actually, the opposite.

Sure, they’re not practicing DSA interview puzzles every day. But they’re building systems that can write tests, simulate failure, and self-correct.

They’re learning new skills you can’t yet Google: • Prompt minimalism • Agent composability • Multi-agent state consistency • Prompt-based debugging

They think more like staff engineers than syntax solvers.

⸻

This is abstraction, not disappearance

The fear that “AI replaces engineering” misses the nuance.

This isn’t magic. It’s not cheating. It’s just abstraction — like every wave before: • Assembly to C • C to Python • Python to Terraform • Terraform to prompt-based execution

As Jensen Huang (NVIDIA CEO) said earlier this year:

“English is now the world’s most popular programming language.”

He’s not wrong. We’re just learning to write instructions that build systems — without the middle step of syntax.

⸻

One more thing

Some developers left. Most who stayed leveled up. And today, no one wants to go back.

That tells me something: It’s not easier work. It’s better work.

Happy to answer more if folks are curious.

falcor84•1y ago
I'm not clear - is this comment the actual post, while the link that you shared is irrelevant? If so, it would have probably been more appropriate to submit this as an "AMA:" without a url.
buzzbyjool•1y ago
Hi thanks for your comment, honestly I don't know how to do it. Thanks
falcor84•1y ago
Oh, it's just that you can make a submission without anything in the 'url' input. Here are a couple of examples:

https://news.ycombinator.com/item?id=15853374

https://news.ycombinator.com/item?id=43363056

buzzbyjool•1y ago
thanks
JohnFen•1y ago
> Some developers left. Most who stayed leveled up.

"Leveled up" is a subjective, loaded term. I assume what you mean here is "adapted to your way of doing things."

> And today, no one wants to go back.

Well, of course, because those who would have wanted to go back already left. This appears to be selection bias more than evidence that your approach is a good one.

To be clear, I'm not trying to imply that your approach isn't a good one. I'm just saying that the devs who remained not wanting to go back isn't evidence that it is.

buzzbyjool•1y ago
You’re absolutely right to call that out — and I appreciate the thoughtful framing.

“Leveled up” is subjective, yes. What I meant more precisely is this: the devs who stayed stopped spending time on tasks like writing boilerplate logic or tweaking form validation, and started focusing on higher-order thinking — designing agent workflows, debugging reasoning paths, writing specs that are machine-parsable, and thinking in systems rather than syntax. That shift, in terms of skill depth and adaptability, is something I genuinely view as a level-up. But I agree, it’s through the lens of our environment.

And yes — absolutely fair on the selection bias. When I say “no one wants to go back,” I don’t mean it as proof the approach is universally better. It’s just true for our current team, within the culture and processes we’ve chosen to embrace. Those who didn’t align with this way of working left early — and I don’t hold that against them.

So your comment is a valuable nuance: internal satisfaction is a necessary condition for success, but not a sufficient one. Our team’s enthusiasm is a sign that the model can work — not that it will for everyone.

Thanks for calling it out clearly.