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
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...
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, you might recognize yourself in this story.
When modern AI tools first exploded onto the scene, I wasn’t impressed.
Yes, they could generate text.
Yes, they could answer questions.
But most outputs felt shallow, generic, and occasionally wrong in confident ways, the worst combination.
As someone who cares deeply about craft, correctness, and depth, I didn’t see how this could fit into serious work. It felt like autocomplete on steroids, not a real collaborator.
So I ignored it.
Big mistake.
Eventually curiosity got the better of me. I started experimenting cautiously.
Not for important work. Not for anything critical.
Just small tasks:
Brainstorming ideas
Summarising articles
Generating rough outlines
Exploring unfamiliar topics
And something surprising happened.
AI wasn’t useful because it was perfect.
It was useful because it was fast.
It became a thinking amplifier.
Instead of staring at a blank page, I now had a messy draft to react to.
Instead of spending hours researching basics, I had a starting map.
The value wasn’t in the answers, it was in momentum.
Then came the turning point: using AI for real work.
Not toy tasks. Not experiments.
Actual productivity.
I started with areas where speed mattered more than perfection:
Drafts that used to take hours suddenly took minutes.
Not publish-ready but close enough that editing was faster than starting from scratch.
AI didn’t replace engineering skill.
But it removed friction:
Boilerplate code
Test scaffolding
Documentation
Refactoring suggestions
It felt like having a junior engineer who never got tired and responded instantly.
AI became the fastest tutor I’ve ever had.
Instead of hunting through documentation, I could ask:
“Explain this concept simply.”
“Give me examples.”
“Compare approaches.”
The feedback loop shrank dramatically.
At this point, AI stopped being a tool and started becoming part of my workflow.
I began to think differently about tasks:
Old mindset:
“How do I do this?”
New mindset:
“How do I collaborate with AI to do this faster and better?”
This shift is subtle but powerful.
AI works best when you treat it as:
A brainstorming partner
A rapid prototyper
A tireless assistant
A second brain
Not as an oracle.
The biggest unlock was learning to iterate.
The first output is rarely great.
But the fifth interaction often is.
Here’s the insight that changed everything:
AI compresses the distance between idea and execution.
Things that used to feel like “maybe someday” projects suddenly became weekend experiments.
You can:
Explore new domains without months of ramp-up
Prototype ideas quickly
Validate concepts before committing
Move from thought → artifact almost instantly
It lowers the cost of trying.
And when trying becomes cheap, innovation accelerates.
AI is powerful but not magical.
It still:
Makes mistakes
Lacks true understanding
Requires guidance
Needs verification
Blind trust is dangerous.
But total skepticism is equally limiting.
The winning strategy is informed partnership:
Trust, but verify.
Use it aggressively, but critically.
Leverage speed, guard quality.
Today, AI touches almost everything I do:
Writing
Coding
Research
Planning
Learning
Decision support
Not because it replaces skill but because it multiplies it.
The best way to describe it:
AI is like giving your brain a high-speed interface.
You still steer.
You still decide.
You still own the outcome.
But the friction is dramatically lower.
If you’re still on the fence, here’s what I wish someone had told me earlier:
Don’t wait for the perfect use case.
Use it for low-risk tasks first.
Momentum builds confidence.
Good results come from dialogue, not one-shot questions.
Start from something. Refine. Clarify. Push deeper.
AI shines in early stages:
Exploration
Drafting
Brainstorming
Prototyping
Your judgment is the quality filter.
AI without human oversight produces mediocrity.
AI guided by expertise produces leverage.
Not using AI today is like ignoring the internet in the late 90s.
You might survive for a while.
But you’ll slowly fall behind people who amplify themselves.
My AI adoption journey wasn’t about discovering a magic tool.
It was about discovering a new way to work.
AI doesn’t replace builders. It upgrades them.
And the people who learn to collaborate with it early will have an unfair advantage for years to come.
===
Source: My experience plus https://mitchellh.com/writing/my-ai-adoption-journey