I have a passion for learning and teaching.
I realized at a young age that all “knowledge” was constructed by people no smarter than you or me. Taking it at face value never satisfied me. Instead, I always sought out to learn it from first principles. This in turn made me a really effective learner, writer, and teacher (all of which I believe are greatly intertwined).
That is how I was able to teach myself pretty much everything I know. Whether it’s math, physics, coding, crypto, or dance ;)
But one problem I see in the world is the dearth of great teachers. Most teachers teach from the perspective of someone who already has mastered that knowledge. There are very few people out there who can explain things with a beginner’s mindset.
That is why you will find that much of my writing (and now videos!) consist of me explaining things from the perspective of a beginner. I have mastered the art of learning and find joy in teaching what I learn in the best way possible. My goal is to empower you the knowledge and skills to be your greatest self.
Join my email list now to get started!
If you’re a programmer or techie, chances are you’ve at least heard of Docker: a helpful tool for packing, shipping, and running applications within “containers." While the Internet is full of excellent usage guides for Docker, I couldn’t find many beginner-friendly conceptual guides, particularly on what a container is made up of. So, hopefully, this post will solve that problem :)
If you’re a newcomer to JavaScript, jargon like “module bundlers vs. module loaders,” “Webpack vs. Browserify” and “AMD vs. CommonJS” can quickly become overwhelming. The JavaScript module system may be intimidating, but understanding it is vital for web developers.
If there’s one thing I’ve learned about programming over the last few months, it’s that you don’t have to be a programming wizard to build something useful.Case in point: My teammates Banun Idris, Colin Seale and I spent the last couple of weeks building our first open-source library.
We went over basic web architecture in part I, and we talked about web application structure in part II. Now it’s time to roll up our sleeves and tackle part III: a closer look at HTTP and REST.