This is "Through the Stack," a weekly list of links relating to topics relevant to Lead developers (actual or aspiring) working with an internet-related product.
Many lead developers, tech lead, and staff engineers have their hands in many projects and influence many layers in their organizations. This publication aims to share thoughts and content relevant to such profiles.
If you have comments or content to suggest, please reach out to us by email firstname.lastname@example.org.
this week ...
We have kept things a bit short. The last few weeks have been busy for us with the conclusion of an infrastructure set up for a client. We will share more on this at a later date.
So this week it's about Ruby and Leadership. But even if you are not a Rubyist or a Lead in a team I'd suggest you check out the posts we have linked. It'd still be, at least, food for thought for your own cases.
On the ruby side
As with any other package management infrastructure piece, RubyGems needs to be as secure as possible. We have seen attack vectors using weaknesses of it over the years, so it's quite nice to see it push for the adoption of 2FA for the accounts of gem maintainers.
AppSignal's blog also published a good post on Flipper, the feature switch for Ruby applications. Feature switches are a very good tool to have in your toolbox. It's also a great opportunity to remind everyone of Scientist. Paired together a feature switch and this great library can help you not only refactor but also build your features in a more scalable and reliable way.
Leading and managing
Twitter and LeadDev have continued to be a source of interesting content on those two topics.
First an interesting exchange between a few people about good practices and how to spread them in an organization.
But there was also a thread from @rhein_wein about the difference in perception of productivity between managers and developers.
But there were also some great posts to read ...
One I liked is Nick Means take on "How to run a great retrospective" on LeadDev. Much has been said about retrospectives but this is a good overview of how it can go and what to get out of it.
Another one I found interesting is Dana Browlee post on Forbes "Great work-from-home leaders actually lead differently". It's based on an exchange with David Patcher, author of a book on the topic. The article itself is a good reminder that leading a remote team is best done differently than when we were all in the office. I'd add that there are actually bits of all this that should be picked and used by leaders not working remotely too.
This content is written and published by Imfiny, a consulting company based in France. We do Ruby software engineering and DevOps in the Cloud (AWS, GCP, and others). We also train and support teams in their journeys to grow code, infrastructure, and practices (production engineering, incident management, retrospectives, ...).
We have courses available on https://learn.imfiny.com/. We are available for 3 to 18 months contracts. Contact us.