6 posts tagged with "thinking"

In my earlier post, Shakespeare and Dataism, I argued that incomplete information creates drama, surprise, and joy. Perfect information flattens experience.

If perfect knowledge is the theoretical endpoint of human understanding—an omniscient, frictionless clarity—then perhaps its inverse, incomplete information, is the essential condition of drama, comedy, and life itself.

A Product Manager is supposed to be the great connector—the person who brings engineering, design, and business together. PMs are expected to be curious, collaborative, and customer-obsessed. They align stakeholders, navigate ambiguity, and create clarity from chaos. They're not the boss, but they lead. Not the expert, but the glue.

I recently ran a values exercise with a team of engineers in 1-1s. Each had to select three sticky-notes from a predefined set of values. Every single one of them chose Cooperation.

When we asked what cooperation meant, I got five completely different answers:

I've been doing a lot of vibe coding, and my particular tools of choice include v0.dev (as a Vercelvercel Vercel is a cloud platform for frontend developers. It is used to deploy and host websites and web applications. fanboy). By default, v0 will use tailwind for styling. This means I've been using Tailwind for the first time, and... I hate it.

In software engineering, complexity often masquerades as sophistication. Nowhere is this clearer than in frontend code that relies on inferential logic: the practice of deducing user intent or state based on limited information, rather than explicitly guiding the user experience.