engineer
Engineering
Designing systems that are real, resilient, and maintainable — the foundation everything else stands on.
About
Brandon Donaly / Pakkit
I'm Brandon Donaly — Pakkit — a software engineer, cybersecurity-minded builder, AI tinkerer, DJ, and competitive-gaming nerd who likes turning weird ideas into working systems.
Engineer by discipline, fox by temperament. Same brain ships the secure infrastructure and the late-night DJ sets — it just changes hats.
Origin
How I got here
I started where a lot of builders do: taking things apart to see how they worked, then putting them back together a little better. That curiosity turned into software, then into networks and security, then into the messy, wonderful space where all of it overlaps.
These days I design and ship systems — software, infrastructure, and automation — with a security-first mindset and an AI-assisted workflow. I care about things that are real, resilient, and actually maintainable. That's the professional work.
The same part of my brain that wants clean infrastructure also wants a better Discord bot, a tighter DJ set, or a weird automation workflow. The through-line is systems: make the idea real, make it understandable, make it fun enough to keep improving.
Pakkit is the side of me that keeps tech fun: DJing, gaming, side experiments, and a playful fox-flavored identity that reminds me to enjoy the build.
Identity
Build · Create · Play
Three modes I move between to keep the work sharp and the curiosity alive.
engineer
Build
Software engineering, cybersecurity, AI & automation, and infrastructure / networking — turning ideas into resilient systems.
Explore Build →make
Create
Music and DJing as PakkitStorm, plus the side experiments that keep the curiosity loop running.
Explore Create →compete
Play
Gaming, Overwatch & esports, community, and the playful Pakkit identity that ties it all together.
Explore Play →Build → Build hub, NexusPort, Duvall WiFi, Private Cloud / Homelab
Create → Create hub, Music, Creative Tech Experiments
Play → Play hub, Gaming, Community Bots
AI thread → AI Automation Lab, woven through all three.
One brain, many outputs
The through-line
The serious work and the playful side aren't two people — they're the same instincts pointed at different problems.
secure
Cybersecurity
A security-first instinct that treats trust boundaries and failure modes as first-class design concerns.
operate
Infrastructure
Networks, homelab, and cloud wired to be observable and boring in the best way — so the fun parts stay reliable.
accelerate
AI workflows
AI-assisted automation woven through the stack to move faster without losing the plot or the paper trail.
perform
DJ / music
PakkitStorm sets — a live system where pacing, latency, and feel matter as much as any deploy.
compete
Gaming / community
Overwatch, bots, and community tooling — the same engineering discipline aimed at making things fun.
How I work
The Pakkit build philosophy
Six rules I keep coming back to — equal parts engineering discipline and hard-won opinions.
-
01
Small slices beat heroic rewrites.
Ship the thin vertical slice, learn from it, repeat. Big-bang rewrites mostly bang.
-
02
Security is architecture, not decoration.
Threat models, boundaries, and least privilege are design inputs — not a checklist bolted on at the end.
-
03
Automation should reduce anxiety, not hide complexity.
Good automation makes a system legible and calm. If it papers over the mess, it's a liability with a green checkmark.
-
04
Documentation is part of the deliverable.
If the next person — including future me — can't operate it, it isn't finished yet.
-
05
AI is acceleration, not architecture.
I let models draft, refactor, and explore at speed, but the structure, judgment, and accountability stay human.
-
06
Keep the weird part; scope the rest.
The strange idea is usually the point. Everything around it gets disciplined so the weird can survive contact with production.
Values
What I optimize for
Make it real
Ideas only matter once they ship and actually run in the wild.
Keep it secure
Security is a design input from the start, not a bolt-on at the end.
Automate the boring parts
If it's repetitive and predictable, it should run itself.
Build for humans
Systems exist to serve people — clarity beats cleverness.
Document the path
A solution isn't done until someone else can understand and operate it.
Make it fun enough to keep going
Sustainable momentum needs a little chaos and a lot of curiosity.