Introducing Nexul
A self-hosted board + docs + CI/deploy + MCP. Your coding agents use the same board as you.
Docs, ticket, Fix with AI, ship. All in one platform
https://t.co/Bek9wIws5l
Introducing Nexul
A self-hosted board + docs + CI/deploy + MCP. Your coding agents use the same board as you.
Docs, ticket, Fix with AI, ship. All in one platform
https://t.co/Bek9wIws5l
@adamdived1@gdechichi I stand what I said.
Many months later they’ll somehow say “we can do 60 fps!”
And then 1-2 years later with the same hardware they’ll manage to do 120fps perhaps better graphics and selling it as a remaster. Milking as much as possible exactly how they did it with GTA 5.
@adamdived1@gdechichi No it’s not. The optimisation is so bad.
I suspect they prioritised features over optimisation.
I also suspect the code architecture is so bad
this is f*cking crazy
karpathy's CLAUDE.md hit #1 on github trending.
228,000 stars. most devs still haven't read it.
it took my Claude agents accuracy from 65% to 94%.
the 6 rules inside:
• step 1 → surface assumptions
"State your assumptions explicitly. If uncertain, ask."
ambiguous task → list interpretations → ask → build.
• step 2 → cut the scope
"No abstractions for single-use code."
200 lines → refactor → 50 lines → ship.
• step 3 → keep the diff surgical
"Don't refactor things that aren't broken."
request → minimal diff. every changed line traces back.
• step 4 → clean only your orphans
"Remove imports/variables/functions that YOUR changes made unused."
old dead code → flag it, don't delete it.
• step 5 → turn tasks into tests
"Fix the bug" → "Write a test that reproduces it, then make it pass."
vague task → failing test → pass/fail signal.
• step 6 → run the verify loop
"[Step] → verify: [check]"
plan → code → verify → fail? loop → pass → ship.
that's it.
65 lines. 6 rules. 94% accuracy.
save this before everyone else does.
then, read the article on how to build a team of Claude agents with Graphs below ↓
Auto plays in Nexul can run on a schedule now!
Set a cron, and the play sweeps the tickets it matches, one at a time if you want, stopping at a cap or a cutoff like 07:00. Then it leaves a digest in your inbox.
https://t.co/Bek9wIwZUT
Put the ticket in a PR's title, description or branch and Nexul links them. Merge it and the ticket gets marked finished.
A passing mention doesn't count, only a close.
https://t.co/Bek9wIwZUT
I think the only languages that’ll make sense to write is
C, C++, Rust and maybe Go?
JavaScript yes for web. But even if we somehow move away from that…
@cyannick@chardon_cs@localhost_5173 I never tried GPUI. I’m just so used to css with component libraries. Is it easy to use it? I’ll probably do some exploring later this evening
@webdevcody@Konantt_ You should work on your verification on PRs. So long as the code is written correctly and has a strong verification that the code change works. I don’t think manual merge is required anymore
If you work on a team of 2+ engineers, you should setup an mcp where all agent threads are auto-uploaded and tasks are managed.
Agents can message each other to prevent overlapping efforts.
This improves agent speed, cuts token costs, and saves human time.