uv for Rails Developers: Bundler, rbenv and pipx in One Tool
A Rubyist's guide to uv, the fast Python tool that covers what Bundler, rbenv and gem-installed CLIs do in Ruby, with direct command mappings and a working Flask setup.
One senior engineer, accountable end to end. Modern AI tooling does the heavy lifting; fifteen years of shipping by hand - for Johnson & Johnson, GSK, Babbel, Carwow, Citizens Advice - supply the judgment. You get working software at a fixed price, not a burn rate.
Step 1
One week: your idea becomes a spec, an architecture, and a fixed quote.
Step 2
Fixed-scope build
I build the agreed product with visible progress at every milestone, no surprises.
Step 3
Launch & support
Deployed, documented, and supported after it goes live.
Not a build? I also take contract engagements and fractional support. More on the services page.
When we hand Wagner a build with a hard deadline - a congress opening, a live event - it ships. Complete, working, on the floor when the doors open.
Wagner was enjoyable to work with. He was able to quickly get up to speed, immediately wrapping his brain around problems and shipping clear code to fix them.
Wagner handled our blog migration end to end including migrating all content, URLs and redirects for SEO, and a custom Cloudflare Worker. All documented and deployed with zero drama.
A Rubyist's guide to uv, the fast Python tool that covers what Bundler, rbenv and gem-installed CLIs do in Ruby, with direct command mappings and a working Flask setup.
Anyone hiring one engineer has the same question and almost nobody asks it: what happens after he leaves? This is the honest answer. The two hosts, the checks that run on them, the tool I built to close the two gaps nothing else covered, and what 'supported after launch' actually means when one person is on the hook.
Buyers of AI built software all ask the same question: who checks it? This is my honest answer, using Interlock, the approval gate I am building for my own automated work, as the worked example. Not may I run this, yes or no, but here is a draft, fix the second paragraph, ship what I edited.
Retries, idempotency keys, and dead letters as an evidence problem, how to build Rails webhook delivery that survives a HIPAA audit, not just a happy-path integration test.
Get notified when I publish something new, and unsubscribe at any time.