Networking · Infrastructure · Design

If It Only Works for Me, It Doesn't Work.

When I started this blog, it was simply an excuse to write.

A place to document ideas, experiments, and the occasional lesson learned after breaking something.

My homelab started the same way. It began as a technical challenge. I wanted more control over my own infrastructure. More privacy. More ownership over the services I used every day.

At first, everything was built for one person. Me. I knew every IP address. Every port. Every password. Every service had its own bookmark, its own shortcut, its own way of being accessed.

That worked — but only for me.

If every new application requires me to explain "go to this IP address, on this port" — I haven't built a useful system. I've built a puzzle.

The Realization

This infrastructure isn't just mine.

My wife uses it. My children use it. Guests will eventually use parts of it. And hopefully, years from now, they'll use services I haven't even deployed yet.

If every new application requires me to explain "go to this IP address, on this port, using this browser" — then I haven't built a useful system. I've built a puzzle.

Don't Make Me Think

The best systems don't ask users to remember.

One idea has been influencing my thinking for years: Don't Make Me Think. Steve Krug wrote about it in the context of web design, but I believe the principle applies almost everywhere. The best systems don't ask users to remember. They don't require explanations. They simply make the right thing obvious.

I realized my homelab deserved the same treatment.

The Solution

Names instead of numbers.

Instead of asking people to remember addresses like 192.168.2.114:8080 or 192.168.2.20:2283, I configured local DNS records in Pi-hole so every service now has a name:

Local DNS records

firewall.home
dns.home
nas.home
fotos.home
music.home
servicios.home

Pi-hole Local DNS — 6 registros activos, nombres en vez de IPs.

Nobody has to remember where a service lives. Only what it does.

The Launcher

A starting point for everyone in the house.

I built a launcher that lives on any device in the house — a simple page that shows only what's relevant to each person. Not because they need access to everything. Quite the opposite.

The goal isn't to expose every service. The goal is to make the available ones effortless to find. No documentation. No explanations. No technical knowledge required.

It runs on the NUC — the machine that's always on — served by a simple Nginx container. Any device on the network opens servicios.home:8888 and sees it immediately.

Servicios activos y planificados — cada uno con nombre, no con IP.

El launcher abierto en el Pixel — accesible desde cualquier dispositivo en la red.

The Philosophy

This may seem like a small change. Philosophically, it changes everything.

The infrastructure stops feeling like a collection of servers and starts feeling like a product. One designed for people instead of administrators.

Eventually I want to add much more — a local AI assistant, a family wiki, a digital library, internal tools, automation. The list keeps growing. But I've learned something important: every new service should become easier to discover, not harder. Adding functionality should never increase complexity.

External access is a completely different problem. That requires authentication, permissions, reverse proxies, VPNs, and much stricter security. I'll write about that separately.

Inside my network, my philosophy is simple: if someone has permission to use a service, they shouldn't have to think about how to reach it. They should simply open it.

The Point

A well-designed system disappears.

The funny thing is that this has very little to do with servers. It's really about design. A well-designed system disappears. People stop thinking about how to use it and simply use it.

That's the kind of infrastructure I want to build. Not one that impresses me. One that quietly works for everyone else.

If someone has permission to use a service, they shouldn't have to think about how to reach it. They should simply open it.

How do you handle service discovery in your homelab? Drop it below.

This post contains Amazon affiliate links. If you purchase through them, I may earn a small commission at no extra cost to you. Every product listed here is something I personally own and use daily.

Read More

Philosophy · Design · A Life's Work

This is the final post in the six-part series Build Different — How I Think. If you haven't read the others, they're all worth starting from the beginning.

Designing Around Constraints.

I never start from a blank canvas. A blank canvas paralyzes me. I need something to push against — a restriction, a problem, a condition I can't ignore — before anything starts to move.

That's not a limitation I learned to work around. It's how I've always worked. And it took me most of my life to understand that it wasn't a flaw.

You never start from a blank canvas. You start from what's already there.

Before the Tools

A blank surface with no rules was uninteresting. A surface with limitations gave me something to design inside.

Before computers, before software, before design school — I drew.

Not on paper, necessarily. There were pieces of plaster chalk near the house growing up. We used them to draw on the street. In another neighborhood, I used markers on walls. Almost always monochromatic. Patterns. Mosaics. Geometric shapes on sidewalks. Not flowers or vases — my mother enrolled me in drawing classes and I was bored immediately. Still life didn't interest me. A mosaic on a sidewalk did.

I didn't know why at the time. I know now: my brain needed structure and repetition. A blank surface with no rules was uninteresting. A surface with limitations — the shape of a sidewalk tile, the width of a chalk line — gave me something to design inside.

My Father's Method

He never praised good grades. He rewarded good understanding.

My father was an engineer with more than 35 years of experience. And he had an ability that I've never seen replicated: he could explain anything to anyone using whatever was at hand.

If the person listening was an upholsterer, he explained mechanical engineering through upholstery. If they worked in pastry, he explained it through baking. If they were a designer, he spoke in design. He adapted the explanation to the way the other person processed information — not to show off, but because getting the concept across was what mattered. The medium was irrelevant. The understanding was everything.

He never praised good grades. He rewarded good understanding. His rule was simple: understand the concept first — everything else follows. Decompose the knowledge, then recompose it in a way you can work with.

I didn't know at the time that I was learning a method. I was just a sponge — absorbing everything from everyone, especially him. But that instruction became the foundation of everything I've done since: find the formula hidden inside the problem, understand it completely, and then you'll know exactly what needs to be done.

I spent 25 years absorbing that — from birth until I left home. I became an expert at seeing the world the way he saw it.

What I didn't know until much later was that this was also how he worked. He collaborated with presidents, with multinationals, with international organizations. He solved problems of extraordinary complexity. And he never announced it. He walked down the street like anyone else. The people who needed to know what he had done — knew. And they sent others. Always by referral. Always because the work spoke before he did.

I watched that for 25 years. And I absorbed it without realizing I was learning anything.

1998. The First Computer.

The blank canvas never inspired me. A specific goal always did.

I was twelve. A PC arrived at the house. I discovered the internet — version 1.0. I spent time searching for images. When I learned I could change the desktop background, that became the daily goal. Change the wallpaper. Find something better. Change it again.

That obsession led to the first practical design decisions I ever made: a folder with dividers, printed and organized. Covers printed for notebooks. Not design projects — just solutions to small needs with the tools I had.

Then came the tutorials. Photoshop at 13. 3DS Max at 15. Freehand, Illustrator, After Effects. I learned the tools without knowing the theory behind them. I designed without structure. The blank canvas never inspired me — but a specific goal always did. Make this wallpaper. Build this effect. Solve this visual problem.

University — The Why Behind the How

The university didn't teach me to design. It taught me to think in design.

I arrived at university thinking I already knew how to design. I had the tools. I had the hours. What I didn't have was the vocabulary for why anything worked.

Balance. Hierarchy. Alignment. Typography. Proportion. Repetition. Color theory. Psychology of form. High contrast techniques. Pointillism. Building a color chart from scratch. At first it felt unexpected. Then it clicked.

Every assignment arrived as a restriction — a format, a brief, a set of rules. And automatically, before I started, I already knew the direction. The constraint didn't block me. It activated me.

A friend told me after graduation that university had been easy for me because I already knew how to design. It bothered me — it made my effort seem small. I told him: the university didn't teach me to design. It taught me to think in design. I didn't fully understand what I meant until years later.

2009 — The First Hard Technical Constraint

The tightest technical constraints produced the most creative solutions.

One of my first projects after university was building a virtual world inside a web browser. This was 2009. HTML5 didn't exist yet. Web-based 3D engines were in their infancy.

I joined the team and proposed a change: use a game engine to render everything in real time inside the browser. The restriction was severe — limited polygons, baked renders, textures compressed to 1024 pixels, all running inside a browser that wasn't designed for any of it.

It didn't last long. The funding ran out. But the lesson stayed: the tightest technical constraints produced the most creative solutions. Not despite the limitations — because of them.

The Paint Factory

The box changed. The approach didn't.

After that came the paint factory — the leading brand in the Dominican Republic. Pre-made label templates. Specific color systems. Budget limits at every level. Design that had to work within the brand, within the printing process, within the cost structure. The box changed. The approach didn't.

SIUBEN — 2013. The Hardest Brief.

How do I make someone want to look at this?

I became a father before I started at SIUBEN. I arrived focused on design. The real challenge came with the first book — a national statistical study. Hundreds of pages of data. Complex tables. Dense numbers.

I physically rejected looking at a complex statistical table — and I had to make one readable. If you've read the previous post in this series, you already know why that rejection wasn't just aesthetic.

I asked myself: how do I make someone want to look at this?

The answer was the same process I had been using my whole life, applied to data for the first time: Understand the data. Decompose it into parts. Restructure it into something worth seeing.

I used the same design principles I had learned in university — contrast, form, hierarchy, typography, negative space — but applied them to statistics instead of graphics. I didn't discover how to make infographics. I discovered I already knew how. I just hadn't applied it to data yet.

The publication was a significant success. Then I repeated the model. Understand. Decompose. Restructure. Every time.

The Formula Behind Everything

Every field has a formula. The skill is understanding it — and then designing inside it.

After 20 years of working across graphic design, communications, government, construction, and technology, I've noticed that every discipline follows the same structure:

The structures

Methodology of Research
Problem → (Data + Analysis) → Interpretation → Knowledge

Creative Brief
Challenge / Need → (Audience + Insight) → Key Message → Creative Solution

Advertising Campaign
Objective → (Insight + Creative Concept) → Media Plan → Impact / Conversion

Homelab
Need / Use Case → (Hardware + Software) → Configuration → Functional Service / Automation

3D Design / Render
Concept / Plans → (Modeling + Texturing) → Lighting / Render → Final Image / Animation

Software Development
Requirement → (Code + Logic) → Testing → Deployed Application

Fabrication / Workshop
Design / Diagram → (Cutting + Assembly) → Finishing → Completed Piece / Furniture

The domain changes. The structure doesn't. Every field has a formula. The skill is understanding it — and then designing inside it.

Working Behind the Scenes

Not visibility. Function.

My father never walked around showing his portfolio like a business card waiting to be praised. He worked hard. He did it right. He didn't announce it. And the right people always found him.

I learned that by watching him for 25 years — not because he taught it as a lesson, but because it was simply how he lived.

In almost 20 years of professional work, I've worked with every type of client — commercial, institutional, governmental, international. I've never entered a competition. I've rarely shown my work publicly. What exists is on Behance and Dribbble — and most of it is years old. The rest belongs to the people it was built for, under agreements that prevent me from showing it.

That aligns with something I've understood about myself for a long time: I work best as the number two. The person who makes things function without needing to be the protagonist. The one who finds the solution inside the constraint and hands it off without a signature.

There is a specific pleasure in watching something work — a system, a publication, a network, a kitchen — and knowing that you built it, without needing anyone else to know. My father taught me that pleasure. He lived it for 35 years. He worked with presidents and walked down the street like anyone else.

That's the version of success I understand best. Not visibility. Function.

The Closing

And what's already there is always enough to build something worth building.

My father simplified complexity. My mother invested in therapy I didn't understand at the time. The university gave me vocabulary for instincts I already had. Twenty years of clients gave me constraints I couldn't ignore. And every restriction — economic, technical, physical, temporal — produced work that unlimited freedom never would have.

You never start from a blank canvas. You start from what's already there.

And what's already there is always enough to build something worth building.

If any part of this series connected with the way you work — drop it below. I'd genuinely like to know.

Build Different — How I Think · Complete Series

Post 1 — Embrace the Mistake
Post 2 — Think Inside the Box
Post 3 — If I Have to Do It Twice, I Build a System
Post 4 — If I Can't See It, I Don't Understand It
Post 5 — Everything Wants a Second Life
Post 6 — Designing Around Constraints

This post contains Amazon affiliate links. If you purchase through them, I may earn a small commission at no extra cost to you. Every product listed here is something I personally own and use daily.

Read More

Philosophy · Mind · Visual Thinking

"I swear to you, gentlemen, that to be too conscious is an illness — a real thorough-going illness."

— Fyodor Dostoevsky, Notes from Underground (1864)

If I Can't See It, I Don't Understand It.

I found out I was dyslexic as an adult. Not from a doctor. Not from a formal evaluation. From a style consultant who noticed a pattern during a 400-page document review session — and typed "dyslexia indicators" into Google while I watched.

Every item on the list was a click. Every description was my life. And instead of feeling like something was wrong with me, I felt something I hadn't expected: relief. I had just put a name on a way of thinking I'd had since childhood.

This is that story — from the beginning.

The Beginning

My mother never called it therapy. She called it extra class.

When I transitioned from kindergarten to primary school, something happened. I don't remember the details — I was a child. What I do remember is that my mother received information, and that summer before first grade I spent my vacation in what she called a "homework room." A special leveling course. For me, it was just class.

From second grade onward, I always had somewhere to go after school. A homework room. Educational therapy. Some kind of specialist. The locations changed. The content was always the same: mathematics, which was always relatively easy for me, and calligraphy. Endless calligraphy.

My mother never explained why. I never asked. I was a child — I assumed it was just something children did.

What I do remember is a specialist telling her — not me — that my brain recognized patterns faster than normal. That I thought quickly. My father later mentioned that someone once told them I had the mental ability to disassemble something in my mind without ever having seen it taken apart.

Nobody told me any of this at the time. For me, it was just extra class.

The Calligraphy

Twelve years of the same cursive system. From second grade to the last day of high school.

My school had its own cursive calligraphy system and required every student to maintain it. Combined with the therapy sessions, I spent years doing calligraphy. It was repetitive. It exhausted me. And somewhere in that exhaustion, I started looking for ways to do it faster without losing legibility.

My handwriting was never beautiful. But it was readable. That was enough.

Looking back, I think those years of forced repetition planted something. The instinct to find a faster path through a repetitive task — without abandoning the result — started earlier than I realized.

The Method

I didn't memorize what the book said. I understood what the topic meant.

Grammar was always the exception. It still is. Words that sound identical to me but apparently have different accents, different meanings, different rules. I passed grammar with the minimum required grade. I think some teachers passed me out of sympathy — or out of recognition that I understood everything else.

Because in the subjects that made sense to me — mathematics, physics, chemistry, biology — I excelled. I became addicted to Discovery Channel and National Geographic documentaries. Not as entertainment. As input. My brain absorbed scientific information through video in a way it never could through text.

When I had to give presentations, I stopped trying to memorize the material. Instead, I took the topic, mixed it with information from a documentary I already had in my head, and explained it in my own words. I didn't say what the book said — I said more than the book said. And the teachers loved it.

I could explain how the heart works by comparing it to a car engine. I could explain mathematics using chairs and cushions instead of numbers. I could explain physics concepts using things I'd seen in documentaries that had nothing to do with the textbook.

Understanding the concept was worth more than memorizing the answer. I just didn't know yet that this wasn't how everyone's brain worked.

The Notebooks

My notebooks weren't notes. They were infographics.

During every class, if there was a formula, a scientific explanation, or a concept I needed to hold onto, I would draw around it. A box around a key word. An arrow connecting two ideas. An icon next to a concept. A rough sketch of something the teacher described verbally.

My notebooks weren't beautiful. They were full of irregular shapes, marks, and drawings. For anyone else looking at them: chaos. For me: a system that worked perfectly. I understood my own visual language better than any clean set of written notes.

When the consultant named my condition years later, one of the first things that made sense was this. The tendency to take notes with graphics and very few words wasn't a study habit I'd developed. It was how my brain processed information. I just hadn't known to call it anything.

The Psychologist

She didn't name it. But she got close.

Before I finished high school, I spent about a week visiting an educational psychologist. I remember clearly what she told my mother: the problem wasn't lack of confidence. The problem was too much of it. I thought so fast, and I accepted my first answer so completely, that I stopped questioning whether it was right. I needed to learn to be wrong — consciously, intentionally.

She was partially correct. What she was describing was a symptom of something she didn't name. My brain moved fast. It skipped details. It accepted patterns as complete when they weren't. She saw the output — she just didn't know what was producing it.

The Name

The moment everything fell into place.

I was working on a 400-page national report — graphs, statistical data, full layout. The final review was done in group sessions where the economists read the document aloud and I made corrections in real time. They would identify a word, repeat it, and I would correct it in the file.

Except I couldn't see what they were pointing at. They would say a word and I would read the same line and see nothing wrong. They would repeat it. I would read it again. Still nothing. "I read it the same way — what's the problem?"

The consultant — a style editor — noticed the pattern. Not once. Not twice. Consistently. He asked me if I was dyslexic. I didn't know what that meant. We searched Google together. He read each indicator. Each one landed.

It wasn't a diagnosis that changed anything. It was a confirmation that named everything. The calligraphy sessions. The notebooks full of graphics. The documentaries. The presentations that went beyond the book. The grammar I could never see. The details I consistently missed. The visual memory that operated above average. All of it had a name. And the name didn't make me less capable — it explained why I had spent my whole life building systems to compensate for something I didn't know I was compensating for.

The team adapted. The economists learned to be specific: line number, paragraph number, exact word, exact change. Not because I needed less — but because that level of precision let me process the correction visually instead of grammatically. The solution wasn't to change me. It was to change how the information was delivered to me.

I kept working. I thanked my mother for the effort she put into something she never fully explained. And I moved on.

The Visual Memory

Reading exhausts me. Images don't.

Reading a book puts me to sleep. Not because the content isn't interesting — because the act of reading requires extra effort that most people don't notice because they've never had to. Every sentence costs more than it should. Eventually the brain gives up.

But I can scan 2,000 or 3,000 photos — sorting by color, by composition, by form — quickly and accurately. I can hold visual information in memory in a way that doesn't translate well to words but works perfectly in images. An online test I took confirmed it: visual memory above average.

The brain that struggles with grammar and misses typographical details is the same brain that can disassemble a concept mentally, translate it into a visual system, and build something from it that nobody asked for — because it could already see what it would look like before it existed.

The Point

It wasn't a limitation. It was a different operating system.

The doodling wasn't distraction. The documentaries weren't procrastination. The infographic notebooks weren't poor study habits. The systems I built at every job weren't just efficiency — they were compensation mechanisms that worked so well I never needed to know why I was building them.

I didn't find out I was dyslexic and suddenly understand everything. I found out I was dyslexic and realized I had already figured most of it out — I just hadn't known what I was solving.

My mother put in the effort. My father named the ability. A consultant named the condition. And somewhere between the calligraphy sessions and the 400-page report, I built an entire way of working around something I didn't know I had.

If you can't see it, you don't understand it. That's not a weakness. That's just how some brains work — and once you know it, you can build everything around it.

Do you process information differently than the people around you? Drop it below.

This post contains Amazon affiliate links. If you purchase through them, I may earn a small commission at no extra cost to you. Every product listed here is something I personally own and use daily.

Read More

Philosophy · Design · Process

If I Have to Do It Twice, I Build a System.

I have to be honest about something first: repetition exhausts me.

Not in a dramatic way. But when I realize I have to do the same thing a hundred times, something in my brain activates that refuses to accept it as the only option. The repetitive task stops being a task and becomes a problem waiting to be solved.

In my years working as a graphic designer, I encountered two very different types of work.

The first was complex. Corporate identity. Advertising campaigns. Report layouts. Press kits. These projects required thinking, coordination, adapting to the constraints of the brief. They were demanding, but they were interesting.

The second type was repetitive. A set of 40 name badges for a sales department. 300 business cards with different information on each. A catalog of 1,000 products where name, category, code, and price repeat in the same position on every page. Five or six presentations of the same product for different regions. A session of 350 photos that needed consistent backgrounds and uniform crops before they could be used for anything.

The complex work required my full attention. The repetitive work required my patience — and I don't have much of that when the solution is sitting right there.

The tools were always available. The question was always the same: are you willing to invest the time to learn them?

The Discovery

I found genuine pleasure in spending 15 hours to automate something I could do manually in 3.

Batch processing in Photoshop. Data Merge in InDesign. Scripts in Illustrator. Mail Merge in Word. Automatic numbering in PDF. These tools existed long before I started using them. Most people in my field knew they existed. Very few invested the time to actually learn them.

I did. And I found something unexpected: genuine pleasure.

I would spend 10, 15, sometimes more hours figuring out how to automate something I could have done manually in 3 or 4. Not because I was being inefficient — but because I understood that once the system was built, I would never have to do it manually again. The investment paid for itself the next time the same problem appeared. And the time after that. And the time after that.

That moment when the automation runs for the first time and produces exactly what you needed — without you touching it — is a specific kind of satisfaction that's hard to describe. A confirmation that the hours were worth it.

The Cases

Seven problems. Seven systems. All built with tools that were already there.

350 staff photos. The institution hired an inexperienced photographer to take ID photos of all staff members for their institutional badges. Instead of a clean backdrop, she used standard A4 paper sheets as the background — inconsistent, wrinkled, and far from professional. Manual editing for 350 photos would have taken days. I set up a Photoshop Batch: automatic subject selection, standardized crop, background removal, export. All 350 processed in a fraction of the time. The imperfect input became a clean, uniform output.

Data Merge — one tool, every repetitive problem. InDesign's Data Merge became my answer to almost every repetitive design task. I used it for statistical infographics — 36 regional documents generated almost automatically from a structured data table. I used it for 10,000 field staff identifiers. I used it for full department business card sets.

But there's a benefit nobody talks about: Data Merge forces the information to arrive in a table. That means every department had to organize their data in a structured format before sending it to me. Errors were caught before they reached the design. The automation didn't just save time on output — it standardized the input.

The numbered receipts. The accounting department ran out of pre-printed numbered receipts and was waiting on a purchase order to restock. I built the template, set up automatic numbering, and exported the PDF. Printed on the laser printer already in the office. It was so efficient that the department cancelled the purchase order entirely. The cost of printing locally was lower than the procurement process. Automatic numbering is a native feature in InDesign, Illustrator, and PDF export. It just required someone to use it.

The institutional identity crisis. A government institution went through a brand identity change. The new isotype arrived 30 to 35 days late — no official stationery could be printed for 10 regional offices during that time. My solution: a Word template with the header and footer locked, containing the new identity. Every department already had a digital color printer. The purchase order for offset-printed stationery was cancelled. The files were already there.

The measurement ruler. One of the most frequent conversions I did was between inches and centimeters. I printed a custom conversion ruler and left it permanently on my desk. The next time someone arrived with a measurement question, I didn't calculate. I put the object on the ruler.

The paper form distribution. Distributing forms to field units across the country meant counting stacks constantly — always in multiples of 50. I converted the stack height into a measurable reference using the industrial copier's output. Units stopped asking me to count. They came, read the ruler on the stack, and took what they needed. Over four months, I processed approximately 750,000 copies. Counting each delivery by hand would have been impossible.

The homelab. The same instinct that built systems in professional environments eventually applied to the homelab. When a cable broke mid-run through a wall in a tenant's property, re-cabling the entire line wasn't an option. I relocated a router, converted it into an access point, and used its position as a signal relay. The wall stayed closed. OPNsense restarts automatically after a power cut. Pi-hole runs in Docker with a restart policy. Cloudflare Tunnel reconnects through systemd. I didn't build the homelab to manage it every day. I built it to manage itself.

The Honest Limit

I don't automate everything. I automate what I can control.

Some repetitive tasks require equipment or resources I don't have access to. An automatic die-cutting machine is incredibly expensive — so when I have to do die cuts, I do them by hand. No complaints.

But if I can automate it within the digital tools I already control, I will. Every time. Because once you've built the system, the work stops being repetitive. It becomes a process. And a process can be improved. A repetitive task just gets done again.

The Point

I don't work harder. I work once.

Every system I built started with the same frustration: having to do something again that I had already done before. Every automation was a decision not to solve the same problem twice. And every time I found a tool already sitting in the software I was using — already available, already documented, just waiting for someone to invest the hours — I felt the same thing.

Not efficiency. Satisfaction.

The tools were always there. The question was always the same: are you willing to invest the time to learn them, so you never have to do it manually again?

What's the most repetitive task you've ever systematized? Drop it below.

This post contains Amazon affiliate links. If you purchase through them, I may earn a small commission at no extra cost to you. Every product listed here is something I personally own and use daily.

Read More

Philosophy · Design · Constraints

Think Inside the Box.

Before explaining this philosophy, I want to share some context. I am a graphic designer with a Master's degree in Visual Communication and nearly 20 years of experience. Throughout my career I have worked with all kinds of clients: commercial, institutional, governmental, and non-profit organizations. Not a single one — not even once — has ever told me: "Budget is unlimited, and you have total creative freedom to do whatever you want."

Never.

There is always a budget cap, a technical restriction, a limitation on format, material, or printing. And if I was lucky, those constraints came clearly defined in a creative brief.

My professors, panel members, and guest speakers always repeated the same phrase: "You have to be creative and think outside the box." But reality is different. Every time a new client, project, or personal task comes along, you have to learn to think inside the box — because that box represents the real limitations of the project.

The box isn't a limitation. The box is the brief.

Learning the Craft Through Limits

My first professional constraint wasn't creative. It was economic.

In one of my first professional jobs, I designed for an analog offset print shop. There was a strict limit of four colors, and every extra color carried a direct cost for the client. Not every client was willing or able to pay for full process color, so I had to design within that economic barrier. Many times I had to work with just a single color — my mind had to stay creative inside that monochromatic box.

As the print shop evolved into digital printing, color stopped being a strict limit — but a new restriction took its place: format. We had to maximize every sheet of paper to optimize cuts and reduce waste. Once again, right back inside the box.

Four Cases. Four Boxes. Four Solutions.

Every job had a different box. The approach was always the same.

The cases

The color chart. At the leading paint factory in the Dominican Republic, the company decided to reduce the physical size of their color charts to lower production costs — requiring a full redesign of almost every layout. The constraint was real and financial, not a creative exercise. Same information. Different approach. It worked.

The 21,000 labels. At the same factory, 21,000 labels were marked for destruction due to a minor specification change. Instead of scrapping them, I proposed a custom correction sticker that could run through the automated labeling machine. The cans simply went through the line. We saved 21,000 labels that would have ended up in the trash. The constraint wasn't an obstacle — it was the brief.

The data merger. During seven years at a government institution, major statistical studies were published every four years. The first time, I adapted each chart manually, province by province. Extremely tedious. For the second study, I redesigned the concept and set up a datamerge — automatically generating 36 regional documents using tools I already had. Preparing a template for 36 automated documents is infinitely easier than building each one from scratch. The economists reviewed data without typographical errors. Everything shipped on time.

The press kit. At the same institution, right before an international NGO event, the vendor failed to deliver the custom USB drives. I printed a QR code linked to a Google Drive folder and added it directly to the physical kit design. All 50 press kits went out on time. Access logs later confirmed 45 had been opened. A physical drive can be lost. A link stays active until you take it down. The supplier's failure produced a better solution than the original plan.

Real-Time Adaptability

The constraint kept the business running while I fixed the problem.

After leaving the government institution, I ran my own sublimation business — mugs, t-shirts, thermoses, birthday kits. At one point, one of my machines developed a color profile problem: blues printed green, and dark tones tilted toward brown. Orders kept coming in while I worked to fix it.

My solution: I adjusted my design strategy on the fly. I shifted to two-color or three-color designs, avoiding the problem shades entirely. I also built a complete mockup system using Photoshop Smart Layers so clients could approve designs before production. The thermo wasn't available on any mockup site online — so I built the template myself. That constraint pushed me to create something my competition didn't have.

The limitation kept the business running while I resolved the technical issue.

The Kitchens

Not everyone can afford to start from scratch.

In my current work, one of my main responsibilities is measuring and designing custom kitchens. I have to adapt to the physical reality of the client's space — walls that cannot move, fixed plumbing, tight budgets, measurements that don't match any standard.

My job isn't to design a perfect kitchen. It's to design the most ergonomic and attractive kitchen possible within what already exists. And I think that's part of why new clients keep coming — because when someone arrives with what they think is an impossible space, I give them a solution using materials they already have.

The limitation is the design.

A Philosophy for Life

I find it difficult to draw inspiration from a blank canvas. But it comes naturally when there is a real constraint to solve.

My wife is incredibly creative when it comes to decoration. When an awkward space bothers her, she always finds a way to redesign it. Whenever she shares a new idea, I never say "we can't." My answer is always: "We can do this — and we can do it with what we already have."

That has led us to create beautiful pieces from leftover materials: buckets into planters, a remnant countertop piece into a nightstand, a PVC pipe into a lamp, cleaned glass bottles into vases and centerpieces. We don't do it just to save money. Transforming something destined for the trash into a decorative piece gives it double the value. And doing it together adds something to the space that no store can sell.

My wife brings the vision. I bring the question: what do we already have that can make this happen?

The Point

A constraint gives you a structure to build upon.

I have started almost every project in my life with a limitation. Not a blank canvas — a set of real conditions I couldn't ignore. And almost always, the work that came out of those conditions was better than anything I would have made with total freedom.

Because unlimited freedom gives you nothing to push against. A constraint gives you a structure to build upon. And when you tackle it with enough creativity, it stops being a wall and becomes a foundation.

I am not handed a blank canvas to create abstract art. I am handed real problems. And I build real solutions.

Many of these solutions cannot be shown publicly due to NDAs — which aligns well with my philosophy of working behind the scenes. But that is a story for another post.

What's the tightest constraint you've ever designed around? Drop it below.

This post contains Amazon affiliate links. If you purchase through them, I may earn a small commission at no extra cost to you. Every product listed here is something I personally own and use daily.

Read More

Philosophy · Design · Life

Embrace the Mistake.

From a young age, we're taught to work in a way that avoids mistakes. The entire education system is built around precision, focused on a flawless result.

But I was a kid who doodled constantly.

On pencil cases. On my backpack. On the desk chair. On anything within reach. Even teachers who noticed didn't make me feel like I was doing something wrong — and even if they had, it wouldn't have stopped me. It was the way I quieted the noise in my head. I would start with a single stroke that would become an abstract form I hadn't intended. No plan. No goal. Each mistake became a new stroke, a new direction, a new piece. And at 40, looking back, I realize I've applied this to my entire life — almost as a philosophy. Without ever deciding to.

I didn't know I was dyslexic until I was an adult — working at a government institution, listening to a consultant describe the condition in a meeting. I recognized myself mid-sentence. Suddenly, a childhood full of educational therapy sessions, support rooms, and extra effort made sense. My mother never explained it to me. I never asked. What I do remember is my father telling people that I could visualize an object in pieces in my mind — even one I had never seen disassembled. Now, in this conversation with myself at 40, I understand every mental process I built just to help myself function. Because I couldn't write well. So I learned to see instead.

The first time I noticed it was with a name.

When I was learning English as a kid, playing an MMO, I created my character and misspelled my own name. I tried to write Shadow. It came out Shiado. I kept it. That became my name in every game through adolescence and adulthood. A typo that became an identity.

The Pattern

The philosophy showed up everywhere — I just didn't recognize it as one at the time.

When I was learning Photoshop — version 3 or 4 — I made mistakes that ended up as my desktop background. I scratched my leg absentmindedly with a toothpick at the beach and ended up with a temporary tattoo from the salt drying on my skin. I burned a SODIMM connector by inserting it wrong into my motherboard and used it as a keychain for almost two years. In RPGs, when I made mistakes in my character builds, I refused to start over — I played the broken build and made it work.

The magnets from damaged hard drives became refrigerator magnets. At one of my first jobs, operating a CNC machine, I kept the centers of the O's and Q's — the small pieces that fall out when you cut those letters — and turned them into keychains for my girlfriend. A leftover strip of acrylic, about 30 cm long and 3 cm wide, became a necklace holder for her. I didn't plan it. I just looked at the piece and saw what it could be. I took the remaining rectangular scraps from the same cuts and turned them into a puzzle for my daughter. A PVC pipe left over from a project became a lamp.

Now she's my wife. Some of those things still exist.

I built a monitor stand from scrap wood and a threaded rod I'd accidentally bent at work by stepping on it. My boss was not happy. I was — the bend made it useful for something else.

I once bought a desk from a department store that came with a retractable keyboard tray underneath. It kept hitting my knees, and the ergonomics were wrong for how I worked — I was gaming a lot at the time and needed the full surface. So I removed the tray. But the tray itself was tempered glass, with decorative bolts, and it was too good to throw away. I turned it into a small side table. Twenty years later, it still exists. My mother's plant sits on top of it.

More than once, I've found myself lying on the floor, photographing the broken pieces of a glass or a cup. Not out of sadness. Out of curiosity about what they looked like from that angle.

I never did any of this consciously. It was always instinct.

But I think I owe a little of it to my parents — specifically to my father, who taught me that mistakes are inevitable, but learning from them is a choice. He never made errors feel like the end of the world. So I never learned to treat them that way.

Now I try to teach my children the same thing. Mistakes are inevitable — living is making mistakes. But understanding them is a decision. Analyzing the chain of events that led you to an error is a unique and personal form of learning. Nobody can teach it to you. You have to discover it yourself.

The Box

The real skill is thinking inside the box — when the box is a genuine constraint.

People talk about "thinking outside the box." But my experience has always been the opposite. The real skill is thinking inside the box, when the box is a genuine constraint: your tools, your budget, your situation. You don't get to ignore it. You design around it.

Four real cases

The color chart. At a paint factory, the entire catalog needed to be redesigned. The constraint was the budget — not a creative exercise, a real financial limit. I restructured the whole design around what was actually available. Same information. Different approach. It worked.

The 21,000 labels. At the same factory, there were 21,000 labels marked for destruction — a print error made them unusable as they were. I proposed saving them with a sticker overlay. It wasn't elegant. It was practical. It saved the cost of reprinting 21,000 units. The constraint wasn't an obstacle — it was the brief.

The sublimation printer. I once ran a sublimation shop — mugs, t-shirts, thermoses. The printer had a calibration problem: the blue channel printed green. Instead of stopping production, I redesigned everything around the limitation. Two colors, three at most. No blue until I corrected the color profile. I didn't advertise the constraint. Nobody knew. The work just looked intentional.

The press kit. At one of my last formal jobs, I was working an event for international NGOs — the official release of a study. At the last minute, the supplier couldn't deliver the USB drives. I printed a QR code linked to a Google Drive folder and added it to the kit design. Fifty press kits went out on time. Later, I confirmed that 45 of them had been accessed — tracked through Drive access requests. A physical drive can be lost. A link lives until you take it down. The supplier's failure produced a better solution than the original plan.

That's what "the box" actually means. Not a metaphor. A real boundary with real consequences. And the question is always the same: what can you build inside it?

Same Instinct. Different Scale.

And now, at 40, the pattern is still running.

Old computers that were heading for the trash became a homelab. An OptiPlex that nobody wanted is now a firewall serving a 1,200 m² property. A NUC that sat unused is now the DNS resolver and tunnel gateway for everything I've built. The hardware didn't change. The intention did.

Same instinct. Different scale.

The Point

Perfection is a ceiling. A mistake is a door.

Not everything has to be perfect. In fact, perfection might be the most limiting state of all — because everything considered perfect cannot be improved. Perfection is a ceiling. A mistake is a door.

It's not about making broken things work — sometimes it's about recognizing that a broken thing is actually better suited for something else entirely. The mistake wasn't wrong. It was just early.

The stroke that went where you didn't intend it — that's not a mistake. That's the beginning of something you hadn't thought of yet.

This is how I've always built. And apparently, it's also how I've always lived.

Have a mistake that became something better? Drop it below.

This post contains Amazon affiliate links. If you purchase through them, I may earn a small commission at no extra cost to you. Every product listed here is something I personally own and use daily.

Read More