Background
How I got here
It started with Logo on an Apple IIe. I was moving a turtle around the screen, making it draw shapes and patterns — I had no idea I was programming. I just thought it was a way to make the computer do something interesting.
My early career was on the sysadmin side of things. I kept writing code to automate whatever I was doing manually — if something took long enough to be annoying, I'd build a tool for it. That pattern hasn't changed.
At one point I was in a product support role, and I started reverse-engineering the product to build better internal tools for my team. The director of engineering noticed and offered me a spot on the team. That's how I became a professional software engineer — not because I planned it, but because I couldn't stop building things.
Expertise
What I specialize in
Backend & APIs
.NET and C# services, REST APIs, full-stack web. This is where most of my consulting work lands.
Android
Native Android development — from concept to the Play Store. I build and maintain production apps used daily.
Embedded & IoT
.NET nanoFramework on ESP32 and STM32 hardware. I contribute upstream and maintain a library collection that covers gaps mainline doesn't.
The company
About CCSWE
CCSWE is a one-person operation. Everything here — the apps, the libraries, the consulting work — is built and maintained by me.
The products came from personal need. Smoking Log exists because every quit-smoking app I tried was too prescriptive. App Manager exists because Android makes it surprisingly difficult to disable system packages. I built what I needed, then released it when it was good enough to share.
Consulting runs alongside the products. I take on backend, API, and full-stack .NET work; Android; and embedded development. I'd rather maintain a small number of things well than ship a large portfolio of half-finished projects.