Michael Littell

Application Devleloper, Digital Artíste,
OK Drummer, & Insane Mastermind


Hello World... I’m Michael - I write software.

I've been delivering successes for over 30 years, focusing mainly on databases and back-end systems — though as you can see... I dabble in UX too.

I work fluently in SQL / T-SQL, C#, .NET Core and Entity Framework, architecting complete, optimized SQL RDBMS solutions from the ground up. I shape schemas, write functions and stored procedures, and build custom ETL pipelines & integrations. I also fine-tune queries and automate repetitive tasks to keep systems lean and efficient.

Oh, and I also play drums... sorta.


I tend to notice things other people don’t.

Sometimes it’s a pattern. Sometimes it’s a silence. Sometimes it’s the moment just before something breaks. My mind runs a little sideways—off the beaten path but always aiming for the truth of a thing. I’m not here to win arguments or rack up achievements. I’m here to build what’s needed, fix what’s broken when I must, and try not to lie to myself about what matters.

I’m not in love with systems, but I do respect them. The way they emerge. The way they decay. The way a small shift in one corner can throw the whole thing out of whack—or pull it back into harmony. I suppose I’ve lived most of my life trying to sense those shifts early, whether in people, code, or circumstances. It’s not something I trained for. It’s just how I’m built.

I don’t trust pretense. I don’t chase attention. I don’t think every thought needs to be shared or every moment needs to be captured. I’m not a content creator. I’m not trying to build a personal brand. But I am trying to leave behind something useful, or at least honest. That’s why this site exists.

I have my rhythms. I have my edges. I have my own little weather system, and I’ve learned to navigate it pretty well by now. I know when I’m sharp, when I’m drifting, when I’m about to tear something down that maybe just needed a little patience instead. I’m not always easy. But I am consistent. And if I say I’ll show up, I will. Usually with more than what was asked for.

I believe most things worth doing are harder than they first appear. I think solitude is undervalued. I think the world’s getting louder and shallower, and I’m trying—quietly—to resist both. That doesn’t make me noble. Just deliberate.

There’s a reason I live the way I do. There’s a reason I’ve left certain things behind. There’s a reason I’m still building, still learning, still showing up to the blank page or the empty editor even when no one’s watching. Some of it’s habit. Some of it’s compulsion. Most of it’s love—for the creativity, for the moment of clarity, for the grand satisfaction of building something from nothing.

So, who am I? I’m someone who notices. Someone who builds. Someone who tries to get it right, even when nobody’s keepin’ score.



I build things that didn’t exist until I showed up.

That’s the simplest way to say it. I don’t maintain code for a living, though I’ve done plenty of it. What really gets me going is solving the kind of problem that doesn’t have a template—where there’s too much nuance, too much legacy weirdness, or too many blind spots for anyone else to want to touch it. That’s where I fit.

I’ve spent most of my professional life down in the data—SQL, T-SQL, stored procedures, schemas, the kind of logic that has to hold up under real-world pressure. I don’t fear complexity. But I do expect it to earn its keep. When I design a system, it’s because the problem deserves one—not because someone thought it’d be fun to build. That mindset has served me well across decades of .NET, API integrations, ETL pipelines, and good old-fashioned problem solving.

My work doesn’t live on slides. It lives in the quiet hours before the users log in, when the system either hums or hiccups. I write the kind of code that keeps things humming—secure, resilient, tuned for the long haul. I like building engines more than dashboards. I like laying the foundation more than hanging curtains. If you need something with a UI, I can get you there. But I’ll always start with, “Where’s the data coming from, and where does it need to go?”

I’ve built background processes that just quietly do their job, day after day, without raising a fuss. I’ve architected data flows that quietly reconcile a decade of chaos. I’ve written the kind of automation that makes people wonder how they ever lived without it. But the real thread through it all is simple: I’m a builder. I figure out what needs to happen, and then I make it happen. Clean. Repeatable. Human-scaled.

There’s a line between clever and dependable. I try to walk it. Sometimes I fall off. But I always get back up and tighten the bolts. That’s just how I’m wired.



What I Am

I’m a pattern-seeker, a problem-solver, a strategist, and a builder. My mind moves deliberate and quiet, tracing possibilities before deciding where to strike. I don’t chase every impulse—I listen, I weigh, and I let things take shape before I act. And when I move, I move with conviction. Not because I trust my instincts blindly, but because I trust the values that shape them. Integrity, clarity, and respect for the real stakes—those are my north stars, and they don’t waver.

Adaptability is in my bones. I can shift direction, rewrite the plan, pivot when the terrain demands it—but never without a reason. Underneath that fluid motion is a deep responsibility: to do the right thing, even if it’s the hard thing. I don’t half-ass my work. If I put my name on it, it’s been through the fire. And behind the fire is a quiet sense of belief—an internal compass that keeps pointing toward meaning, even when the world’s content with noise.

I value integrity more than image. I don’t lie, I don’t manipulate, and I don’t play nice just to get ahead. I say what I see, and I stand by it. I’ve got empathy, but I won’t coddle incompetence. I’ve got vision, but I know when to shut up and listen. And while I might not always follow the traditional path, I’ve carved out my own with clarity and conviction. And like “Frank”, I did it my way—and paid for it.


What I’m Not

I’m not a peacemaker. Harmony ranks low for me—not because I want conflict, but because I won’t pretend everything’s fine when it isn’t. I’d rather have an honest disagreement than a dishonest smile. If the house is on fire, I’m not gonna comment on how lovely the curtains are. I’ll call it like it is and start lookin’ for the hose.

I’m not the guy who smooths over chaos with charm or spin. “Woo” doesn’t even show up on my radar. I don’t sell. I solve. I won’t schmooze a client just to keep the contract. I’d rather lose a deal than lose my self-respect. That may cost me some gigs, but it keeps me clean. I’m not built for surface-level wins—I’m built for deep, sustainable value. You either want that or you don’t.

I’m not here to win popularity contests. I don’t crave being liked, and I don’t need to be followed. I won’t sugarcoat the truth just to keep the peace, and I don’t change shape to fit the room. If that makes me an outsider, I’m fine with that—I’ve always worked better from the edge of the herd anyway. I don’t show up to fit in. I show up to make it work, make it right, and then ride on to shape what comes next.



I tend to move in quieter channels.

Most of the time, I’m not broadcasting. I’m listening. Feeling for the right frequency—whether it’s in a conversation, a piece of music, or a foggy morning that doesn’t need explaining. I’m not one to fill silence just to avoid it. There’s often more truth in what’s unspoken than what gets said loudest.

Music has always been a companion. Not as noise, not as background, but as medicine. A good song can feel like someone put their hand on your shoulder without asking. I play drums and have sang in few bar bands, but these days I mostly let the music find me. Sometimes it’s something obscure and beautiful. Sometimes it’s a track I’ve had on repeat for a decade.

I’ve got dogs who don’t always listen, a neighbor who built a rehearsal space across the street, and a stubborn little gazebo that’s seen more thoughts worked through than most meeting rooms ever will. That’s my kind of place. Outside. Unpolished. The wind doing what it wants. Me doing the same, most days.

I don’t document life much. I don’t take a lot of pictures. I don’t write things down unless I need to. But I live slow enough to notice what matters, and that’s its own kind of record.



What is this thing I'm' looking at?

The part you're looking at now—the structured text, the hero section, the accordion content—that’s the easy part. The real work lives just off to the side.

The “Dream Engine”, as my GPT jokingly named it without permission, is the actual framework powering this and my other sites. It’s a custom .NET 9 application built with EF Core under the hood and a full Three.js stage on the front—a system I designed, architected, and wrote in the midnight-hours over the course of a year or so. Not in some agile sprint or hackathon flurry, but over hundreds of quiet sessions—each one adding another layer to a thing I couldn’t quite name yet, but knew I had to finish.

What makes it different isn’t just the tech stack—it’s the experience model. The entire UI is navigated through a 3D scene. No hamburger menus. No sidebars. Just layered visuals and a kind of ambient logic. Cards rotate upward on rails. Click one, and it hands off control to an HTML overlay that reveals a curated set of media and text—a full “meal” of content: visual appetizer, core message entree, and a fortune-cookie closer. Some of it’s random. Some of it’s deliberate. All of it’s driven by a backend that lets me control what’s served, when, and how.

Every image you see is mine—generated through Stable Diffusion, then mapped onto double-sided 3D planes that flip and cycle like thoughts catching light. There’s a second set of hidden “understudy” cards waiting offstage, always synced, always ready to take over when the front card gets clicked. The preloaders are smart. The transitions are layered. The system never really stops moving—it just shifts what’s visible.

To the average user, it might feel like a quirky interface. To me, it’s the closest I’ve come to putting my internal logic on screen. It’s not perfect. It wasn’t built to scale. But it was built to mean something. And that’s enough.



This one’s for later. For the weeks that go sideways. For the seasons when the signal gets fuzzy.

Sometimes it helps to have a few notes from an earlier version of yourself—especially when they were written without an audience in mind. These aren’t rules. They’re reminders. Things I’ve learned, things I forget, things I don’t want to lose track of.

Keep building what feels strange and right.

When the path disappears, draw a better map.

Don’t trade integrity for clarity. Trust takes longer, but it lasts.

Stay human. Even when the room isn’t.

Touch the code, even if you don’t have to. It keeps you sharp.

This space might grow. Might stay just like this. Depends on where the next chapter goes.