It was tiny when it started out. Now it's huge.

Everything is!

Is there a similar list for computer vision and/or computational photography?

Why exactly did it make programming joyful?

Because it turned out Lisp is the language that comes most natural to me and I'm most productive with.

For me, it is the demonstration that amazing things are possible, even elegant, with the most rudimentary elements.

Scheme is a beautiful language because there is almost nothing to it.

> CS programs are less about teaching kids CS and more about preparing them for jobs at FAANG companies

So true..

Btw, do you have any good suggestions about books or other materials (like codebases), from where one can learn more?

Operating Systems: The Xinu Approach

https://xinu.cs.purdue.edu/#textbook

Yes.

HtDP more so. It builds a thinking and problem solving framework for your mind. That is recursive thinking based on the data structure.

Once you can think that way you can code in any programming language with its niche syntax or constructs.

Where did you learn to see it like that?

I am self taught. I was involuntarily reassigned from a design to a developer position and just had to learn to program.

If you really want to learn functional programming you can take a look at How to Design Programs. It is free online.

https://htdp.org/

> I certainly see younger programmers who don't understand simple "separation of concerns" when writing code and get themselves in to trouble with overly complex approaches

I was also like this before. I didn't receive a formal CS education. I majored in electrical engineering. Then I read the book How to Design Programs[0] and understood that I have been approaching coding problems all wrong.

[0] https://htdp.org/

Waterloo uses the HTDP book to teach freshmen introductory programming and CS. Now, I am sure, there are many students who take CS135 with no knowledge of what programming is. They are taught a functional language without state or mutation.

My question is how do they fare when they are to use imperative languages later on in the CS program where they have to use messy for loops and mutation and memory allocation? Is it better because they did CS135 first or hard?

To be frank, I don't think imperative language use is going away anytime soon. So, they need to learn the best use of both the worlds, hence, asking.