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, avoiding the filthy expert blind spot? The cognitive load theory can help you 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?