9 Comments

The two main problems I see in data engineering regarding SQL: using SQL for everything, and avoiding SQL even when it’s the best solution, usually because it’s not a ‘real language’.

Expand full comment

Haha! Hear hear!

Expand full comment

This article was superb. Why wasn't Python listed in the language set? Seems like with databricks, airflow and Snowflake Python would be THE language to learn besides SQL?

Expand full comment

True, an oversight. Python is the best way to move towards a broader skill set from SQl.

Expand full comment

You mean "from SQL"?

Expand full comment

That's what happens when I type on phone.

Expand full comment

I'd be stoked to build these lessons and help form a community around these ideas

Expand full comment

You need to break up with SQL... if you're looking for a job and/or want to increase your earning potential across your career. The lede was definitely buried in this post. That said, I would agree that SQL skills alone are definitely not enough to make it in Data Engineering. Huge +1 for the DevOps-related skills.

Expand full comment

SQL developers had commitment issues

Because they were always DELETEing things and never COMMITing their changes!

But it's almost 2023 and we have sql code and data versioning

Why are we still debating sql vs xyz when clearly industry accepts for simple things you need simple tools like sql and for not so simple things you have flexibility of more complex tech

If you don't learn sql with other languages and vice versa , it shows bias and does not help you become a better engineer.

It all boils down to the problem you trying to solve , sql is handy to get the job done for specific tasks, it's based on basic arithmetic and does add a lot of value in your tool chain

Expand full comment