This is a great article, one I wished I read a long time ago after a lot of inefficient learning.
One thing I'm still keeping an eye out for is how to best learn when time is limited.
As I get older, free time is at a premium, with job/kids/life/etc. meaning that some days even 20m practice is a luxury.
So I've always been curious how to make the most of that and unexpected slots of free time.
Should I just work on technical exercises/scales? Have a set of things written down to work on in case free time appears? Follow the advice in the article? Or accept that nothing worthwhile can be done in such short time and noodle around?
I think they mean that they add "reddit" to the end of the search strings they submit to Google.
Often if you're looking for discussion on a certain topic it's a reasonable starting point for a lot of things.
Curious if there are any chorded keyboards that use tilt sensors to make character input depend on button plus position, rather than button combinations alone.
Another memorisation aid I accidentally observed was with using different pens/inks for note taking.
I started taking an minor interest in different pens at some point, and have about a dozen pens I switch between
(a mix of cheap fountain pens and rollerballs mostly).
I found that I started remembering which pen or which colour ink I wrote certain things with, it seemed to add yet another memory link to whatever I was writing.
Yup, no problem here, was just making an observation about how common such blocking was (and about the fact that some people were upset at being crawled by someone other than Google, despite not blocking them).
The company did respect robots.txt, though it was initially a bit of a struggle to convince certain project managers to do so.
A company I worked for ~7 years ago ran its own focused web crawler (fetching ~10-100m pages per month, targeting certain sections of the web).
There were a surprising number of sites out there that explicitly blocked access to anyone but Google/Bing at the time.
We'd also get a dozen complaints or so a month from sites we'd crawled. Mostly upset about us using up their bandwidth, and telling us that only Google was allowed to crawl them (though having no robots.txt configured to say so).
I was thinking along similar lines the other day. One of the things I realised was that imagination played a much bigger part in my enjoyment of games than it does now (as it did with playing with toy cars, lego etc. back at that age).
I vividly remember playing one of the Shinobi games on the Sega Master system, and spent a huge amount of time wandering back and forth in the levels thinking about the townsfolk who occupied various buildings and their work days.
There was also a mountain range in one of the backgrounds on one level, and I recall spending time planning to explore it later, even pausing the game to draw a map of an imagined village there.
Of course now the vocabulary of games (and my understanding of them) has changed a lot, and it's far more obvious what the limits of a game and its interactive areas are - to me they're now throwaway pieces of entertainment, no longer worlds to inhabit and explore.
I'd be interesting in hearing more about some of these.
We're currently using GitLab's CI/CD for ~50 or so private repositories, covering ~7 different languages without any issues. That includes testing, Docker builds and documentation generation for most projects.
We only use private runners though, I don't know if any issues are related to their own runners.