2026-08-20
AI Wasn’t Always This Good. We Just Got Used to It.
AI is rapidly changing team capacity and software economics. That calls for a fair view of the past—and new expectations for today.
Read →5 min
Business-first AI transformation
I've engineered software for 25+ years. With AI's power behind me, I build more ambitiously than ever — and write, from the trenches, about what AI actually changes.
I write about how businesses can use AI, software, data, and process redesign to create measurable value — starting with the business problem, not the technology.
I've been building software since 1998.
My perspective comes from both writing code and leading technology teams.
I care less about what AI can demo, and more about what it can improve in a real business.
Essays
Start here
Recent writing on AI, software, and business.
2026-08-18
AI Made Code Cheap. Verification Is Still Expensive.
AI can produce an implementation in hours. If its author cannot explain the decisions behind it, the real engineering work has not disappeared — it has moved to the reviewer.
Read →8 min
2026-06-28
The Threshold Collapsed to Zero: Building in Public in the Age of AI Cloning
Arvid Kahl, one of the pioneers of the "build in public" movement in the software world, made a confession in recent months (April 2026) that fundamentally shook his own thesis. After years of advocating for sharing metrics, processes, and financial data transparently, Kahl stated that the "safe sharing threshold has collapsed to zero" due to the speed AI has reached. Now, every metric and architectural detail you share openly turns into a cloning blueprint that AI agents can replicate over a weekend.
Read →4 min
More writing
Build in Public 2.0: The New Playbook for Sharing Openly in the Age of AI Cloning
Read →3 min
AI Citations Run on a Separate Clock: What Google's Generative AI Data Revealed
Read →8 min
The Era of the "Previous Vibe Coder" Begins: The Invisibility of Clean Code and the Technical Debt Bill of AI
Read →8 min
One Victory, Several Defeats
Read →3 min
The Job AI Won't Take — and the Five It Quietly Prevents
Read →11 min
ProductLog: The Platform I Built for Myself First
Read →3 min
Comprehension Debt: The Bill Comes Due Alone
Read →8 min
The New Evrenbal.com: A New Era and Blogging Philosophy
Read →3 min
The AI Visibility Illusion: What Bing's Citation Share Data Actually Reveals
Read →9 min
1M Impressions per Month, $0 Revenue: A Programmatic SEO Post-Mortem
Read →4 min
The End of Coding or a New Renaissance? The Invisible Crisis of AI
Read →6 min
Raising Children in the Age of Artificial Intelligence
Read →11 min
Technical writing
Technical writing
Hands-on notes and tutorials on Go, Linux, Docker, web fundamentals, and more—with new technical writing added as I publish it.
Do You Need a Paid CMP for Google Consent Mode v2?
Read →19 min
What Should the REST API URI Structure Be?
Read →5 min
How to Secure a REST API?
Read →5 min
How to Perform REST API Error Handling?
Read →4 min
How to Document and Test a REST API?
Read →7 min
REST API Design: Principles and Output Format
Read →5 min
How to Perform REST API Authentication?
Read →8 min
Sample REST API Project
Read →8 min
Business-first AI transformation
Browse by topic
01
AI where it changes the business
What matters is not the model, but the decision, workflow, or economics it changes.
Explore AI writing →02How work actually moves
Processes, handoffs, information, and decisions are where operational friction becomes visible.
Explore business writing →03Engineering that can carry the work
Architecture, infrastructure, and implementation determine whether an idea becomes dependable.
Explore engineering writing →Business-first AI transformation
How I evaluate a change
I first try to understand what needs to change. I choose the technology only after the problem, expected benefit, and cost are clear.
- 01
Goal
What should improve: cost, speed, capacity, quality, or revenue?
- 02
Current state
How does the work happen today, and where are time, money, or knowledge being lost?
- 03
Looking ahead
Even if I do not act today, I consider likely scenarios. A small preparation now can prevent far more work later.
- 04
Priority
Which change is most likely to produce a meaningful result?
- 05
Benefit and cost
Is the expected gain worth the cost, effort, and risk?
- 06
Workflow
What should be removed or changed before anything is automated?
- 07
Approach
Would AI, software, an existing product, or a process change be the best fit?
- 08
Implementation and measurement
Put the change into practice and measure what actually improves.
Business-first AI transformation
Field notes
Short accounts from systems built in the real world, with the details that made them useful.
Lead operations
100K annual leads
From Rules to Decisions: The Real-Time Sales Intelligence Platform We Built at Vanity
A real-time decision-support and sales-management platform for routing, payments, and management visibility.
Read →Patient conversations
One year of multichannel chat
Beyond the bot: lessons from building a chat system for global patients
What emerged from building and operating a chat system for patients across channels.
Read →Small infrastructure
$5/month small VPS
How I Built a Modern Infrastructure Using Open Source Tools and the Power of Cloudflare
A modern open-source infrastructure assembled with a small server and Cloudflare.
Read →About
I build software, lead technology teams, and write about what I learn.
This site is where I share notes on AI, software, the products I build, and the problems I encounter at work.