Unexpected bonus of working on learning how to solve the 2x2 cube blind: I can practise any time, anywhere, including when the kiddo borrows the only cube I have handy. #cubing
Starting to learn 2x2 blindfolded following J Perm's tutorial. Day 2: I'm slowly getting the hang of moving pieces and moving them back during a sighted solve and I can sometimes close my eyes for one or two pieces in a row. Let's see if I can get the hang of it and if I can keep my brain on-task that long... #cubing
@ramin_hal9001 For algs, I haven't found anything better than just doing the alg slowly and then speeding up as they enter muscle memory. For pattern recognition, the tutorials tell you what colours to look for (ex: look for two corners of the same colour on one of the sides, put them in the back, then do this alg).
> "For pattern recognition, the tutorials tell you what colours to look for (ex: look for two corners of the same colour on one of the sides, put them in the back, then do this alg)."
@sachac yeah, I guess my problem is that I really only know 3 algorithms for the 3-cube, which is enough to solve it, but I should probably learn more if I want to solve it faster. I know all algorithms are basically "merging" of those basic 3 algorithms, but it limits my ability to recognize patterns and determine which algorithm to apply.
I haven't been able to access git.sr.ht URLs for a while, so I finally got around to looking into it. I can access it from my phone if I turn off wifi. I still can't access it from my laptop if I disable the Pi-hole ad-blocker. I think Sourcehut's blocking a range of IPs that my Internet provider uses, which is inconvenient.
@louis Would you consider adding automatic titles to the autoblog RSS feed? :) No rush, low priority, just makes them easier to include in Planet Emacslife and RSS readers.
@sachac Thank you! And my daytime package that now made its way to melpa is in it ☺
And it’s better thanks to melpa: I had missed some linter steps, because I used M-x use-package-lint instead of M-x package-lint. They caught that and its now much cleaner. ⇒ Thank you riscy! https://github.com/melpa/melpa/pull/8937
@sachac The "accepting your own solutions" article goes into the direction of your incremental lisp hacking article.
A shared takeway from both is for me that with this culture in the Emacs community, stability of established API is key. Because every change to the API is bound to break some personal modification — unseen and unseeable to the core devs — causing far more frustration than in a community in which all people restrict themselves to some large packages.