Building Pixels and Grids

#Building Pixels and Grids

Right now, a big part of my life is building Pixels and Grids.

I started it because I wanted to build real things for real people, not just projects that sit on GitHub. Since then, I've worked with clients across different industries and countries, building everything from websites and internal tools to mobile apps, marketplaces, AI products, and fairly complex backend systems.

Running Pixels and Grids has taught me that knowing how to code and knowing how to deliver software are two completely different skills.

When it's your own company, there isn't always someone else to figure things out. I've had to talk to clients, understand vague requirements, estimate projects, negotiate pricing, design systems, write code, deploy applications, handle production problems, manage people, chase payments, and occasionally explain why something that sounds like a "small change" isn't actually small.

I've made plenty of mistakes along the way.

I've underpriced projects. I've underestimated timelines. I've taken on work I probably shouldn't have. I've built things before understanding the problem deeply enough. I've dealt with difficult clients, projects that changed halfway through, payments that didn't arrive when expected, and months where business was much slower than I wanted.

But those experiences taught me far more than building another tutorial project ever could.

The biggest thing I've learned is that building the software is often the easy part.

Finding customers is harder.

Understanding what they actually need is harder.

Communicating clearly is harder.

Getting people to pay for something is harder.

Building something reliable enough that another person's business can depend on it is harder.

And building a company that works consistently without depending entirely on you is much harder.

Pixels and Grids is still very much a work in progress.

So am I.

Right now, I'm trying to get better at the parts I'm weakest at: sales, distribution, communication, decision-making, and building systems that make the company less dependent on me.

I don't know exactly what Pixels and Grids will look like a few years from now.

That's partly what makes building it interesting.

It's still Day 1.