> the point was never yourself.
> It was never the pyramid.
> It was never the optimization.
> It was the people around the fire.
117 karma · joined January 25, 2023
> It was never the pyramid.
> It was never the optimization.
> It was the people around the fire.
Also agree on everything author mentions. I can't attest to all examples but I know what a UI is.
Author mentions center of focus of attention. We should hear more often about the periphery of our attention field. Its bandwidth so to speak is a magnitude lower compared to the center but it's still there and can guide some decisions quite unintrusively to flow.
(Major) eye movements are a detriment to attention, which itself should be treated like a commodity (in case of a UI thousands use, moreso like a borrowed commodity).
Walk slowly and you'll walk safe and far.
For small tasks you should absolutely strive to remove any friction (examples: editor undo, dictionary lookup, make a note).
Complicated tasks (writing a blog post) are a different beast: - needs to be broken down in small tasks - while carving out small tasks needs finesse and fluency - small tasks need to be frictionless
But, principal difference is you need to load your working memory (small but fast (RAM)) (e.g. read documentation, browse a repo, connect to your work from yesterday, ...). Loading your 'RAM' is an investment. And your ROI shrinks if you need to collect the threads from scratch again and again. So, IMO it's not about moving fast but moving uninterrupted. Moving uninterrupted produces flow state and gives you the impression of moving fast (despite your moving only slowly but steadily). Speed becomes irrelevant if you're moving steadily forward.
The blog post shows another problem if your working 'too long' on something: you need to reconnect from scratch to your original idea/intention, which might change. So your creation may become an incoherent medley, you begin to miss the forest for the trees, or worse: you begin to doubt yourself.
I like to think about the mind as an extensible limb that can extend in the direction of a distant goal, but can only span small distances. It's literally like the mind walking. Making steps too big is like moving trying not to touch the floor. It needs unreasonably more effort and is long-term exhausting. You may even break down and think you're a failure. But standing on one leg for too long is exhausting too.
You may laugh about the author who had this post 6 years in the making, but it's extremely important to work by a mental model that doesn't exhaust you, but works FOR you.
"I never understand anything until I have written about it." – Horace Walpole
"If you’re thinking without writing, you only think you’re thinking." – Leslie Lamport
sometimes it does seem to work
your mileage may vary
So, if machines will be decent servants to the cats, will humans get x-ed out of the equation?
It occurred to me that it would be beneficial to use flashcards to trigger the memory. It sounds unconventional/unorthotodox use of flashcards but why not. Take screenshots of your codebase/functions/commits, capture progress on your workbench, take little notes of your progress/procedures/learnings/recipes and resurface them. I'm sometimes annoyed to rediscover a useful tool I made time ago.
I yet haven't done this systematically, much less using a SRS, but it is sure worth a try. Difficult to predict when this is worth the effort. But it's a good habit to keep "lab notes" anyway.
On interfaces:
It's not only the slowness of the software or machine we have to wait for, it's also the act of moving your limb that adds a delay. Navigating a button (mouse) adds more friction than having a shortcut (keyboard). It's a needless feedback loop. If you master your tool all menus should go away. People who live in the terminal know this.
As a personal anecdote, I use custom rofi menus (think raycast for Linux) extensively for all kinds of interaction with data or file system (starting scripts, opening notes, renaming/moving files). It's notable how your interaction changes if you remove friction.
Venerable tools in this vein: vim, i3, kitty (former tmux), ranger (on the brim), qutebrowser, visidata, nsxiv, sioyek, mpv...
Essence of these tools is always this: move fast, select fast and efficiently, ability to launch your tool/script/function seamlessly. Be able to do it blindly. Prefer peripheral feedback.
I wish more people saw what could be and built more bicycles for the mind.
In fact they were portable. Cheap, certainly not.
Sold my beloved Sony TCD-D100 some years ago, as it was just sitting around. Beautiful device.
Also check out the TCD-D10. Truly a gem of 80s design.
As fascia stabilizes joints it explains your joints getting better. Focus on soft, bouncing movements if you want to regain, enhance or simply conserve fascia tissue.
Also, with time, it enables you to do with heavier weights and plainly brings back joy to moving. All the best.
I was looking for an app/cli that lets me adjust breathing patterns on the fly (think of extending the hold duration for 0.5s and a while after for instance extend the outbreathe duration 1s, while having my eyes closed using my bluetooth controller). Finding something like this on any app store with its thousands of bloated apps seems quite hopeless and it's a relatively simple feature. Can I hope for your kindness to implement something like that?
(I'm using 8bitdo controller and mapping of buttons is possible via keyd, so no need for adding configurations, any key combo would do).
I'm also happy for anyone else pointing me to a solution.
Keep on doing good!
(Happy to follow your repo if I can hope for this feature. No worries, I'm a patient man.)
I'd posit that another significant decline in moving occurs in the sixties when many go in rent.
Not sure if the biological clock is cause of abrupt changes or rather our scheduled lives. So, no significant changes from the sixties on? Then what's the genetic function of those programmations?
People who reach old age (100+) are mostly also comparatively healthy.