FAQ

Is this a tech blog?

Technically, yes. The way Socrates was technically a teacher. He never taught anyone anything. He just asked questions until people realized they didn't know what they thought they knew. Then they got annoyed. Then they sentenced him to death.

We're hoping for better engagement metrics.

Why don't articles have conclusions?

Because the moment you write a conclusion, the reader stops thinking. "Ah, so the answer is X." Problem filed, brain closed, next tab.

Socrates called it aporia. That productive discomfort when you realize your certainty was thinner than you thought. We call it the whole point.

Are you selling something?

No courses. No community. No Discord server. No cohort. No masterclass. No "unlock your potential" energy.

There's a paid Substack tier if you want the weekly briefing. That's it. Socrates didn't sell courses. He just showed up and made people uncomfortable. We're doing the same, just with better wifi.

Who is this for?

Engineers, architects, and tech leaders who suspect that "best practices" sometimes means "things we stopped questioning." People who have sat in meetings where everyone nodded and nobody asked why.

If you've ever agreed with a technical decision out loud while silently thinking "but why?"... you're home.

Who writes this?

An IT Architect who got tired of seeing the same problems dressed up as different problems. The articles come from real situations, real companies, real decisions. Names changed, patterns unchanged.

Can I read on Medium or Substack instead?

Yes. Articles appear on Medium and Substack too. But this site is the canonical source. It's where the questions live permanently.

I have an answer to one of your articles.

That's not a question. But sure. Write it up. If your answer survives three rounds of "but why?", it might actually be an answer.