Made with❤️by Alex Kondov
I've neglected tests in the past. I no longer make this mistake.
Examining React's codebase from the prism of software design.
How hexagonal architecture helps to deal with shifting business requirements
My latest book about building REST APIs with Node.js is now available
I'm back to reading open-source projects' code. This time it's React-Query.
Working on a game was one of the most enriching experiences in my career.
Each time I find myself coding without known patterns to help me, I rely on fundamental programming principles.
A few valuable lessons learned on the other side of the interview table.
My long form article with my principles for building Node applications is out.
I've always considered clean code to be too subjective of a term.
Front-end development has never been harder than it is today. Here’s why.
The only project I've needed algos and data structures knowledge to deliver
Reading Redux's source code and reflecting on the decision to use overloading
My yearly reflections & the best software engineering resources I found in 2021
The steps you should take when you're exploring an unfamiliar project
When building large UI applications becomes too hard we must learn how to split them.
Thoughts on two microservice-related projects I've worked on in the past.
Let's not forget that TS is its own language with its own learning curve.
Is it time we put common design patterns under question? Do they help or narrow our design vision?
High-level design using functional programming patterns has never been an easy task.
My favourite functional programming resources and why we don't apply it at scale.
The benefits of layered architecture to decouple domain from transport logic.
I just released my first book - Tao of React! A collection of principles when building React apps.
We start by building, then when we see the software world's real complexity, we start overengineering.
I have officially started writing my first book. Lodash library structure review.
Lessons learned from 2020 and how to architect front-ends so they don't have to be rewritten eveyr two years.
I'm yet to see a good primer on software architecture - only advice and trade-offs. And that's OK.
When you're wondering if a technology is worth your attention, consider if it's solving a real problem.
The first approach to solve a problem is rarely the best one. Also, the high-speed culture of product oriented development.
There are numerous resources on algorithms and data structures. Few about building non-trivial software.