3 ms·
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 pos
by nekopa 13y ago
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.
- remotesynth 13y agoI didn't cover that because I think the criteria changes depending on your role and the type of company you work for. For instance, when I was at a large financial company, it needed to be something that was well established, with solid documentation and with professional support options (so, often this was something along the lines of professional open source). When I was with a consulting company, I was much more open to new frameworks as I might encounter clients using them or they might be suitable for some project. When I am compiling my weekly update, it ends up being something that appears to have at least some decent documentation and the description sounds both useful and makes sense (you won't believe how many libraries/frameworks I come across that I simply have no idea what they actually do or how they are different). Anyway, all that is to say, I don't know that there is one set of criteria that works for everyone and it is subjective anyway. Sorry if that sounds like a cop out.