Software developer handbook

This book aggregates a set of instructions, references and personal observations gathered from several years of working as a software developer. These include my own findings, my conclusions and countless references to other people's work which I consider that share the same opinion as me.

Last update: 2019/08/28

Contents

Understanding different devices

There are several different computing devices, which have different sizes, screens, internal components, etc. Developing software needs to be aware of the differences between them in order to be prepared to work and display correctly.

Example: Consider developing an application for a mobile phone which has a small screen and touch input in comparison to developing the same application for a smart TV, which has a huge screen and input is usually done via a button based remote control.

Fighting for concentration

Software development and programming are a type of knowledge-based work that requires a great level of concentration because of the multitude of complex tasks it involves. From analysis, to investigation, to following logic and other complex sequences; it is of upmost importance to have uninterrupted focused time.
"In knowledge sector jobs, where products are created using human intelligence rather than machines, we must be switched on at all times and prepared to multitask. These are two things that are not compatible with deep, creative, insightful thinking." [(source)](https://www.bbc.com/worklife/article/20190715-how-to-escape-the-hyperactive-hivemind-of-modern-work)
Having the ability to be confortably working without interruptions seems to be a luxury in today's multitasking promoted work environment. In current open space offices we are constantly being bombarded by collegues interrupting, phones ringing, parallel conversations that have pushed every developer to basically work with headphones.
"Being switched on at all times and expected to pick things up immediately makes us miserable" [(source)](https://www.bbc.com/worklife/article/20190715-how-to-escape-the-hyperactive-hivemind-of-modern-work)
Moreover, the constant use of chat applications, push notifications and other attention grabbing events instill in every developer the idea that they have to be synchronously answering the cascade of events being emitted.
"Because it is so easy to dash off a quick reply on email, Slack or other messaging apps, we feel guilty for not doing so, and there is an expectation that we will do it." [(source)](https://www.bbc.com/worklife/article/20190715-how-to-escape-the-hyperactive-hivemind-of-modern-work)
This impacts not only our productivity but the influence that work has in our lives.

Infinite loop of continuous library updates

Always having to update, check for deprecation and breaking changes, etc.
2019