My key takeaway from the book is the importance of conceptual integrity and how hard this is to achieve the bigger the team. I think this is just as true today as it ever has been before.
On the human readability concern, we use protobuf converted to text format. It looks JSON like so very readable and comes with all the other benefits of protobuf.
I was going to mention Peter Naurs paper as well. It's fundamentally changed the way I think about software. The projects I've seen that are in the most trouble are those where the current devs haven't had the opportunity to work closely with developers that understood the codebase well.
Have a look at a site called neetcode. They offer collections of leetcode problems that are representative of what you'd see in an interview. They have tutorial videos for each problem, which should help you get back up to speed with these sort of problems.
Completely agree. Beyond being of interest in its own right, "There exists" is a prerequisite for further work in finding a practical approach to find the path.
In regards to a career as a quant, the top firms may focus on "young geniuses" but there will be plenty of places where your profile would be just fine. It's a broad industry!
There's a book on financial calculus by Rennie and Baxter [0] that gave me very good intuition on the ideas behind option pricing. It starts with the binomial model and moves on to using stochastic calculus. If you get into the topic you'll want to read more in depth books, but this may be a good place to start.
Not the op, but I started using parquet instead of CSV because the types of the columns are preserved. At one point I was caching data to CSV but when you load the CSV again the types of certain columns like datetimes had to be set again.
I guess you'll need to decide whether this is a big enough issue to warrant the new dependencies.
