The animations were done using p5.js.
The source code can be found here: https://github.com/nomemory/andreinc-site/tree/main/assets/j... , but I am not satisfied with it. I was learning p5.js while writing the article.
1,333 karma · joined December 31, 2016
The source code can be found here: https://github.com/nomemory/andreinc-site/tree/main/assets/j... , but I am not satisfied with it. I was learning p5.js while writing the article.
Unfortunately I didn't know how to optimise the animations better, and once I found out, 90% of the code was already written.
It's not something I am particularly proud of, as I was learning p5.js while writing the article, so I've started doing things in a very inefficient way.
When I have some spare time, I will update the article accordingly to include the correct links.
PS: Great stuff you've shared. I remember in the past I've spoke with you about b-trees.
Have you tried kagi?
It's a good reflex when you see the sum of two squares to think at the Circle.
Years later, I've realized they helped me to get some sort of mathematical intuition of things that was enough for me to finish an Engineering degree without having to struggle too much with math. All my colleagues who participated in the contests felt the same.
To this day I believe those puzzles educate the Engineer in you, or if you want to finish with a Math degree they can be complementary.
Yesterday the traffic on that page exploded. I am sure it's related to the Veritasium movie.
https://explore.marginalia.nu/view
Or if you like a blog or a site, you could find similar ones with this link:
https://explore2.marginalia.nu/
I also started to maintain a blogroll with minimalist and interesting blogs:
2) English is not my main language, hard to explain, but we use the masculine form when we refer to "the candidate" (which is a masculine noun). Sometimes I do a bad job at translating my thoughts into English and I get to sound like that.
Most of the seniors I interviewed were acing questions like this (they probably answered them tens of times before), and there's no way to differentiate them, once you get perfect answers. As the author of blog post mentioned, some of them don't even listen the question till the end before reciting manual phrases about Single Responsibility.
Some people would disagree but for us there are a few factors that predict if the candidate would be a good fit:
* The ability to solve easy and medium leetcode-like challenges and explain his choices. Nothing fancy, no dynamic programming or graph theory. This tells us if the candidate knows how to write code, which in most cases is at least 50% of the job.
* His academical record. It's a good predictor, because people who actually did good in school and finished their homeworks have a good work ethic. Of course, we are not recruiting PHDs to do backend work, but people who did decently well in school are usually nice to work with. There are brilliant dropouts, of course, but they are not the norm.
* We test how opiniated the candidate is when it comes to technology by asking outrageous questions (relative to the Status Quo): Why dependency injection is bad. We like people with opinions, but we find difficult to work with "evangelists".
The rest is commentary (at least in our case).
There's an indication for a loss and for a win.
There's a turn based mode implemented.
You can get hints for the best sinusoids.
Now there's a turn-based mode so it stops and gives you time to think.
I've tried touch-action manipulation instead.
Is it working better now?