If you're a stickler about meeting topics, you're hurting the remote workers on your team.
Blasphemy? Maybe.
Read on for 2 changes in your meetings to engage and include your remote workers.👇
You can't improve what you don't track.
When I'm giving demos to or pairing with other devs, they inevitably ask how I put together my workflows and tooling. It, usually, appears smooth and effective. Everything from mnemonic shortcuts in my terminal to instantly opening the AWS console to the right account.
If you want to grow as a developer, remember the abc's: Always Be Coding
There are over 2.1 MILLION javascript packages on npm. On average, 32,000 new ones are published every month.
The more you track Hacker News and [insert your favorite language / framework] Weekly newsletters, the more overwhelming the sheer amount of new tech seems. This un-ending influx of new tools, libraries, and frameworks leads to a constant need to chase shiny objects, and a time sink that is a huge hit to developer productivity.
There's just too much noise and not enough signal. One of the most important tips I've picked up to help filter the firehose is...
The “rule” states simply that I won't invest time digging into any new library, framework, or tool until it has naturally surfaced from 3 separate, trusted sources.
Applying this rule eliminates FOMO. With a good set of trusted sources, whether that is from personal twitter lists, blogs, developers you know IRL, or elsewhere, you can feel comfortable passing on the early buzz and let your sources do the first round of filtering. As you curate those sources over time, only the most useful, highest potential items will rise up from the rest of the cruft.
I've used this technique for many years, and each time I teach it to another developer they stop getting caught by the half-baked new toys, instead becoming the dev who always knows when something is worth looking into.
Remember, developer productivity is as much about not wasting time on the wrong things as it is efficiently doing the right things.
Think about what sources you trust to help apply the Rule of 3 and respond with a few in the twitter thread.
This #ship30for30 #atomicEssay was shipped with this twitter thread:
Let's get started with one of my favorite topics: developer productivity. Today's essay is all about filtering out the noise... pic.twitter.com/eUdaodBszl
— bkono ? (@bkono101010) October 16, 2022
Thanks for reading. If you enjoyed the article subscribe via RSS feed or enter your email in the box below 👇