There seems to be a new programming language every week, and for us busy developers we just don’t have the time to keep up with them. But have you wondered what we might have missed out on whilst we’re busy working in our language of choice?
A series of simple numbers can represent a useful and memorable corpus of hard-earned leadership experience. This talk will succinctly explain essential leadership lessons that you can either heed or simply wait to experience.
On July 19, 1989, United Airlines Flight 232 was en route to Chicago when a mechanical failure caused the plane to become all but uncontrollable. In this unsurvivable situation, the flight crew saved more than half of those onboard. How did they do it?
As your codebase and development team grow, being able to communicate how and why your code has evolved is crucial to your ability to continue to change it.
In a fast developing industry such as tech, the acquisition and retention of talent is a crucial success factor. Often, hiring through personal networks can lead to a quicker and more successful hiring process than traditional methods – and sometimes contacts can even encourage under-represented groups to apply for positions they wouldn’t consider otherwise.
Many factors contribute to developer happiness. However, as engineers, we’re often singularly obsessed with the idea that our job satisfaction comes solely from solving only the most interesting technical challenges.
Feedback is one of the most important skills when collaborating with others. Giving and receiving feedback with honesty, integrity and empathy is hard. Doing so consistently takes practice and requires learning and practising feedback and listening techniques.