Software Engineer Fallacies (part one)

During my career (still ongoing) I had the chance to meet a lot of software engineers, of all levels and job families, from iOS engineers to DevOps and glorified backend developers.

All of them, almost all believed in two fallacies (and often tried to use those as an excuse on various use cases):

Software is getting better, if you rewrite it

No, it is never better, at least 90% of the time. The reason is simple; if you rewrite it, you will have to test it again, and make it work. This usually, is completely underestimated under the tendency, that if they use a different technology to rewrite something that works, the result will be simpler, and faster software.

No, not happening. Usually, is a complete waste of time. Please, do this ONLY in rare circumstances.

Knowledge sharing sessions are the only thing that is missing to enhance inner sourcing/collaboration between teams

Sadly, no. Most engineers complaining all the time for the lack of knowledge sharing sessions and/or in order to understand the software. This is not the case, usually, they do not take into account the amount of work required to understand software, in order to make meaningful contributions.

If we could all learn something by seeing other people presenting it, then it would be great but this is rarely the case.

… to be continued …