bartwaardenburg

4 ms·

1.
by bartwaardenburg 6mo ago
I now it's "yours", but do you know how you differ from for example https://cmux.com/ which I'm happily using right now?
2.
by bartwaardenburg 6mo ago
Thanks for trying it out! Accuracy is the #1 priority every finding should be real and actionable. Glad to hear that's holding up on your project. If you do hit any false positives, please open an issue!
3.
Show HN: Fallow – Find unused code, duplication, and complexity in TS/JS (Rust)(github.com)
4 points by bartwaardenburg 6mo ago|2 comments
4.
by bartwaardenburg 7mo ago
The fields/flags state model is a nice idea, having structured values separate from boolean state is something I haven't seen in other frameworks. How does this compare to Alpine.js or htmx in practice? They're in a similar s
5.
by bartwaardenburg 7mo ago
It's a CLI. CLIs have man pages and cheat sheets. That's not a UX failure, that's the format. The same argument would apply to git, ripgrep, or ffmpeg. The actual complexity in Claude Code isn't the commands, it's f
6.
by bartwaardenburg 7mo ago
This matches my experience. The bottleneck isn't what the agent knows, it's what the agent can verify. A knowledge base tells it "don't do X", but the agent still has to remember to check. Giving it a tool that retu
7.
by bartwaardenburg 7mo ago
This is a good point. For anything without a DOM, screenshot diffing is basically your only option. Mozilla did this for Gecko layout regression testing 20+ years ago and it was remarkably effective. The interesting part now is that you can
8.
The anatomy of a frame(aerotwist.com)
1 points by bartwaardenburg 11y ago|0 comments