942 karma · joined May 2, 2017
Skim [0] is a nice alternative to fzf [1], mainly for the fact you can call additional commands dynamically like so [2]:
sk --ansi -i -c 'rg --color=always --line-number "{}"'
[0] https://github.com/lotabout/skim
[1] https://github.com/lotabout/skim#difference-to-fzf
[2] https://github.com/lotabout/skim#interactive-modeLots of aesthetics is to do with prediction and surprise, and if you don't have the 'perceptual training' you won't be able to make much sense of the art or architecture which defies your expectations.
IANAA but I imagine the "Technisches Rathaus" building is supposed to be a bit like what's supposed to go on inside a technical academy - scientific reductionism or abstraction. The design exposes the 'idea' of the components of the building (the steel poles, obvious floor layout, bringing up the 'foundations' to ground level) and abstracts away the typically visceral particulars (receding the windows, using only design-relevant adornment).
I think there are plenty of interesting buildings that look absolutely disgusting in context, but which I'd probably enjoy and be able to 'see' properly if they were grouped together in their own little town somewhere, because I'm not in a mode where I expect to see traditional architecture.
At the same time, if I never see those buildings, how am I to know what novel aesthetics I'm missing out on?
Start with plain Emacs. Print/write out the popular cheatsheets. Just make sure you know how to exit, access the documentation, and move around the windows/frames/buffers. Get Melpa & install some packages. Play with the config, adding keybindings, figure out hooks and so on. Copy some elisp functions from dotfiles on Github. Spam the documentation command on everything. Get frustrated with how much tinkering you need to do to get the crazy setups you've seen on blogposts. Stay motivated by consuming more content about custom setups. Discover the magic of magit and parinfer and dired. Look up some of the org-mode/PIM heroes on github, usernames: novoid, alphapapa, karlicoss
Install Doom. Tinker with it a bit. Take notes of your learning in an org file. Tinker some more. Go back to plain emacs for a bit. Then try spacemacs. Go straight back to Doom because it's faster and you now understand enough about emacs to be scared of spacemacs' layers.
Below are some links to help you along the way.
http://ergoemacs.org/emacs/blog.html
https://www.gnu.org/software/emacs/refcards/pdf/refcard.pdf
https://orgmode.org/worg/orgcard.html
https://cestlaz.github.io/stories/emacs/
He provides a set of frameworks (and demonstrates by example) for how obsessive, asd-leaning, smart, struggling people can go about growing a more functional pre-frontal cortex. He uses both familiar and relatively novel metaphors to convey the fundamentals of psychology in an interesting way, at least for a young-ish Western audience (drawing on video gaming and hindu/buddhist concepts respectively).
I have a really big problem with this 'should/ought-factory' culture online about how to behave. But if you relate to what I've said above, you should go check the channel out :)
[0] https://www.youtube.com/channel/UClHVl2N3jPEbkNJVx-ItQIQ
I really, really like the combination of Joplin, the Joplin extension and Pocket. The export tools offered by the Joplin extension combine well with the readability processing/formatting that Pocket applies. You can save a markdown-version, save URLs only, the complete HTML of a page, or just some text you've selected.
I have some boilerplate HTML that adds spoilers and a couple other bits to make my rendered notes look nicer and help me study, along with a couple of templates for embedding YouTube videos, Spotify and Github Gists. Most of this is on the Joplin forums, I encourage you to take a look if that sounds appealing to you.
There's a mobile app, and Joplin exposes a REST API the extension uses - I have a few hacky scripts to help me use Joplin as a CMS for a website (still a messy WIP, might show this & the templates to HN soon).
I'm exploring Emacs & Org-mode right now since it pairs well with Haskell, which I'm learning during this whole lockdown thing - even with all my Joplin-based stuff I can see why people accept the trade-offs and buy into it completely. Now might be a good time to try emacs+org out, for those lucky ones just riding lockdown out at home.
Yes, this was exactly my experience when I first encountered the repo for this project a couple years ago [0]. I actually still remember what it was like to read this for the first time.
From the perspective of someone who has been impaled on the hedgerow of despair, trudged through the endless shale of '5-minute-must-reads' and fought their way through the jungle of 'lazy tutorials rehashing a languages main beginner resource', I see why these kinds of things are created and upvoted/proliferated by developers who are no longer beginners. They're probably helpful to a minority I expect to show up in this thread. But to me these roadmaps are pathological (no pun intended) - inducing a cocktail of fear, apathy, and perfectionistic mania.
If you happen to be a beginner reading through this thread and thinking of using this map - don't. Get a feeling for the territory first. Don't worry about all these empty terms. Once you have a feeling for this programming thing you can use your powers of prediction, analogy, and noting minor differences to learn new stuff. You don't have to (you don't WANT to) jam it all into your brain at once. I took that route and it makes it really hard to play and explore for yourself, it was so painful and inefficient.
Go the naturalistic route. It's not wrong unless it doesn't work, in which case it's still not wrong. It's all good. Have fun. Make yourself laugh. Do it stupid, who cares. Edit/break/play around with stuff, maybe go Codepen [1] if that sounds fun. Maybe you want structure and streamlining, go see if FreeCodeCamp is for you - you'll tick off half the boxes here without even realising it, and that half will be the half that's worth anything to you :)
How else are pseudo-intellectuals supposed to make their money these days? /s
I enjoyed the Meadows book about it and although I didn't read it with a critical eye, I didn't find it misleading or obfuscatory. It's written in plain language.
If anything, it's got quite an ecological feel to it (and boils down to something like "testing inputs to a system willy-nilly is really stupid without a broad idea of the interactions between things").
It's not good to wear training wheels all the time. Worrying about the minutia of communication makes you less able to see what is being said, and makes you look for confirmation of your predictions/worries instead.
I don't judge the government for exploring facial recognition technology - there are motivating utilitarian arguments and they have the tools right in front of them. They are doing /something/, even if I think it's deeply wrong. But I do judge those who stick their head in the sand, or sit on their laurels, and that includes myself. We also have motivating arguments and the tools to express them.
I don't want to be part of generation of citizens whose children will say they learned nothing from history - beside the Nuremberg defense.
I'll have to clean it up and put it on GitHub this weekend!
I encourage everyone to try it, but before you do, remind yourself that it isn't Arch or Debian-based, so if you use some unusual software you may well need to build from source.
- knowing what there is to learn within any topic and what order you should tackle things
- whether advice about what to learn in some topic, how, and in what order is any good or not
- when to quit or stick when a certain approach doesn't seem to work
- how to test your learning, and how to assess your efficiency
- how to sustain motivation while playing the 'teacher' (i.e. co-ordinator) role when you'd rather learn, and the 'learner' role when you'd rather teach.
- how not to make certain important things be associated with pain and boredom, when approaching them in a free, open, playful mode would make them stick much better
- how to avoid or undo damaging perfectionism about resources and approach and personal standards for outcome and ability
---
Self-learning is extremely difficult and I don't advise it to anyone, although I wouldn't discourage trying it either.
The traditional didactic models you already know are the best. The problem is getting the right people to teach the right subjects, and ensuring free and open access for all people of all ages.
Ultimately effective self-teaching tends to mean you implement the classical methods but in non-traditional formats.
I find it's usually only those with top percentile proclivity or motivation for a given subject can sit down with a textbook and notebook/repl and absorb information as effectively as the rest of us would with a good teacher and engaged classmates.
If you're like me and you're unable to go to Uni but want to self-teach programming/CS, learn the minimum required to get into a related apprenticeship-style position and throw yourself into it.
man() {
(tldr $1 ; man $1) | cat | less
}
Edit: rewrote without the `&&` conditionalEdit: on mobile it's under Hamburger > Settings > Firefox Account