Who Am I?
I'm a full-stack developer with about 10 years of experience now. Started with PHP and jQuery back in the day, then moved through the usual progression - Node.js, React, some Python, and most recently been working a lot with Go and various AI/ML stuff.
Worked at a few startups, spent time at a bigger company, and did some freelancing on the side. These days I'm mostly interested in building tools that actually save time rather than just adding complexity.
What Is This Site?
This is basically my public notebook. Whenever I spend time figuring something out - whether it's a new library, a weird bug, or just something I know I'll forget - I write it up here.
The idea is twofold: writing things down helps me remember them, and maybe it'll save someone else a few hours of googling the same thing later.
Don't expect a consistent posting schedule or anything. I update this when I actually have something to say, which could be twice a week or twice a month depending on what I'm working on.
Stuff I Work With
Currently using quite a bit, but the main ones are:
Backend
- Go (mostly these days)
- Python (scripts, ML stuff)
- Node.js (still have some projects)
- PostgreSQL / MySQL
- Redis
Frontend
- React / Next.js
- Vue.js (occasionally)
- Tailwind CSS
- TypeScript (trying to use it more)
Infrastructure
- Docker
- AWS (EC2, S3, RDS mostly)
- Linux servers
- GitHub Actions
Currently Learning
- LLM integration (RAG, agents)
- More advanced Go patterns
- System design (always improving)
Side Projects
I tend to start more projects than I finish, but here are some things I've built:
- API aggregation service - Combines data from multiple sources, built with Go
- Developer tools - Various CLI scripts for automating tedious tasks
- This site - Static HTML, nothing fancy
Most of my code is on GitHub, but I don't link everything here since a lot of it is experimental or messy.
How I Work
After 10 years, I've learned that the "perfect" solution often isn't worth the extra complexity. I'd rather ship something simple that works than spend weeks architecting the ideal system.
That said, I do care about code quality. Clean code, good tests (when I have time), and documentation matter. Just not at the expense of actually building things.
I'm also big on practical learning. Tutorial projects are fine, but nothing beats building something real and dealing with actual problems that come up.
Get In Touch
If you want to reach out about anything - a post here, a project, or just to say hi - you can find me on:
- GitHub: Check the footer for the link
- Email: Use the contact page
- Twitter/X: Occasionally active
I don't do consulting or freelancing much these days, but I'm always up for interesting conversations about tech.