musings

I was perusing LinkedIn recently when I saw an interesting post where Cassie Kozyrkov, one of the leading data science professionals (and Chief Decision Scientist at Google), commented on. I found Cassie’s response very relatable and thought it would be great to share.

Welcome to part 2 of my Learn SQL series! Learning advanced SQL has been a fun ride so far, and to be honest, I’ve been seeing the benefits of understanding SQL so much more and more as I look into advanced data engineering and analytics.

SQL isn’t a topic widely taught in school but is incredibly helpful to learn. I wouldn’t say I’m the best at SQL either, thus, the next series of posts will track my progress on learning advanced SQL.

When working with data, you’re almost always going to hit a situation where you need to combine and transform multiple sets of data into a singular entity. Doing this sort of transformation is simpler in analytics frameworks where whole columnar transformations are made easy.

My friend sent me a math joke earlier this year. She was hoping that I would take the bait and attempt the problem, and she won! :) For those of you who remember advanced calculus techniques, this may be a familiar problem.

When I first worked with Go during school, I thought it was very similar to a traditional object-oriented language. It’s not. Go has many similarities with object-oriented langauges, however, when you take a look at the details, you’ll see that it’s a mixture of programming paradigms which will change the way how you design object-oriented Go applications.