I build software the way I'd want to inherit it: readable, tested, and documented well enough that the next person can move quickly without breaking things. My focus is on craft — thinking through the design before writing code, naming things clearly, and leaving a codebase a little better than I found it.
I work best with clients who care about how their software is built, not just that it ships. In practice, that means I'll ask questions before I start, push back when something doesn't add up, and tell you honestly when a "quick fix" is going to cost more later.
What to expect working with me:
- Realistic timelines and clear communication — no overpromising to win the job
- Code that's reviewed, tested, and explained, not just delivered
- Honest scoping — I'd rather decline a project than take one I can't do well
- Quick responses and focused attention; I keep my client list small on purpose
I'm earlier in my freelance career, and that works in your favor on both sides: I'm building a reputation through the quality of every project, and I'm working with current tools and practices rather than habits from a decade ago.