Cognitive biases can bring mistakes, bugs, and wrong implementations. Knowing what cognitive biases are, what are the most common ones in software development, and how to fight them, can help you takes more logical decisions and create effective solutions.
We love, in the software industry, to give to each others titles. Junior developer, senior software engineering, front end programmer, and so on and so forth. Is these titles meaningful? What information do they carry about the people holding them? Can we think about a whole new set of titles, translating more accurately what really want companies from their developers?
As developers, we are alternatively teachers and learners. How to share efficiently our knowledge while avoiding the filthy expert blind spot? The cognitive load theory can help us understand the problem, and logging your knowledge acquisition process can be a powerful solution.
Using a window manager such as i3 offer many advantages: light, highly configurable, flexible, and easy to use only with a keyboard. You'll wonder why you used your mouse with your desktop environment all these years!
Burnout is on every lips nowadays: from 1974 to 2008, no less than 6000 resources have been written on the subject. However, in the software industry, this common phenomenon is still a stigma of weakness. People are afraid to speak or to hear about it, which prevent to solve the problem even more. What's burnout? How can we prevent it?
One of the main tool I use daily, for any project, is the fantastic tmux. It will allow you to have a powerful, flexible, and automated terminal experience. What is tmux? How does it work? How to configure it?
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.
Vim is the most emblematic and feared command-line application out there, even if understanding its basic commands and how it works can be really beneficial for developers. This is exactly the goal of this article. You think that Vim's not for you? Let's find out!
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.
Stress is a serious issue we should all consider very closely. Being a valuable developer means taking a lot of decision throughout the day. Stress can disable you in that regard: let's see powerful ways to manage it on a daily basis.