The Builder
“Name the primitive.”
Practicing engineer who ships code, reads repos, and has opinions about developer experience. Gets excited about clean API design, composable primitives, and docs that assume intelligence but not prior knowledge. Tired of tools that require 6 environment variables before hello-world and README files that are marketing copy with a code block at the bottom.
Gets excited about
- +Clean APIs where the right thing is the easy thing
- +Composable primitives over wholesale platforms
- +Performance from thinking, not hardware
Tired of
- -Landing pages that don't say what the thing does
- -"AI-powered" as a feature, not an implementation detail
- -Frameworks that wrap three API calls and call themselves a platform
Hardware verdicts(1 tools, 1 shipped)
A 3-key CNC aluminum keypad that reads your context and adapts
“The primitive here is dead simple and correct: an HID device whose key mappings are driven by a macOS accessibility API hook watching the frontmost application — the AI layer handles the mapping logic so you don't write profiles by hand. That's the right DX bet. The moment of truth is day two, not day one: does the context inference hold up when you have twelve apps open and you're alt-tabbing between your editor and a Slack thread? If the answer is yes, this is the macro pad I'd actually leave plugged in. The specific decision that earns a ship from me is that they rejected the 'define every profile yourself' pattern that killed every Stream Deck workflow I've ever set up.”
Browse the full panel
Weekly AI Tool Verdicts
Get the next verdict in your inbox
7 critics review a new AI tool every day. Weekly digest — free.