From Code to System: Flipping the Switch to an Engineering Mindset
Today I was reviewing a recent performance improvement for one of our systems. Part of the work involved implementing caching for a segment of the process. When I asked how…
Today I was reviewing a recent performance improvement for one of our systems. Part of the work involved implementing caching for a segment of the process. When I asked how…
Many businesses struggle and fail not because of markets, products, or technology—but because of leadership. How leaders think, decide, and act shapes everything: strategy, execution, and culture. The Issues The…
This is the first in a series exploring how Lean principles are often misunderstood in software organizations.We begin with the most abused concept of all: “Eliminate Waste.” The Intent Behind…
I saw a blog post talking about the first principles and find it interesting, here is the excerpt 第一性原理:改變思維方式的力量 The first rule of building wealth is to accumulation, not to…
At a Vancouver tech meetup, I watched a “turnkey AI” demo promise to generate a full chess.com clone from a short prompt—and fail completely. It looked real, but nothing worked. That moment made me question why so many still think software engineering is just coding. Like asking AI to write *The Lord of the Rings* from a paragraph, it misses the point. Software isn’t written—it’s *built* through design, iteration, and judgment. AI won’t replace engineers; it amplifies those who understand the fundamentals.