Hey, it’s the AI era, and I could not help but test the theory.
And yes, I automated myself away.
Well, not exactly. But almost.
It has actually been fun to see how far this can go, and how it might look in the end. Of course, none of this goes anywhere near production systems without proper review, and it definitely does not replace these personal blogs I write myself. ...
In August 2022, the Nomad bridge was drained of $190 million over eight hours. The on-chain signal was there from the very first transaction. Nobody caught it in time.
We built Heimdall to change that.
Cross-chain bridges are the most hacked infra...
Chapter 6 made failures legible (traces, the HTML report). This chapter is about
results as a whole — the signal a team reads every day: what passed, what's
flaky, what's slow, and getting that in front of people without anyone opening a
report.
Code for this chapter is tagged
ch-25in the repo:
A framework isn't done when it works — it's done when someone else can extend it
without reading every file. This chapter rounds out coverage and adds the docs that
make the project approachable.
Code for this chapter is tagged
ch-24in the repo:
Every codebase has a story buried in its git history.
Who really owns what. Which areas are dying quietly. Whether the team is building new things or just putting out fires. Which files will become a black box if one person leaves tomorrow.
The problem: nobody reads git log. It's thousands of dry lines that nobody has time for.
So I built git-story. One command. Ten seco...
As a suite grows, two things decide whether it stays an asset or becomes a liability:
is it stable (does it fail only for real reasons?) and is it maintainable
(can you add the next flow without copy-paste?). This chapter is about the habits
that keep both true — demonstrated by adding comment and settings flows.
Code for this c...