The work behind the build.
Developer by training, creator by nature. I work on web systems, home infrastructure, creator workflows, and practical tech projects, then document what actually helped.
Developer. Creator. Practical by default.
I've been building things since before it was easy: custom web apps, home servers, PC rigs, production software for real businesses. Got the CS degree. But the real education was the kind of work where something breaks at 11pm and you figure it out anyway.
I started making YouTube videos in 2009 for the same reason I build things: I wanted content that actually existed. Reviews that answered the questions I had. Walkthroughs that didn't skip the hard parts. Not trendy. Just useful.
Show the setup
The useful detail is usually in the wiring, config, tradeoff, or mistake.
01 / processKeep receipts
Benchmarks, photos, screenshots, and source notes beat vague advice.
02 / evidenceBuild in public
The process is part of the work, especially when the first pass breaks.
03 / archiveMake it useful
The point is not polish for its own sake. The point is helping the next run go better.
04 / outcomeA long thread, not a pivot.
The work moved from software to cameras to EVs and back into broader tech, but the habit stayed the same: build the thing, document the thing, improve the next version.
Computer Information Systems, custom web apps, and production software.
PC builds, ESXi, NAS setups, Apple and Android gear, and early tutorials.
Tesla Model 3 ownership led to SherwinM and focused EV tech notes.
SmartinUpCreations became the home base for tech, workflows, and web projects.