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.
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?
We have tendency to forget that being a software developer means dealing all day long with humans. Interacting with others, communicating, explaining ideas, adapting to your team members are very, very important skills. As a developer, you will have to defend your ideas to your colleague: let's see together how to do so, with respect.
This article begin by a story. A story where everybody wanted to do their best. A story where simple, innocent words are the main protagonists. A story which doesn't end well. This is the story of declaring everything as 'easy' or 'simple' without any clue whatsoever.
