Stuff I Use
⚠️ Personal Preferences Ahead
Everything here is what I personally use and find helpful. This isn’t a “best practices” guide or telling you what to do - just my approach. What works for me might not work for you, and that’s totally fine. Use what works for you!
What’s in Here
Section titled “What’s in Here”Here’s a peek into my dev setup and how I like to work. Browse through the sidebar to explore different sections. Again, this is just what works for me - you do you!
Toolkit
Section titled “Toolkit”These are the tools I reach for every day - my tech stack (the technologies, frameworks, and libraries I use) and CLI tools (command-line utilities that make my life easier). They work for me, but you might prefer something totally different, and that’s cool.
Workflows
Section titled “Workflows”How I like to work - my workflows, processes, and methodologies. Your workflow might be completely different, and honestly, whatever gets the job done for you is the right approach.
What is the best X?
Section titled “What is the best X?”“The best X is simply the one that checks every box.”
In the context of software development, the ‘boxes’ represent the must-haves and practical constraints of the project. This includes essential factors like performance goals, integration needs with existing systems, and long-term maintenance affordability.
This principle champions fitness for purpose over technical flash. It suggests that a developer should look past the hype of the latest framework and choose the tool that quietly and reliably solves every defined problem. When a simpler, stable technology perfectly meets all of the project’s requirements, it has achieved its highest possible standard and is, by definition, the best tool for that specific job.
Feel free to explore the sidebar and take what’s useful. Leave what isn’t. No judgment either way!