blundergoat

5 ms·

1.
Show HN: Development Driven Testing, Why TDD Is Not the Best Approach(blundergoat.com)
2 points by blundergoat 6mo ago|0 comments
2.
by blundergoat 7mo ago
fortran > cobol
3.
by blundergoat 7mo ago
The actual license issue is pretty specific. Kimi K2.5 ships under a modified MIT that has one extra clause: if you exceed 100M MAU or $20M/month in revenue, you must prominently display "Kimi K2.5" in your UI. Cursor almost
4.
by blundergoat 7mo ago
The detail about Hoare sitting in the front row at conferences taking notes on specialized topics (after retiring from Oxford, after a Turing Award, after decades of foundational work) is the part of this piece that will stick with me. Ther
5.
by blundergoat 7mo ago
The real win here isn't TS over Rust, it's the O(N²) -> O(N) streaming fix via statement-level caching. That's a 3.3x improvement on its own, independent of language choice. The WASM boundary elimination is 2-4x, but the a
6.
by blundergoat 7mo ago
We treat webhooks as at-least-once delivery over an unreliable transport and design for duplicates and out-of-order events. A few rules that have saved us: - Persist before responding. Never process inline. Write payload to DB, return 200 f
7.
by blundergoat 7mo ago
Duke Nukem 3D was my first experience urinating in a video game. Hail to the king, baby.
8.
Claude Code /insights showed me where my AI workflow breaks down(blundergoat.com)
2 points by blundergoat 8mo ago|0 comments
9.
The worst programmer is your past self, and other egoless programming principles(blundergoat.com)
2 points by blundergoat 8mo ago|0 comments
10.
Code Review for Teams That Ship(blundergoat.com)
1 points by blundergoat 8mo ago|0 comments
11.
by blundergoat 8mo ago
Author here. After years building healthcare software, I noticed most teams treat code review as a quality gate—reviewers re-checking functionality, hunting bugs, re-verifying requirements. That's duplicated work. The developer wrote i
12.
Code Review Best Practices: Focus on Maintainability, Not Correctness(blundergoat.com)
1 points by blundergoat 8mo ago|1 comments
13.
by blundergoat 9mo ago
Happy to discuss the framework or where it breaks down. The TL;DR: ~90% single AI, ~10% signal-triggered multi-AI escalation. The hard part is knowing when to escalate - I use three gut-check signals (Loophole Detector, Annoyance Factor, Sn
14.
Signal-Based Adaptive Orchestration: When to Use One AI vs. Many(blundergoat.com)
1 points by blundergoat 9mo ago|1 comments