Through the stack / 01-04 (Week 7)
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. Episode 4.
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 firstname.lastname@example.org .
For this fourth publication I want to focus a bit on background job processing with Ruby and remote work. Those are two topics I have worked on and with quite a lot over the years and I am always happy to read more and share on them.
Ruby has a nice panel of possibilities for background jobs. We covered Que in Episode 2 , but the most known solutions are usually Sidekiq and Delayed Job. So it's quite common to see comparisons between those different solutions. This week AppSignal's blog has a post comparing Sidekiq and DelayedJob. I don't always go with such click bait titles but the content is good to get a quick overview of the differences.
Sidekiq made the headlines (or headaches) recently with a change in the way it handles job signatures. Keygen.sh took the time to cover a safe migration path for those.
And this leads us to look a bit more into Ruby and arguments. There has been changes in this over the last few years so it can't be bad to have a read to refresh ourselves on the topic. I have listed a few posts I have found on Ruby keyword arguments over the last major versions.
Then I wanted to read and share on Remote Work. There is a lot to read on this out there. This week I have found a few posts on leaddev on this topic : how to run better meetings, how remote change our leadership style. And I encountered a great post from @olivianlacan on communication tools for remote workers.
I also stumbled upon some nice nuggets : on vim-config from @joemasilotti, on AI powered transcripts and their potential issues (following my link to AssemblyAI content in episode 3). The latter one is a good reminder that, among all those SaaS services gobbling tons of our data, there is a real risk of exposure of that data to third parties. This exposure can be known to us or not, known to the provided or not.
Have fun !
- https://thoughtbot.com/blog/ruby-2-keyword-arguments oldy on ruby keyword arguments
- https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/ keyword arguments changes in Ruby 3.x
- https://leaddev.com/managing-distributed-teams/run-better-meetings-build-community-your-remote-team A great piece on how run meetings
- https://leaddev.com/managing-distributed-teams/huge-opportunity-remote-leadership Good food for thought on how remote work is changing our leadership style
- https://olivierlacan.com/posts/high-fidelity-remote-communication/ A good post on remote communication tools (camera, microphone, ...)
- @joemasilotti shared his vim-config : https://github.com/joemasilotti/vim-config ; always interesting for other vim users to have a look over the shoulders of our neighbors
We are a small studio specialized in helping companies level up their teams and scale up their product. We work through the whole stack : software engineering, infrastructure and, also, tehttps://blog.imfiny.comam management and technical culture.
You can read more about our work on https://blog.imfiny.com and https://www.imfiny.com/ .