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!
In my previous post, we dived into how the web works on a basic level. For this post — part two of a three-part series — let’s double click on understanding how the client, server and other parts of a basic web application are actually configured to make your web browsing experience possible.
If you’re just getting into web development, chances are you think you know how the web works — at least on a basic level. But then you try to explain how a basic website works and draw a blank. What does an IP address mean again? How does the “client-server” model work, exactly?
Ever have the Monday blues? Or even worse, the Sunday-in-anticipation-of-Monday blues?If not, I commend and envy you. For the rest of us, let’s admit that the workweek lifestyle sucks — “living for the weekend” may be a good subject for a country song, but it’s a bad way to live your life.
Documentation can be incredibly scary for newcomers. It certainly was for me — I avoided docs like the plague. I was frustrated by the difficult jargon and overwhelmed by all the new concepts. Like many newcomers, I relied on blog posts and tutorials to walk me through issues, only cracking open the documentation when truly desperate.