A little over a year ago, I wrote a post called “The Year of the Kiwi.”
At the time, Kiwi Engine was still mostly an idea.
Not in the “idea guy” sense — but in the sense that the architecture existed more in notebooks, diagrams, experiments, prototypes, and long nights of thinking than in polished products.
It was a collection of philosophies:
modularity over monoliths
contracts over assumptions
pipelines over hooks
systems over trends
stewardship over convenience
architecture over hype
And honestly, at the time, I wasn’t entirely sure how far the idea would go.
I just knew I couldn’t shake the feeling that modern development had become increasingly chaotic.
Every few months:
a new framework
a new “must-use” stack
another rewrite
another abstraction
another platform trying to become the platform
another ecosystem lock-in strategy disguised as “developer experience”
Meanwhile, developers and businesses are left carrying the long-term weight of those decisions.
Over the last year, I’ve…