ollran

Erich Fromm came to mind as well. The same ideas and themes also appear in the books of Hermann Hesse.

Sicilian Defence (1. e4 c5) and how to develop it further by using different variations. It is easy to learn, it has hundreds of years of history and it is very popular in grandmaster tournaments.

APL is quite common in the code golf scene.

You could follow the western canon if you wish to find classics.

For culture and fun: GolfScript

Catch Me If You Can by Spielberg (2002)

Good Will Hunting by Van Sant (1997)

I think the most common thing to implement is the perceptron algorithm from scratch.

I would recommend Pattern Recognition and Machine Learning by Christopher M. Bishop. It assumes no previous knowledge of pattern recognition or machine learning.

Learn You a Haskell for Great Good! is aimed at people who have experience in imperative programming languages but haven't programmed in a functional language before.

http://learnyouahaskell.com/

Hermann Hesse - Siddhartha

Esoteric programming languages are usually created to bend the boundaries of programming language design or prove something, not to be actually used to write software. It is hacker culture.

Similar quote from Steve Jobs (1998)

"That's been one of my mantras - focus and simplicity. Simple can be harder than complex: you have to work hard to get your thinking clean to make it simple. But it's worth it in the end because once you get there, you can move mountains."

The Sublime Object of Ideology (1989) by Žižek

Interactive and high-level languages are really fun to use. This reminds me of Sharp tools essay in The Mythical Man-Month (1975).

"The most important two tools for system programming today are two that were not used in OS/360 development almost a decade ago. They are still not widely used, but all evidence points to their power and applicability. They are (1) high-level language and (2) interactive programming. I am convinced that only inertia and sloth prevent the universal adoption of these tools; the technical difficulties are no longer valid excuses."

Oh yes, reader macros, now I get it. As far as I know, you cannot write your own reader macros in Clojure (unlike in Common Lisp).

What's the story behind clojure.core/read-string? I have always wondered why it executes code. There are some examples in the docs: https://clojuredocs.org/clojure.core/read-string

I started reading The Wealth of Nations by Adam Smith and I think I'll continue with Debt: The First 5,000 Years by David Graeber. Not really compexity economics, but classical economics and anthropology.

The Art of Electronics is on my technical reading list as well.

If you are into Clojure, you will probably enjoy Elements of Clojure by Zachary Tellman. It is not a tutorial, it's more like an attempt to bring tacit knowledge of idiomatic programming practices into light.

The Rum Diary by Hunter Thompson was also absorbing.

There is a list of Forth projects used in NASA missions.

https://www.forth.com/resources/space-applications/

I think the only way to do this might be founding your own company and building your own product in Forth and Lisp.

Paul Graham is great and his blog is one of the most quotable and inspiring blogs I have ever read. I even bought Hackers & Painters: Big Ideas from the Computer Age. It is a must read for anyone attempting to found a new start up company.

I think it applies to almost any programming language and certainly also to every programming paradigm.

Darknet diaries is not as technical as HN but it has good quality content related to the industry. I especially like the stories from the visitors.

https://darknetdiaries.com/

It is hard to find learning resources when trying to write NIFs for BEAM. The documentation and bindings are fine if you are using C, but when using some rarer programming language it can be quite difficult to get along.

Programming in Lisp or Forth is such fun since you can stretch the programming language itself. For me, the reflective approach keeps the fun in programming.

I haven’t seen even one relatively large open source project without politics involved.

Thanks for the tip. All my experience is based on the use of an analog oscilloscope. Analog Discovery 2 looks interesting though. I will definitely take a look on it.

Oh sure. It's for hobby projects: reverse engineering and building electronic devices. Price range is somewhere between $300 and $1000.