Make yourself invaluable by learning the basics of data Science

Many data science pros will tell you: learning SQL was one of the best investments in their career, even though the language is a bit basic. See why so many developers become data pros in this 2-hour video tutorial featuring data from the Cassini mission.

Develop Yourself

Invest in a long-term skillset that will have a massive impact on your career.

A Lifelong Skillset

I learned SQL on a plane 28 years ago because I was handed an Access database and told to "figure it out" because my boss wanted a chemical report created. I did, and it's a skill that's served me ever since.

Develop Your Data Sense

You know when you look at something and it just doesn't feel right? Maybe it's a unit test, a software pattern or a piece of cheesecake - you can work develop the same innate sense when it comes to data.

Become Invaluable

People that are good at SQL and databases in general are core project members in almost every case. Nothing is more valuable than safeguarding that which means most to your project: it's data.

Most programmers think SQL is a snarling mess of syntactical nonsense. Let them.

I felt the same way many years ago too. There were far more elegant ways to work with data, why did I need to spend time learning this archaic beast?

I love working with data but decades ago I did everything I could do avoid working with SQL. I knew it, yes, but only well enough to write a single "select * from" statement - that was enough for me.

I went on to create some of the most popular data access tools of the time, for languages like C#, JavaScript and Elixir. Every time I did so I kept thinking "someday, someone is going to solve this data access thing".

Simply put: there are always problems when it comes to data access and people seem to be continually confused by the same issues. 

How do you ensure that things happen in a transaction? How do you avoid executing queries within a loop? What's the right way to abstract the library you're using... or should you even try? What logic goes into a model vs. a service class?

It makes my head hurt just writing this because, you see, we've been trying to figure this out for the last 15 or so years and have gotten nowhere.

It's time to stop avoiding what is, ultimately, a very simple toolset: SQL. Learn it once, use it as you need to and move on. That was my choice over a decade ago and I am so glad I made it. Yes, I still use data access tools but for some things I go right around them and use what I consider the best tool in my belt: SQL.


you will learn SQL and databases the way we all do: under the gun

You'll be given the raw data that Cassini gathered during its time orbiting Saturn and passing by Enceladus. You'll also work with the JPL Mission Plan, 65,000 records detailing Cassini's movements during its 20+ year mission.

You're going to load this data, transform it into a solid relational design using PostgreSQL, and then export it for analysis by the analytical team... but not before taking a few peaks for yourself.

When you're done, you'll be able to create tables and views, run analytical queries and tweak data as needed. You'll be on your way to your new life as a data pro.

You'll be given access to a dedicated video site where you can watch all 24 videos, downloading as you need.

I created these videos like I always have: with care and patience, offering what I hope is the best production value out there. I even bought myself a new microphone just for this course (a Shure SM7B)!

Have a look around...

Want to see what the course looks like? You sure can! Head on over to the course site and you can see the outline as well as a few preview videos.

Know someone who might like this production? Buy it as a Gift!

You can give the gift of data science to that special someone who maybe just needs a small nudge. They'll receive this video as well as a copy of A Curious Moon, which these videos are based on.