Execute code snippets, generate graphs from code, plot ... err... your plots. -- With a client/editor extension to do the character offset calculation for you, you can put the cursor into a code block, invoke md-babel on it, and get the computation result inlined into the document. Not side-effect free: if you configure plantuml or Mermaid for this, it will generate image files for you. Repeat calls will update the result.
HN user
ctietze
Which browser?
Faithful and opinionated English translation of Niklas Luhmann's original notes on Zettelkasten.
The weirdest thing was when I ran Dwarf Fortress Adventurer Mode in text-output in Emacs and fiddled with custom key-bindings. (I still think there's potential, esp. for macros :))
The best thing is very boring, but it's the best because I use it all day, every day, and it brings me joy: bringing all my text things to Emacs. Writing, project/task organizing, and email. Never thought I'd end up there.
Fixed! Thanks
Thanks for telling me! Glad I found a tone that rang well
Wrote a short follow up in case you're interested: https://christiantietze.de/posts/2021/01/voice-assistants-an...
Cool! The clock's font size is good. Display contrast could be enough to work. 2x2 tiles instead of 3x3 would be ace.
Please share if you figure out a way :)
The clustering idea came pretty late, sorry, it's not a scientific comparison :)
I think failing to some extent is fine, if the feedback is good and the device returns to a clean state. Even on a phone with buttons, she sometimes fat-fingers the wrong button super close to the phone-book-down key and ends up in the main menu, scrolls down 10x, then tries to hit the dial button for e.g. display settings. Phone appears broken because it just doesn't dial, and neither resets itself for invalid input so she could start over. She has no mental map of the various other states the phone might be in, and in confusion forgets that the hang-up button also returns to the home screen. Things are less than ideal.
Right.
She had a Windows Phone for years because you could zoom-in the tiles and thus increase touch targets for quick dialing. That eventually broke down, too, because of lack of haptic feedback and, well, we all can hardly imagine how hard it is to navigate a device like that when everything's so blurry you cannot see the space between huge-ass tiles on a, what, 6" screen or so.
Totally! I often wonder how much accidental functional ADHD we are training ourselves to suffer from when I see how elderly people including my granny react to modern tech devices and all the movement, flashes, animations, notifications, ...
OP here:
She also can barely hear, so giving voice commands might work, but understanding the machine-generated audio feedback doesn't work. Also, she can't fix problems, like accidental activation. It's too overwhelming. And that's while she's technologically curious and adopted mobile phones and smartphones to some extent. She just can't use these things properly.
I bet we will have an easier time with these things because we learned how to use them while everything was fine.
100% agree. Most large mobile phones are useless. Can't feel the keys, or have touch.
Yes, this! +1
Shoutout to you, Rui, for Tao of Mac :)
This is a false dichotomy: you can create a Zettelkasten in a single TXT file. The implementation (e.g. using multiple files, one per note) is just a convenient way to see your stuff in a file listing and note taking apps, for example. But as long as you can link between notes, you're good, and a single-file Zettelkasten works just fine.
I like that project status approach to filing!
I do struggle with the information/knowledge distinction as I never researched that field in detail. Would love to hear about some helpful alternative!
I can imagine a primary source that’s important in your life becomes part of your knowledge, too, because you ... well, got to know it so well. But that really isn’t the point, since mere collecting is the opposite of familiarizing yourself with the material.
I don’t keep them in my head at all :) In fact, my memory is quite bad except for procedual stuff like programming techniques. That’s why I process and store notes so extensively.
I think patronage is hard to justify from a business standpoint. But it's consequential if aou value creating software to give it away for free and seek other means to make a living.
Do you have experience with this? Or moral arguments?
I find it funny that a lot of reasons boil down to "it's easier for the machine" -- developer happiness (which most of you mentioned, too!) through autocompletion and less failures seem to be a better selling point :)
I love the approach. Been using it for my latest projects and the results are amazing: having a clearly defined app state at all times makes lots of view updates so much easier.
I think you wouldn't; instead, you change the state twice: once the "model" state, once the navigation state.
The first will incorporate the changes of the current view controller and make it accessible to whoever is interested -- and then the next view controller will show the current "model" state which in fact includes everything that was changed already.
I wrote and released a book called "Exploring Mac App Development Strategies" which helps developers design reusable code and untangle Core Data from their app, for example.
I have another writing projects in the queue, so first, I'd like to get your honest feedback on the topic. There's not a lot of literature on maintaining Cocoa code. I'd like to change that.
What do you think of the book?
Seems to be down all of a sudden. DoS?
The book 'The Willpower Instinct' is citing research which supports this claim. There are ways to increase your overall willpower, if you like to think of it as a resource.
Nicely illustrated and concise!