Professional survivor of enterprise enthusiasm

Software obeys instructions
instead of intentions

Most organizational problems eventually become technical problems after enough meetings. Most technical problems become organizational problems after enough PowerPoint.

Several
Root Causes Rebranded as Strategy
Countless
Temporary Solutions Approaching Adolescence
Unexpectedly High
Green Dashboards During Active Failures
Calibrated for environments where "lessons learned" means "same incident, different fiscal year."
Digital Transformation AI Strategy Platform Modernization Cloud Journey Innovation Labs Synergy Technical Debt (exists somewhere else) Legacy Systems (created three years ago) Microservices Monoliths Distributed Monoliths Temporary Solutions (since before Git)
Architecture diagram omitting the failing component
01

Architecture discussions become sociology

Every organization claims to value honesty — until it acquires a budget estimate. Requirements become negotiations between physics and optimism, and nothing scales faster than responsibility moving sideways.

Dashboard that stays healthy during active failures
02

Every incident introduces itself politely first

Known issue. Corner case. Rare. User error. Low priority. Then production develops a different opinion, long after the dashboards stopped agreeing with it.

Kubernetes solving problems it also created
03

Every abstraction promises simplicity. Most deliver archaeology

Automation doesn't remove mistakes — it helps mistakes discover parallel processing. Kubernetes has solved many important problems. Roughly half were created by Kubernetes.

Choose whichever model procurement tolerates

The outcome remains approximately the same. Continue only if the problem survives contact with reality.

Consulting
Implementation Clear Terms
Usual Starting Point
Discovery
Per session
450 USD
60 min
Focused audit
3,500 USD
1–2 weeks

One hour, mostly spent discovering the original question was decorative. Usually confirms what everyone already suspected — now with diagrams.

  • Problem diagnosis
  • Architecture review
  • Written summary
  • Likely direction
  • Technical reality check
Book Discovery
Usual Starting Point
Advisory
Monthly
4,000 USD
Retainer
Embedded
8,000 USD
Monthly

Attend meetings. Prevent future conference talks that begin with "Looking back, there were warning signs..."

  • Technical advisory
  • Architecture reviews
  • Strategic direction
  • Executive briefings
  • Priority access
  • Long-term guidance
  • Ongoing refinement
Inquire Advisory

Things that remain true whether or not anyone likes them

"Every rewrite eventually becomes legacy."

01
First Principle
Painfully True

"Every permanent solution began as 'just for now.'"

02
Second Principle
Painfully True

"The fastest database query remains deleting the dashboard."

03
Third Principle
Painfully True

Recurring organizational phenomena

Patterns that reappear across engineering, analytics, infrastructure, and intelligent systems, regardless of the org chart drawn around them.

Renaming Projects, Not Fixing Them
Productivity by Calendar Invitation
Consultants Validating Decisions Made
Documentation via Tribal Folklore
Six Approvals for One SQL Query
Discovering DevOps via Job Title
Platforms Nobody Requested
Frameworks to Avoid Frameworks
APIs Designed Before Agreeing on Nouns
Six Months Selecting Issue Trackers
Optimizing Before Confirming Users Exist
Migrating Everything but the Problems

Questions people ask when they are still being polite

Legacy systems generally work. That is why everyone is afraid of touching them.
Excellent. Now it resembles reality.
Certainly. Whether it solves the correct problem remains a separate discussion.
Roadmaps are among humanity's most optimistic literary genres.
The slides must have been magnificent.