A talk about Go showing mistakes to be avoided when coming from other languages, discussion about strengths, and perceived shortcomings like dependency management.
We all want to stay ahead of the curve – after all, that’s what you go to a conference for. But have you ever considered how being ahead of the curve might be dangerous?
When you were just a developer, things seemed so simple. Sometimes it was a choice between using several libraries, or working out the right algorithm to solve a problem. Making decisions seemed really easy. When you are playing the Lead Developer role, decisions no longer seem black and white and you have several competing priorities.
Over the last decade or so we have seen a shift towards “generalising specialists”, programmers who, as well as designing and building great software, can understand a business domain, design a user interface, participate in and automate some of the testing and deployment activities, and who are sometimes even responsible for the health and wellbeing of their own systems in production.
The Internet is full of articles about how to build & lead tech teams, however reading these will only get you so far. In order to become a successful tech lead you must also know how to manage people, including: clients, project teams, other colleagues and your bosses.
Keeping up with a team of developers who release every day is a tough job, but someone’s got to do it! Gone are the long, relaxing days of manual testing for weeks on end. Here is how we are keeping the acceptance testing process at JUST EAT as lean as possible.
Microservices offer an architectural style that is flexible enough to become the de-facto approach for future enterprise software systems, but the individual journeys, and pitfalls vary dramatically from context to context.
We all know how difficult (and expensive!) it is to convince brilliant engineers to join our team. The real challenge starts on Day 1 – What can we do to keep them happy and engaged?