Through the stack / 01-05 (Week 8)
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 organisations. This publication is aimed at sharing thoughts and content that are relevant to such profiles.
If you have comments or content to suggest please reach out to us by email through-the-stack@imfiny.com .
You can sign up to the mailing list version of these posts by signing up to this blog !
This week ...
... was like many others : a mix of different topics from different layers of the stack. From Ruby to management, there is a bit of everything. No list of links this time, I like the "edito" format a bit more than the cold list of links. Enjoy !
A regular one thanks to one of my former co-workers is an "old" link from App Signal's blog about "how to benchmark ruby code". Most senior Ruby developers know how to do that but many less senior don't. It's always a good one to keep in mind to quickly review our work and choices of implementation.I also stumbled into a nice piece of debate on how to grow RubyOnRails applications (again).
As I am reviewing evolutions to www.morning.st and how to replace podia.com with a solution that has a proper support for markdown and code blocks ... I stumbled upon a discussion about Markdown, and a bunch of ready to use editors : https://www.slatejs.org/ , https://quilljs.com/, https://prosemirror.net/.
In a different set of mind, mostly because of my interest in #noestimates and @allenholub I stumbled upon a thread on "do we need bug tracking software ?". Definitely a good read for food for thoughts.
And then ... Slack had issues. They published a kind of post mortem through the public log of the incident. That left me perplexed as this is not the format I am used to. So I dug out a few links on the topic for the team I am working with at the moment :
- My usual go to links : https://sre.google/sre-book/postmortem-culture/ , https://sre.google/sre-book/example-postmortem/
- A good one from .. the one tool we are happy to have to keep us in the loop and also hate it for doing so (especially when it's 3AM) : https://postmortems.pagerduty.com/how_to_write/writing/
- Another good take on it : https://www.atlassian.com/incident-management/postmortem
- A short one but packed with plenty of good tips : https://www.geekpoweredstudios.com/post/postmortem-checklist
As a reminder : a good postmortem is as important as good incident management.
A week without looking into coaching and management topics is odd lately for me. As many of my potential and past clients have told me they are only looking for seniors like me and don't want to hire juniors ... I am a bit perplexed at the state of the Ruby ecosystem. I personally like to help people level up their skills and learn Ruby. I have written many introduction articles and paired with less senior engineers for that reason. The results are quite often very good and the team can quickly shift gears. Many managers see growing junior engineers as a time suck but it's more of an investment. LeadDev published an interesting post on this topic.
To end this week I want to share an interesting article on how to migrate Gitea from Docker to Kubernetes. https://gitea.io/en-us/ has been one of my favorite Git hosting solution for a while : it's simple, light and doesn't pretend to do anything beyond Git repository hosting, issues and merge requests.
That's it for this week. Big hugs to all of you out there. Take good care of your close circle of people, your teams and yourself.
Podcasts episodes to checkout
- The always good and often excellent Tech Lead Journal podcast : https://techleadjournal.dev/episodes/76/ "Learning Domain-Driven Design - Vladik Khononov"
Imfiny ?
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) as well as training and supporting teams in their journeys to grow code, infrastructure and practices (production engineering, incident management, retrospectives, ...). We are available for 3 to 18 months contracts starting mid April.
Credits
- Photo (in the email version) by Agathe Marty : https://unsplash.com/photos/BU1N6sGKTCo