📰 Dev.to · machuz

Taste is formed by class and history (Bourdieu). But in Japan, manga worked as a democratization device for cultural capital. How aesthetics rises from a place

Why this book ended up as a dual structure (structure-driven × Psychological OS), a 10-question self-diagnostic for individuals and organizations, and the full

When a strong Psychological OS enters an organization, both sides break each other. The mechanism: mutual destruction, not malice. One reason the startup death

Chapter 3 showed why Psychological OS and organization destroy each other. This chapter shows the only way they stop: dual design — translation on the individua

A strong Psychological OS isn't perfection. It's heat kept pointing inward, attachment directed to the right target, and vectors aligned so external pressure do

You can't directly observe your own Psychological OS — observer and observed are the same system. Three paths that create distance, and a practical case of usin

An operating principle for staying yourself. Why some people keep their heat while others lose it — and what the invisible base layer of decision-making really

A 3-minute intro to Engineering Impact Signal — an OSS CLI that quantifies engineering impact from git log and git blame alone. No API keys, no AI tokens.

16 chapters condensed: how git log and git blame reveal engineer gravity, team health, software cosmology, and why AI creates stars but not gravity.

Git remembers the past. AI imagines the future. Between them, engineers shape gravity.

AI creates stars. But it doesn't create gravity. What happens when code universes experience their first starburst?

Most code universes die. Only a few become civilizations — self-sustaining structures that outlast their creators.

AI creates stars. But it doesn't create gravity. What happens when code universes experience their first starburst?

Most code universes die. Only a few become civilizations — self-sustaining structures that outlast their creators.

Final chapter of Engineering Impact Signal. Git archaeology is the astronomy of code universes.

Chapter 12 of Engineering Impact Signal. Not all strong gravity is good gravity. Some engineers create structure that survives their departure. Others create gr

Chapter 11 of Engineering Impact Signal. Entropy always increases. Engineers fight it.

Chapter 10 of Engineering Impact Signal. Most of the universe's mass is invisible. The same is true in code universes.

Chapter 9 of Engineering Impact Score. Every universe has an origin. In code universes, it's the first commit.

Chapter 8 of Engineering Impact Score. The same engineer produces different EIS scores in different codebases — and that's not a bug, it's physics.

Chapter 7 of Engineering Impact Signal. Codebases have gravitational structures. Great engineers don't just write code — they bend the gravity of codebases.

Chapter 6 of Engineering Impact Score. When individual changes ripple into team-level shifts, patterns emerge — and those patterns have laws.

Chapter 5 of Engineering Impact Signal. When you line up quarterly snapshots, numbers start telling stories — including the ones people don't talk about.

Chapter 4 of Engineering Impact Signal. Backend teams evolve differently — and departed Architects leave souls that must be laid to rest.