Type systems are core components of programming languages. However, it's easy to get confused by the rich vocabulary we use to describe them, especially since they seem to have different sense depending of the programming language you speak about. What are the big ideas of a type system? Is there a better type system to rule them all?
Why nobody seems to agree when to apply the Single Responsibility Principle? Why is it often misunderstood? Let's see what are the first principles of the SRP.
Software entropy can easily makes our work, as developers, way more difficult that it has to be. Knowing what is software entropy and how to keep it low is essential for our projects to be maintainable and easily scalable.
We speak about abstraction all the time, as software engineers, and yet its meaning can be pretty confusing. Could you explain clearly what means abstraction, if you needed to? This article will explain in depth what abstraction stands for, if we should abstract everything and, if not, what should be abstracted.
Global variables are common pitfalls many developers fall into. Indeed, difficult to scale and maintain an application crippled with globals. Why is that? Isn't it convenient to be able to access variables and their values everywhere? The global state problem is only part of a bigger one, namely leaking states and the lack of encapsulation.