I've been writing music for about 10 years, but low output, only about 1 song per year. I mostly write some variation of metal. I love writing, but so far haven't gotten much practice at mixing, so a "professional" sounding mix eludes me.
Here's what it sounds like when I have help with the mixing:
I don't dislike coding interviews either. But if I were asked about a Convex Hull, my response would have to be, "What is a convex hull?" otherwise I'd have to guess. I have a computer science degree, did I miss something? Is that common knowledge? Right now I have the power to look it up, but it's a little strange to me that I could be asked about that in an interview and my pass/fail would potentially depend on it (granted when I am the interviewer, my pass/fail rarely depends on the response to the coding questions).
So the next question is, will interviewers explain the problem if you're unfamiliar and not "fail" you if you can explain how you'd approach a solution?
For NoSQL, I currently use MongoDB and Elasticsearch in production. Elasticsearch was by choice, whereas MongoDB was something I inherited.
For new projects, if I'm picking NoSQL at all, I'm more likely to lean Elasticsearch, but it definitely takes longer to set up and has a much higher learning curve. And as always, it's going to heavily depend on the data and its access patterns. My default continues to be RDBMS unless there's a good reason not to, even though at this point, I actually have more experience managing MongoDB and Elasticsearch clusters.