90s Child Tech Skills

What an early lesson in digital weight taught us about building light.

What if I told you the company's logo was built using software skills taught in primary school in the early 1990s?

There is something almost counterintuitive about building a company in 2026 and realizing that one of its most essential visual assets can still be reduced to the same basic digital building blocks we were taught to manipulate as children: pixels, colors, shapes, and proportions.

In large corporations, we usually work within very large teams across strategy, marketing, and advertising, following tried-and-trusted business recipes. New products and rebrand projects can take months as teams discuss, shape and implement what a brand should become and ultimately convey. Yet when you begin removing the fluff, the visual question is surprisingly simple: What should this logo look like? What can be deleted? What is essential enough to keep?

The digital assets we typically hand publishers tend to be quite small. Featherweight is the name of the game. Logos and ads need to work across websites, presentations, social platforms, email, and devices of every size. That means resizing, exporting, and compressing them until they become almost weightless.

But what if we simply reverse engineered for speed?

We often confuse technological sophistication with computational weight. Larger files, more processing power, more features, and more software can create the impression that more machinery must produce a better result.

Often, it does not. Photography went through a similar evolution. For years, megapixel count functioned as shorthand for camera quality. Eventually, that number stopped telling the whole story.

Computers in the 1990s made inefficiencies more obvious. Storage mattered. File size was closely tracked. Websites had to load over dial-up connections. Images had to be compressed deliberately. We learned that digital objects had weight, and that unnecessary weight had consequences.

Being lightweight is intentional and valuable for this studio. Not lightweight in the sense of being underpowered, but in the sense of carrying as little unnecessary baggage as possible. You may begin with a massive layered document and considerable computing capacity. But the object doing the actual work may ultimately weigh 32 KB. What if we simply started there?

And that is how we move. If we want to build the fastest ship in the Milky Way, we need featherweight parts and a lot of engine.