“Yes, but my father said that free advice often turns out to be expensive,” said Tiffany.
— Terry Pratchett, The Wee Free Men
Welcome to my corner of the internet. I’m not here to teach you the “right” way to do things. Instead, this is a window into how I approach problems, the techniques I’ve developed and borrowed over the years, and the methods that have proven useful in both my professional work and personal projects.
What This Is (And Isn’t)
fieldtested.dev isn’t a tutorial site. You won’t find step-by-step guides or “Follow these 10 steps to become better” posts here. What you will find is transparency about my process - how I think through challenges, why I make certain decisions, and what I’ve learned from both successes and failures.
This is simply my way of doing things, and it’s just one approach among many. If something resonates with you, great - take it and adapt it to your context. If you disagree with my approach, even better. Use that disagreement as a starting point for your own experimentation and discovery.
The “Field-Tested” Philosophy
Every technique, tool, and approach I share here has been tested in real environments - whether that’s in production systems at work, personal projects that actually need to function, or the messy intersection of both. I’m interested in what works when you have constraints, tight deadlines, and all the other realities that make building things challenging.
These aren’t pristine examples that work perfectly in isolation. They’re approaches that have survived contact with real requirements, real teams, and real problems.
As Miss Tick might say about following your dreams and trusting in yourself: "…you’ll still be beaten by people who spent their time working hard and learning things and weren’t so lazy." The techniques I share here come from that harder path - the one where you actually build things, break them, fix them, and learn from the mess.
Who This Is For
Whether you’re just getting curious about the tech industry or you’re a seasoned expert looking for different perspectives, there’s something here for you. I believe everyone’s learning journey is unique, and I value readers who appreciate seeing diverse approaches rather than being told what’s universally “correct.”
If you’re someone who:
- Enjoys seeing how others think through problems
- Values context and trade-offs over one-size-fits-all solutions
- Appreciates honesty about what works (and what doesn’t)
- Likes to experiment and adapt ideas to your own situation
…then you’ll probably find something useful here.
What to Expect
I share techniques that cross-pollinate between my professional work and side projects. Sometimes the most interesting insights come from applying enterprise patterns to personal projects, or bringing the freedom of side-project thinking into professional constraints.
You’ll see how my approaches have evolved over time - some methods I’ve developed myself, others I’ve borrowed and adapted. I try to be transparent about the journey of how these techniques were refined through actual use.
Don’t expect a posting schedule or a curriculum. I write when I have something genuinely useful to share, not to fill a content calendar.
A Different Perspective
The tech world has enough content telling you “this is THE way.” I’m more interested in showing you “this is A way” and encouraging you to build your own toolkit of approaches. The goal isn’t to convert you to my methods, but to give you another data point as you develop your own process.
Context matters enormously. What works in my environment with my constraints might not work in yours - and that’s perfectly fine. My hope is that seeing my reasoning process helps you think through your own decisions more clearly.
Thanks for taking the time to understand what fieldtested.dev is about. Now go build something interesting.