A developer is, first and foremost, a problem solver: the code written is just the implementation of a hypothesis to solve a problem.| The Valuable Dev
The cognitive load theory can help us learn more effectively our codebases, and make them easier to understand.| The Valuable Dev
Let's explore the concepts of cohesion and coupling in depth: why they are so important, and how to concretely apply them.| The Valuable Dev
The Open-Closed Principle is not a good idea. Abstractions and indirections shouldn't be created because we need to modify a bunch of code.| The Valuable Dev
We speak about it, we complain about it, we want to get rid of it. But do we really understand what's a legacy system?| The Valuable Dev
Why inheritance is considered as a pillar of OOP when so many developers criticize it? We'll see where inheritance comes from and what problems it solves.| The Valuable Dev
When developers speak about the Single Responsibility Principle, nobody seems to agree. What means the SRP? Should we still use it?| The Valuable Dev
As developers, we are alternatively teachers and learners. How to share efficiently our knowledge while avoiding the expert blind spot?| The Valuable Dev
Managing software entropy is an important part of our job, as developers. What is software entropy? How do we keep it low?| The Valuable Dev
What's the consequences of stress and how to manage it as a developer? Let's review some important and actionable tips.| The Valuable Dev
Global variables are a common pitfall many developers fall into. Let's take a look why, and how we can fix this problem.| The Valuable Dev
The keys to debate effectively as a software developer and therefore bringing value to yourself and your company.| The Valuable Dev
What are the benefits and drawbacks of the DRY principle?| The Valuable Dev