Reading lessons I read this month

In the study of the machine is the same.
To enter codes, waiting for results, interpreting them, returning to the code. Also, some representations between one's development. But, very much things don't mean nothing you can learn. On the contrary! In the past two to three years, I started a daily practice to write the lessons learned in my ML work. Looking back on some lessons from this month, I received three outstanding practical lessons:
- Continue to sign in simple signs
- Use the checklist
- Keep the whole night in mind
Continue to sign in simple signs
For many years, I used weights and research (W & B) * as my study Logger. In fact, I've been over 5% of all working users. Maths in the number below tell me that, at that time, train me to the models closely with 25000 models, spend 5000 hours including, and performs more than 500 searches. I use it with paper, large projects such as weather forecasts with large datasets, and by counting countless tests.
And W & B is actually a good tool: If you are looking for beautiful Desertes and affecting her ** and group, W & B Shine. Also, until recently, while reorganizing data from neurural networks, I ran a lot of many hyperparameter skills and W & B's Visualification Accessibility. I can compare direct comparisons.
But I realized that in my many research projects, W & B was not over. I have never run again, and when the project was done, the logs were staying there, and I did nothing in the future. When I repeatedly repeated the re-mentioned data rebuilding project, I clearly remove W & B integration project.
Now, my setup is very easy. I just got into selected metrics on CSVs and text files, write exactly the disk. Hyperpareter search, I rely on Optuna. Not even a Central server – Optuna of the area, save study studies in the Pickle file. If something crashes, I roll again and continue. Pragnatatic and enough (my charges of using).
The main understanding here is: Login is not a job. Support program. To waste 99% of your time to decide on what you want to enter – gradientents? metals? Distribution? And usually? – It can easily affect you in the original study. For me, simple, local entrance includes all the requirements, with a little hard work.
Save LAB Writing Letters
In December 1939, William Shockley wrote down the idea about his lab book: replace vacuum tubes with semiconductors. About 20 years later, chocolate and two colleagues in Bell Labs were awarded Nobel awards to find out the establishment of today.
While most of us do not write Nobel's proper parties in our writing structures, we can still learn from the vaccine. Admittedly, in a machine learning, our defenses do not have chemicals or test tubes, as we all see when we think about the lab. Instead, our Labs often our computers; The same device I use to write these lines train many models over the years. And these labs are more abundant, especially when we are remotely improving the highest sets of operation. The best, due to the most management of skills, these groups run 24/7 – so it lasts time to check the test!
However, the question is, What tests? Here, your colleague introduced me to the imagination of the lab write book, and recently returned me in a very simple way. Before starting long-term tests, I write down:
What I tested, and why I test it.
Then, when I returned later – usually in the morning – I can quickly see what the right results and that I had the hope of learning. It's easy, but changing the work of work. Instead of saying “Rerun never worked,” these dedicated tests become part of a book written. Failure to interpret. Success is easy to repetition.
Run the tests throughout all
That is small lessons, but the pain I have learned this month.
Friday evening, I got a bug that could affect my test results. I installed and restored the tests to confirm. On Saturday morning, running runs – but when I checked out results, I realized that I had forgotten to put in to put in the middle of a huge chaos. What was saying … another perfect day wait.
In ML, time the whole night is valuable. For us programming, we relax. Our testing, applies. If we do not have a test that runs while we are sleeping, we spend free timing.
That does not mean that you should use the exercises as a result. But whenever there is a goal to start, starting with the right time. Cluster are used to use of resources and resources are immediately available, and – most importantly – you will have analytical consequences for the next morning.
A simple plan is to plan this willfully. As Cal Newport discusses his “Deep Work”, the good work days begin the night. If you know tomorrow's jobs today, you can set appropriate exams on time.
* That doesn't mean anything about W & B (Unlike, eg
** Footnote: Culture just in my vision is not enough to install such stolen devices using the stolen devices. You need to find more information from the stolen tools then than time spent to set up.



