Skip to content
OPERATOR / ABOUT DOMZ

So… who the hell is Domz?

ONE PERSON, START TO FINISH

I'm Dominic. Most people call me Dom. Online, you'll probably find me as Domz — or Dombzki.

I'm a designer, builder, problem-solver, computer nerd, and professional "wait… I can probably figure that out" guy.

I build digital things. Websites. Applications. Interfaces. Brands. Interactive experiences. Computers. And occasionally something that started as a terrible idea at 2 AM and somehow turned into a real product.

I've never been particularly good at staying in one lane. And honestly? I stopped trying.

I started college studying Computer Science. I went through the actual CS path. Programming, mathematics, logic, the whole deal.

And I liked it. I liked understanding how things worked. I liked solving problems. I liked figuring out why something broke and what needed to happen to fix it.

But eventually I realized something pretty important: I’m a creative.

I didn't want to spend my entire life buried inside a codebase. I wanted to make things people could actually see, feel, interact with, and experience. So I switched to Graphic Design.

Turns out, I didn't actually want to leave technology behind either. I just wanted to bring it with me.

That pretty much explains everything I've been doing ever since.

I work somewhere between design, technology, and product. I take an idea and start asking questions.

What problem are we solving? Who is this for? How should it work? How should it feel? What should it look like? What's happening behind the scenes?

And, probably most importantly: How the hell do we actually make it real?

Sometimes that means designing an interface. Sometimes it means building a website. Sometimes it means figuring out an application's architecture. Sometimes it means staring at a computer for six hours wondering why the thing isn't working. Sometimes it means asking Claude to write a frankly unreasonable amount of code while I sit there judging its architectural decisions.

I'm not going to pretend I'm a traditional software engineer. I'm not. I don't sit around proudly typing thousands of lines of code by hand.

I understand how the systems work, I understand the logic, I know what I want the product to do, and I use modern tools and AI to help me turn those ideas into functioning software.

I don't need to personally hammer every nail to know how I want the house built. That's the way I work.

That's the idea behind DomzLab.

I'm not a giant agency with twelve departments, three account managers, and a guy named Brad who has to "circle back." It's me.

You talk to the person designing it. You talk to the person building it. You talk to the person figuring out why something broke. You talk to the person who actually gives a shit about how the final thing turns out.

That doesn't mean I know everything. Far from it. It means when I don't know something, I figure the fuck out.

That's probably the simplest way to explain me.

I've built PCs from the ground up. I've worked with low-end hardware and ridiculous high-end hardware. I'm getting into home servers and self-hosted infrastructure.

I've designed brands. I've made websites. I've built digital products. I've designed mobile applications. I've worked with APIs, databases, authentication, deployment, and all the other fun little pieces that make software actually work.

And then there's TrailR. A movie discovery platform I designed and built from the ground up because apparently watching trailers wasn't entertaining enough already.

Take an idea. Pull it apart. Figure out how it works. Figure out how it should feel. Build it. Break it. Fix it. Make it better. Repeat.

Graphic design is where I get to do what computers can’t do for me. Think. Feel. Experiment. Make something weird. Make something beautiful. Make something stupid and then somehow make it work.

I'm obsessed with typography, visual systems, interfaces, branding, motion, digital experiences, and the little details that make something feel intentional instead of slapped together.

I don't want technology to make things feel more technological. I want technology to disappear into the experience.

I'm fascinated by how things work underneath the surface. Software. Hardware. Networks. Servers. Applications. APIs. Systems. The weird little chain of events that has to happen for you to click a button and have something actually happen.

I'm not interested in technology just for the sake of technology. I'm interested in what we can do with it.

SPEC PLATE
BASED
New York
STUDYING
Graphic Design — BMCC
DISCIPLINES
Design · Software · Hardware
FLAGSHIP
TrailR — movie discovery
STATUS
Taking client work

I'm finishing my Graphic Design degree at BMCC while continuing to build, experiment, and figure out exactly where all of this takes me.

I'm building TrailR. I'm growing DomzLab. I'm taking on my first client work. I'm getting deeper into software and AI-assisted development. I'm preparing to build my own home server. And I'm still probably going to build another PC I absolutely do not need.

Because apparently that's who I am.

That's the funny part. I don't really fit neatly into one title.

I'm not a traditional graphic designer. I'm not a traditional software engineer. I'm not trying to be either.

I'm a creative technologist. A designer who understands systems. A builder who cares about aesthetics. A product person who likes getting his hands dirty. A creative who happens to love computers.

And probably most importantly: I’m someone who likes taking things from "someone should make this" to "holy shit, I actually made this."

No bullshit. No pretending I know everything. No pretending I do everything the traditional way. Just curiosity, creativity, technology, and a borderline unhealthy desire to figure shit out.

I don't need to know exactly what something is going to become before I start building it. I just need a reason to start.

And if I don't know how to build it yet? I'll learn.

I don't really care about being the guy who knows everything.

I want to be the guy who can figure anything out.

I don't need to know what it becomes. I just need a reason to start.