Recently, we explored some of the habits that can sap the effectiveness of a developer. Even the best of us can get bogged down by challenges that make us struggle for too long. We believe that developers who better understand themselves and can identify these challenges before the bandwidth drain are more likely to be happy, satisfied, and productive. Do you recognise any of these bad habits?
With years of building large scale web apps, we’ve experienced almost everything that goes right and wrong during software development projects. So we created Milestone Mayhem, a card game that reflects the challenges and successes with app development.
Day 2 of the Lead Developer Conference continued with a series of excellent talks. Be sure to check out the Day 1 recap if you missed it.
Michael Lopp, Slack
Michael is the VP of Engineering at Slack and known for Rands in Repose. He gave the talk Leadership. By the Numbers which included a fun series of tips and suggestions to improve as a development lead.
Michael explained that you need to say the difficult things, in order to make sure someone fits in. Meaning that if you avoid addressing issues, the engineer will not succeed within your organization. A recurring theme of the conference was to give feedback early and often, rather than waiting for annual or semi-annual review.
Last week I had the opportunity to attend the Lead Developer Conference, a two-day, single-track conference with over 400 development leads from the UK, Europe, the US, Australia, and New Zealand. The event included an excellent array of speakers representing development leads at companies including Slack, Atlassian, ThoughtWorks, Amazon Web Services, GitHub, Shopify, Couchbase, and many other organizations.
Why didn’t anyone think of creating this conference sooner?