To remotesynth (who I believe authored the post): Hey, how do I decide what is noise and what isn't?

Could you possible think about adding a section to the post with actionable steps similar to the ones you listed for side projects? Those were golden. But the main part of your article talks about 'finding if it's relevant to your work' and such.

Do you have a process you use for objectively evaluating a new tech for work purposes vs side project purposes? Or do you use a funnel such as: >try in side project >if good, try at work

I'm wondering because I do a lot of work with edutech, and I have a very specific set of criteria I use when evaluating the 'latest and greatest' new piece of learning software that crosses my desk. It helps me to weed out the chaff from the wheat.