Search for a command to run...
Hands-on technology leader with 10+ years building scalable, mission-critical systems at Goldman Sachs, Brevan Howard and fast-growing fintechs. Expert in cloud-native architectures, distributed data pipelines and high-throughput systems; experienced in migrating legacy platforms and designing AI-enabled services. Proven track record delivering reliable platforms that process millions of transactions daily.
No comments yet. Be the first to comment.
It’s an Exoskeleton, and That Changes Everything Most people are thinking about AI the wrong way. They imagine it as a coworker:Something you assign tasks to… wait for… and hope it delivers. Sounds re
I didn’t wake up one day and decide, “AI will change everything.”My journey into AI was slower, messier, and honestly… a bit reluctant at first. If you’re a builder, engineer, or curious technologist,
Imagine a programming language designed not just for humans but also for AI.Not adapted for AI. Not retrofitted. Built from scratch so AI can read and write it easily. That’s exactly what NanoLang is. It’s a tiny, experimental language created by vet...
Most PostgreSQL optimization guides feel like laundry lists of settings and indexes. But real performance gains often come from clever ideas, not just the usual tricks. Let’s unpack a few of those ideas in ways that actually make sense for you. These...
Remember when we defeated pop-up ads? Yeah, they're back. And this time, nobody's fighting them. The Good Old Days (Of Terrible Ads) Back around 2000, the internet was a warzone. Visit any website and BAM!!! random windows would explode onto your scr...
Software development isn’t about churning out lines of code and hoping they work. Anyone can generate code, even AI does that now. What separates the pros from the amateurs is this:
No ifs, no maybes, no “let reviewers find the bugs.”
We’ve all seen it: a huge AI-generated pull request lands with no evidence that it actually works. Someone else, usually a reviewer or maintainer, has to chase down bugs, figure out if it even runs, and fix it. That’s not teamwork, that’s dumping your mess on someone else.
That used to be forgivable. Today? There’s no excuse.
A real engineer doesn’t just hope code works. They prove it. There are two essential steps every time:
You must see your code do the right thing yourself.
Run it
Try it
Break it
If you haven’t seen it actually work with your own eyes, it might as well be imaginary.
A smart trick: capture a terminal log or short screen recording that shows your change working and include that in your pull request.
Tests are your safety net, they prove your change still works tomorrow, next month, and after someone else touches it.
Modern tools make this easier than ever. Skip this only if you love bugs.
Manual testing + automated tests = Proof.
Yes, modern coding assistants like Claude Code and Codex CLI can write and test code for you. But that doesn’t mean you can trust them blindly.
You still need to:
Teach the tool to show it tested the code.
Understand the test results.
Add proper automated tests to your repo yourself.
In other words: AI assists, you’re responsible.
Submitting unproven code:
Wastes reviewers’ time
Introduces hidden bugs
Shifts the real work to someone else
Proving your code works:
Saves time
Builds trust
Makes you a stronger engineer
It’s not optional. It’s the real definition of professional software development in an AI-augmented world.
✔ Run your code yourself
✔ Show it works
✔ Add automated tests
✔ Don’t submit anything unless it’s proven
Treat your evidence of working code like gold. Anyone can write lines you prove results.
Source: https://simonwillison.net/2025/Dec/18/code-proven-to-work/