[ryandrake]

Different strokes for different folks. I would go bananas having to keep up with the totally unnecessary technology treadmill: re-skilling again and again forever, on new hotness technology fads just because they’re new.

“I can’t wait to rewrite this legacy software in Rust!” - said not me.

[_huayra_]

There are differences in the "totally unnecessary technology" treadmill. If some employer says "I want to build this product on Azure. I heard it's hot. Oh and use Mongo DB too, and use Go" when it would be sufficient to just spin up some sqlite-backed simple thing in Python on one low-end colo box, it's still unnecessary technology, but I'd definitely enjoy learning it. Those pieces of tech would also be good resume fodder for future jobs too.

When I have to learn some NIH-based technology that poorly copies something widely used (e.g. the place I currently work at has some custom language to generate "template instantiations in C" and some half-assed hideous clones of protobufs and grpc), I can't bring myself to care or really do my job.

Thank goodness this pandemic has made it easy to spend large portions of my day on leetcode / the CRLS algo book without anyone looking over my shoulder so I can get outta here!