Green Paint and Data Types
By Toria · Published May 6, 2025
Data Explorer · Systems Thinker · Writer in Progress
Photo by Greg Galas from Pexels
The Unexpected Lesson Behind a Simple Task
This is one of my earliest ‘whoa’ moments — a point where something that felt small suddenly expanded into a much bigger understanding. It happened in my first role as a Junior BI Developer. I’d been given a task to run an Excel file through SSIS and map it to one of our data tables. My team told me it was something simple, done monthly — no issues expected.
First Run, First Error
First run? Errors.
Of course I got errors, I thought — it’s me. Nothing’s ever that straightforward. I Googled the error, found a forum, followed the advice, and it worked. But… something didn’t feel right. I couldn’t let it go. Why did I have to change the data type to something that felt totally random? A string’s a string, a number’s a number, right?
Seeing What Data Types Really Represent
That’s when it hit me. It wasn’t just about choosing from a dropdown menu. Each data type had meaning — not just in terms of what it represents, but how much space it uses, how it’s stored. It’s like loading a voucher card: you preload it with a set amount, and once that’s used, there’s no overflow. Data types are the same — you’re setting the size and format before anything’s even stored.
Photo by Niklas Jeromin from Pexels
Every bit counts
What blew my mind was the idea that each character, whether part of a string or a number, carries its own data cost. It’s our data currency — bits and bytes. And while today’s cloud infrastructure means we don’t have to be quite so picky about storage, the concept still holds. It’s a bit like money: we used to be more careful about what we spent when cash was physical, but now most payments happen online, often invisibly. Data works the same — just because storage is abstracted, doesn’t mean the cost disappears
The Value of the Error
Looking back, if I hadn’t got that error, I probably wouldn’t have questioned it. I might’ve kept thinking that data types were just fancy alternative names for the same thing — like choosing ‘Jungle Fern’ instead of ‘Forest Mist’ when you just want to paint the room green. But they’re not just cosmetic choices. They’re decisions about form, space, and meaning.
From Fixing a Bug to Seeing the Bigger Picture
That one small bug gave me one of my first real glimpses into systems thinking — that beneath every interface is architecture. Even something as ordinary as a drop-down list of types can reflect an entire philosophy of structure. It taught me that curiosity, especially when something doesn’t feel right, is often the first step toward deeper understanding.
Written by Toria
Data Constellations — For layered thinkers, quiet disruptors, and curious minds.
Keep exploring the patterns others don’t always see.