bin/
...all personal bash scripts can be found here...
documents/
audiobooks/
backups/
books/
personal/
projects/
videos/
work/
downloads/
hosts/
...sshfs to all important folders on several servers, no sync...
images/
music/
share/
...for locally installed software, no sync...
temp/
...remove all files in this folder once a month, no sync...
I (r)sync these folders with all my computers once every day. I have used this structure for the last 15 years. Therefore, I know by heart where to find what. Perhaps I could move the downloads folder into my temp folder. I don't know why I don't.
I had exactly the same feeling when reading this blog. Sure, the techniques used to find the solutions are really interesting. But the claim more than they achieve. The problem statements are not available in Lean, and the time limit is 2 x 4.5 hours. Not 3 days.
The article claims they have another model that can work without formal languages, and that it looks very promising. But they don't mention how well that model performed. Would that model also perform at silver medal level?
Also note, that if the problems are provided in a formal language, you can always find the solution in finite amount of time (provided the solution exists). You can brute-force over all possible solutions until you find the solution that proofs the statement. This may take a very long time, but it will find the solutions eventually. You will always solve all the problems and win the IMO at gold medal level. Alphaproof seems to do something similar, but takes smarter decisions which possible solutions to try and which once to skip. What would be the reason they don't achieve gold?
Not only did these techniques save me money, but they also saved me a considerable amount of time. I've employed these same strategies at work and private to navigate away from requests and projects in which I have no interest.
I 100% do exactly the same. I gave up following what's new in Artificial Intelligence (Machine Learning?) years ago. 99% of it is distraction, and not worth my time to find that last 1% of useful information. Instead, I focus on improving my foundations: statistical inference, linear algebra, calculus, classical machine learning (e.g., regression, boosting, component analysis, ...), programming, domain knowledge, social skills, ... I only learn a new technique if I cannot solve it with my usual toolbox (which is not very often).
I'm way more productive, have to work less hard, and I'm not distracted. Sure, I don't do that fancy new thing, but at the end of the day (or earlier) I get the job done. And I'm judged on what I do, and how it brings money into the company, not how I do it.
Another benefit working mostly with a box of boring, old tools, is that it will likely still be relevant in the next 30 years. You never know how long that new popular thing will remain popular and useful. But I'm pretty sure we'll still fit datasets with linear/logistic regressions, optimize processes with linear programming, or do straightforward A/B testing for the next few decades (if not centuries or millennia).
I used this library very often when writing a new paper. When the paper was a draft I would put coffee stains on the pages. In this way, I always knew if I was looking at a draft or the final version.
I use lists, a lot of them. I have Daily, Weekly, and Yearly lists (all on paper). I don't have them to be productive, I have them so that I don't have to remember the things on the lists. I want my head to be empty of all the things I cannot do right now. For me, the best way to achieve that, is to write the things I want to do in the future. That way, they get out of my head and I can focus on my daily business.
For me, the same trick also works for other things that are on my mind. Especially the things that would usually keep me up at night. I write them down, so that they get out of my head.
My recommendation would be to first learn vanilla Javascript. Become experience in it (I'm assuming you're not a Javascript expert yet). Build a couple of websites with vanilla Javascript. Then, move to a framework. First, it's much easier to learn these frameworks when your foundations are strong. Secondly, you'll better understand how the framework works under the hood. Thirdly, you understand better why a framework is used, and what it tries to solve what vanilla Javascript cannot (easily) do.
p.s. You'll be surprised how far you can get building a website with vanilla Javascript without the use of any advanced framework.
The Black Swan: The Impact of the Highly Improbable from Nassim Taleb. I'm rereading the book for the third time. Previous two times were in 2015 and 2019.
I still have a working X60s from 2006. Really liked that laptop. Unfortunately, for modern standards, the battery life is not great, a couple of hours at most. And the resolution is just a little bit too low, 1024 × 768.
Of course I don't know. This is just pure speculation. But perhaps it's just not that hard to build a trading platform with just a couple of (very good) developers?
Not having separated large teams also has its benefits. Keep everything as simple as possible reduces complexity, which could make it more safe as well.
I (r)sync these folders with all my computers once every day. I have used this structure for the last 15 years. Therefore, I know by heart where to find what. Perhaps I could move the downloads folder into my temp folder. I don't know why I don't.