There are YT courses available to support the book. Or rather, the book exists to support the courses:

• 6.046J - Design and Analysis of Algorithms
• 6.851 - Advanced Data Structures

Don’t mind the ages of these series - I watched them in full, and they’re generally still relevant. I say generally because I’m not sure if I’ll ever use a Tango Tree, but who knows!

PS: If you’re not sure if you don’t know the required Math, I created a graph of all MIT courses with YT videos here. The courses on the left are dependencies for those to the right.

That reminds me to read all his public letters (available on the website you just linked) soon. Using TTS, because that’s all too much text for my poor brain to handle.

Head First Java is also nice to learn OOP as well! Don’t worry that you’re learning an older version of Java. It’s good to know the old style, because not all Java code is fancy schmancy new ;)

Out of a lot of series I’ve read, the Head First is really geared towards beginners. Highly recommended for beginner to intermediate programmers.

I am going to toot my own horn… Or rather: MIT’s horn.

https://thaumatorium.com/articles/mit-courses/mit.drawio.svg

This is a graph of most of MIT’s CompSci courses, where the lines are dependencies. If you want to learn something on the right, learn the connected things on the left.

While there are video courses, the top link in each block links to MIT pages where they tend to recommend books for each course. The algorithm courses recommend “Introductions into Algorithms, Fourth Edition”, for example.

I hope it helps (even if I don’t think this is the be-all end-all to your question).

And lack of trailing comma’s

Someone’s working on a standard! https://datatracker.ietf.org/doc/draft-rivest-sexp/

and no possibility of (a lack of) trailing comma’s. Unless you use JSON inside Yaml, you heathens!

Depends on the data structure. If you want to save a table of sorts, you’re getting a bunch of unreadable [[[]]] nonsense.

For flat structures it’s great though.

That lack of trailing comma has been the bane of my existence.

People are working on making S-Expressions a standard: https://datatracker.ietf.org/doc/draft-rivest-sexp/

Note: This is just a draft, but improvements have been happening since 2023.

I probably won’t like the parentheses, but I think I’ll take it over yaml/json/whateverelse.

YAML is fine if you use a subset (don’t use the advanced features - not like you know those anyway) and use explicit strings (always add " to strings), otherwise things may be cast when you did not intend values to be cast.

Example:

country: NO (Norway) will be cast to country: False, because it’ll cast no (regardless from casing) to false, and yes to true.

country: "NO" should not be cast.

Alas it’s not my site (and I think it’s meant to be read on a desktop screen), so I can’t fix it.

For the newbies: RFC 3339 vs ISO 8601. Bookmark this site.

YAML is complex and has security concerns most people are not aware of.

YAML is racist to Norwegians.

If you have something like country: NO (NO = Norway), YAML will turn that into country: False. Why? Implicit casting. There are a bunch of truthy strings that’ll be cast automagically.

2024-08-30, but yes. Is that a German notation? Boo! ISO8601/RFC3339 or DEAAAAATH!

https://ijmacd.github.io/rfc3339-iso8601/

Because if we are in different zones we could both commit around 09:00 local time, so then it would seem we both committed at the same instance in time, which we didn’t.

If we were both running UTC it could work, I guess; otherwise the order of commits would stop making sense.

edit: unless you meant to auto-convert the local time to a unix timestamp, that could work. I’m overthinking stuff.

We used to say that people who made vertical videos had Vertical Video Syndrome. It was a terrible time.

Wasn’t talking about that, but OK Boomer.

Programming.dev represent! o7

I wish they had a section for query languages. Too many people only know about SQL, which being based on the Relational Model is rather powerful, except crappily implemented due to inconsistencies in the language. We need alternatives.