From Default to Design

Baltimore gave me a lot of things. A tough skin. A short fuse. And a very clear picture of where I was headed if I didn't change something.

I was born March 31, 1985. Raised by a single mother who did everything she could with what she had. I was not a good student. Not an easy kid. I got expelled from grade school. Then high school. The system didn't know what to do with me and honestly, I didn't know what to do with myself either.

Job Corps was the first place that gave me a direction. I was studying Electrical Wiring; vocational, practical, real. But completing the program required employment. I needed a job. Fast.

Service was the fastest answer. It was also a way out; out of Baltimore, out of the environment I'd grown up in, out of the version of me that was slowly forming there.

I enlisted.

They taught me discipline. They did not teach me how to be a man.

I had my first son while I was still in uniform. I could not be the father he needed. That weight doesn't just sit on you; it becomes part of you.

A deployment did something else to me. Something I didn't have a name for when I came home. I know what it was now, PTSD. Back then it was just pressure I couldn't explain and couldn't escape. So, I didn't deal with it. I managed it the wrong way. Carried it in silence for fourteen years; self-medicating, staying in motion, never stopping long enough to actually look at it.

When I left the service, I had the baggage and none of the tools.

I got into trouble. Started moving in a direction I recognized was wrong and kept moving anyway. Baltimore had a way of pulling you back into the current if you let it.

So, I left.

Late 2005. I caught the Greyhound to Florida with not much more than the intention to start over. Took every job I could find; working jobs nobody brags about, putting my electrical training to use wherever I could, learning things nobody planned to teach me.

In 2008 I had my second son.

The questions I'd been half-asking got sharper. I couldn't keep floating. I started getting serious about figuring out what it actually meant to be a man, the real version, not the one I'd been performing. I sought psychiatric help. Started reading. Studying frameworks. Testing ideas against my own life. The self-medication never fully went away but for the first time I was dealing with the source, not just quieting the signal.

By 2012 I was working inside VA medical centers, serving veterans while still quietly carrying my own damage. The irony of that was not lost on me.

In 2015 I left Florida and moved to Georgia. That's when I picked up a camera. Videography became something real, a way to tell a story, at a time when I was still learning how to tell my own.

Then in 2016 I had my third son.

That was the actual beginning.

My second son had made me want to be better. My third son made me understand that better wasn't enough, that what I was building needed to be bigger than me. The concepts I'd been developing, the frameworks I'd been living, the lessons accumulated through all of it, they couldn't just sit in the back of my mind. They needed a structure. A system. Something that could reach further than I could reach alone.

I didn't have a name for it yet. But what would become my book series, "Lifescape: The Making of Meaning", was born in that room, even before I knew what to call it.

I kept doing the work. Seeking help. Reading. Writing. Growing, imperfectly and honestly, without pretending the journey was clean or the path was straight.

January 2021, I sat down and started writing the manuscript in earnest. Five years later, 48 chapters in, I'm not just writing about the system anymore. I'm building it.

That became the foundation of Project Lifescape.

Not a concept. An obligation. A system built from everything I went through, for people who are ready to stop living by default and start designing something they actually chose.

The Builder: Full-stack Web Developer & Brand Architect

I build systems that work. I design identities that mean something.

Most developers build features. I build the bridge between what a brand promises and what a system actually delivers.

The Engineer Behind the Interface

I'm a Full‑Stack Web Developer but let me clear something up upfront: I am not a web designer.

I don't make things "pretty" for the sake of it. I make them work, scale, and deliver measurable value. A beautiful interface that collapses under load isn't beautiful, it's a liability.

What I actually do:

• System architecture that doesn't crack at the seams.
• Business intelligence: turning your data into decisions, not just dashboards.
• Feature development with actual product sense, not just ticket‑punching.
• Internal tools that stop your team from drowning in spreadsheets.

But Here's Where I'm Different

I'm also a Brand Architect. I design Brand Identities and create comprehensive Brand Bibles, the kind of documentation that turns a loose vision into a system your whole team can execute from.

Most developers can't do this. Most brand strategists can't code. I live at the intersection.

A Brand Bible isn't just a PDF with your logo and some hex codes. It's the operating manual for how your brand looks, sounds, behaves, and scales across every touchpoint; web, social, print, email, video, even merchandise. I build those systems so you never have to answer, "what color should this button be?" again.

When clients come to me, they need:

A member portal that actually works (not one that breaks at 100 users)
Internal tools that replace the chaos of manual operations
Dashboards, reporting, or automation that saves hours per week
Someone to take a rough concept and turn it into a reliable, production‑grade system

The Technical Part (because credentials matter)

AI‑augmented full‑stack developer. Four years shipping production‑grade applications. Some of the Enterprise‑level deliverables that I've produced include a comprehensive personal development LMS platform with a custom CRM system and a hybrid SaaS/desktop self-publishing application.

Stack agnostic, but fluent in: Claude Code, GitHub Copilot, ChatGPT, OpenAI Codex; I use AI as a force multiplier, not a crutch. Multi‑system technical orchestration. Product ownership from concept to deployment.

Who this is for:

• Florida‑based or remote. Freelance, contract, partnership, collaboration, or just an initial conversation to see if we're aligned.

• If you need backend or full‑stack firepower, and you want someone who understands that code serves the brand, not the other way around, let's talk.

• Open to virtual coffee, real coffee if you're in Florida, or just a direct message that starts with an actual question you need answered, problem you need solved, or a challenge you need met.