Used to hate Ruby, then I picked it up for a side project. I wouldn’t exactly write a compiler in it, but it’s great for small scripting tasks that don’t need to be fast. I’m still not entirely sure why people do so much with it, but it’s much more friendly than bash scripts for doing many of the same small tasks.
I ended up successfully replacing Facebook with a combination of group text and group LINE message to talk to friends and family,whether they live near me or no. I don’t miss it.
Maybe I’m strange by HM standards, but unless it’s sometjing I’m just learning for fun, it must be used by 2-3 major companies or projects before I’ll consider it worth seriously picking up. It must solve a problem I have that I can’t solve with technology I already know. It must be relatively approachable and have at least minimal documentation.
I only use a ridesharing app when I can’t get a bus or train. If it’s going to take more than 20 minutes for that bus or train to arrive and I need to travel more than a mile, ridesharing is generally how I get there. It fills a niche where I live that isn’t served by public transit.
I know I’m one data point, but I’ve taught classes as an adjunct before and my (tech co) employer was fine with it... it’s totally workable if you can say get Friday mornings off.
This seems to have built on top of a lot of accepted ideas that were floating around in the academic peer to peer space in the early 2000s. Glad to see some of them getting traction in the wild aside from, you know, old school music pirating networks.
Hey! I’d actually say that’s a... reflection on your friend. I thought for a couple hours about whether to reply to this comment, and I ultimately decided that writing maintainable or readable code in any language is the engineer’s primary responsibility. So if nobody could maintain this person’s code after they were done with it, maybe they were truly brilliant, but not so good on the “raise up the others who come after me” part of engineering :/