I wrote this post for Net Magazine issue 320. I wanted to showcase how I have begun using React Hooks, and hilight some best practices to follow for better accessibility.
How do we not get overloaded with what’s going on in web development, but not left behind either? Should we try to keep up with latest trends that might fade away into nothing? Here’s my take on how (and why) I continue to learn about web development.
Build for complexity and performance in this deep dive into React’s Context API. This article was originally published in Net Magazine.
Many people I respect and admire have voiced conflicting opinions on their blogs and Twitter recently. I wanted to reply in general with reference to a song that pops into my head every time I hear those conflicting opinions being discussed.
When you start a Node web server using it’s HTTP interface you will by default run on a specific host that resolves to
127.0.0.1, your localhost. Here’s how to access your NodeJS server on Mac in Windows using Parallels.
I’m not proud of the code I wrote today. In fact, I hated it. But that’s okay, it did what it needed to. And I’m going to redo it tomorrow.
Structuring components in a reusable, discoverable way is a challenge across teams with diverse requirements. It can be difficult for developers unfamiliar with your library. Id like to introduce the idea of Atomic Development using React and styled-components.
Wow. 2018 was a real rollercoaster for me. This is a brief review so that I can look back on what I achieved, and set out what I hope I can achieve in web development this year.
In the recent past, I’ve heard React being criticised for not being accessible, or for allowing practices that don’t help developers think about accessibility. I have to disagree.