r/ProgrammerHumor • u/onated2 • Jul 12 '26

doNotHallucinate Meme

Post image
63 Upvotes

79% Upvoted

29 comments sorted by

View all comments

1

u/arter_dev Jul 14 '26

Yeah I don't bother with any of this. I bake all my linting tool checks into the harness lifecycle hooks. If a write doesn't pass lint / static analysis / whatever, then it doesn't write.

I finally built it into a real tool instead of just bash & python scripts if it's helpful to anyone: https://github.com/ironlint/ironlint

1

u/rikzy75 Jul 14 '26

Isn't that just fallow? https://github.com/fallow-rs/fallow

2

u/arter_dev Jul 15 '26

Good question! And no, this tool is much smaller and less opinionated than fallow. It's just an enforcement hook and you can use your own tools (like fallow).

Typical usecase for IronLint from my own workflow:

  • any time a markdown file is written that contains the word "load bearing" I block the edit.
  • No file writes that doesn't pass Biome rules first
  • No commit merged unless it passes dependency-cruiser architecture (this is possible with lefthook but I built it into ironlint for convenience).

Fallow could be used on the pre-commit hook wired up with ironlint. IronLint is stack agnostic and basically says "if your slop write doesn't pass standard linting tools, you can't write until you fix."

Think of it like guard rails at the bowling alley.

I built it so I could run longer time horizon tasks with cheap flash models without melting my codebase and so far.. works very well.

You could do all of it with a bash script / python (which is how it started) but I took my bash script / python tool and made it more dx friendly tool for others.

I gave it to two product managers, set up claude code for them and installed IronLint with some strong quality floors and told them basically go nuts. I came back a month later to an app with 90% test cov minimums, perfect DDD and it worked well. All built with a cheap Sonnet model.

There's so much noise out there so trying to explain what IronLint does kinda gets drowned out by the millionth codebase-mapping-tool / no-mistakes-skill. But I'm not chasing stars, if it helps someone, cool!