Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

TL;DR starting with a list of the data types before querying the data is putting the cart before the horse IMO.

It seems a bit like DuoLingo. You learn a random assortment of facts, rather than being exposed to what people are actually doing. I learned MySQL by example and this is far from it. I don't recommend learning about the schema or the data types first, unless you're just being shown a CREATE TABLE statement with just the types you need in order to go through a CRUD example (having you start with a table that already exists and do a SELECT query first is also good). Otherwise, like with DuoLingo, you'll likely get bored, unless the reward mechanism grabs you. (DuoLingo is fully gamified. This has a bunch of short steps so you can watch yourself progress through them.)



The creator posted this elsewhere in the comments:

> it seemed like it was mostly intro stuff, or straight to DBA level

This would have been perfect for someone like me a few years ago. I went into my first job knowing how to make simple queries and simple joins. I changed jobs into a legacy system where there was an overwhelming amount of data sharded across few databases and several hundred schemas.

I didn't need to learn how to do simple joins or basic keywords like union and intersect that every tutorial talked about. I also didn't need a bunch of DBA knowledge like distribution strategies, replication, and HA techniques. I needed to learn how to leverage what was in the database to pull the exact data I needed more efficiently than what I was doing - windows, cursors, and good subqueries. I was the type of person being addressed.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: