Hi everyone, hope you all had a great weekend. This week, I’m adding something new, aiming at making us a better developer: ‘Code to Read’ and ‘Tools’. If you have any recommendations, please reply to this email. Also, if you learn anything from our links and come up with some code or some articles you’d like to share, please let me know too. I’ll share with our readers in next issue.
Several people at React Conf asked me for advice on becoming a better programmer. For some reason, people see me as a pretty advanced programmer worth listening to. I thought it would be worthwhile to write down my “mental model” for how I have approached programming over the years.
Here’s a handy checklist of the most important security countermeasures when designing, testing, and releasing your API.
The aim of this blog post is to tell you about what we’ve done to run Kubernetes on AWS in a (hopefully) scalable, reliable, and repeatable way and explain why we did it like that.
There are two things you need to know to build your own Virtual DOM. You do not even need to dive into React’s source or into the source code of any other Virtual DOM implementations. They are so large and complex — but in reality the main part of Virtual DOM can be written in less than 50 lines of code… 50. Lines. Of. Code!!!
BEM (Block, Element, Modifier) is a component-based approach to web development. The idea behind it is to divide the user interface into independent blocks. This makes interface development fast and easy even with a complex UI, and it allows the reuse of existing code without copying and pasting. But does it work? For the author of article, it does.
In the last couple of weeks I have started to see CSS Grid layout-based frameworks and grid systems appearing. I’m actually surprised as to how long it has taken, but I am yet to see one that adds any value at all over just using CSS Grid Layout.
You don’t have to declare that a Go type (which can be used kind of like a “class” in other languages) implements an interface, like you do in C# or Java. You just declare the interface, and then any type that happens to have those methods can be used anywhere that interface is required.
I’ll start with some context and background about Constructor functions and the class keyword, then I will explain exactly what the
When writing code, we have to make many small decisions when a problem can be solved in different ways. The author thinks that the teeny tiny decisions that don’t really matter are actually some of the most important ones. If there are no reasons to choose one version over another, take the time to find a reason to pick one.
Better Dev Link