🏛 Stoas near [[@agora/2023 05 27]]
📚 Node [[2023-05-27]]
↳ 📓 Resource [[@agora/2023 05 27]]
Bought biokat's diamond care fresh for Lady Burup
- I think this is the ideal litter (from the ones we know)
- New Agora of Flancia user!
- There is this weird redirect-to-wikipedia bug that I'm finding hard to get to the bottom of
- First step is to reproduce in the dev environment -- for some reason it's not happening there
- Hypothesis: it's content from one of the streams (e.g. social media) that triggers the issue in e.g. node Taixu
- It's weird how the Agora is somehow redirecting to Wikipedia but Chrome doesn't show any hint of a redirect in the console or the request log
- email@example.com is now a Google group that can be posted to.
- firstname.lastname@example.org is an account meant for the stewards of the Agora of Flancia :)
- Lovely Flancia meet with Aldhari!
- Tare tuttare ture
- In the Agora you might find de-indents from Flancia that are only illusory in nature :)
- Goldberg variations
- filed expense report
- social coop
- hex numbers == centered hexagonal numbers
- love oeis as the very day I met it
- recompiled Waybar
more fixes :)
- which next?
what about shipping primes, that 'out there' executable subnodes implementation that was actually working? :)
- turns out I haven't solved passing parameters to these :)
- more fixes :)
- Saturday, 05/27/2023 ** 13:19 Tried watching some "Tsoding" streams to see what steaming for programming looks like. I'm not sure if I'll start streaming again, but his investigation of Zig was very insightful.
Almost-quote of a language: "Developing a language could be just like discovering a game. A game is designed to teach you how to play it - to discover new tips and tricks without realizing that the system is teaching you how to progress. The process of using a language - from the starting process, the error messages, and so on - should be designed like a game, to inform the user to navigate the language and teach them features."
All computer programs are the same; a program is a tool that a user has to learn. Choosing the right way to help your users is vital to helping your users understand how to use your program.
Do I provide a manpage? A
--help flag? Good error messages? A website with a great search bar? An interactive tutorial? A supportive Discord community? How do I determine what the best way is to teach my users to use my software?
Today I've also been testing out the
Helix editor, software that claims to be a modern replacement from neovim. The program claims to be a complete rewrite, but effectively rewrites and compiles in expressive neovim packages and configurations to produce the best source code editing experience out of the box. The best aspecf of this is the help menu, though - as soon as I started typing and saw a keybind that I didn't expect, I was (1) shown a menu of all possible keyboard shortcuts, and (2) shown an English explanation of my action in a pop-up. I felt encouraged to play - trying more keyboard shortcuts helped me understand more about the system! - and it was incredibly easy to find tools like the file browser and to start using the modal editing features. It's still a bit confusing to open the program to an empty buffer - but their onboarding experience is doing a lot of things right.
At work, a principle design focus is killing any sort of product tour. We include one as a crutch - it allows us to explain features we're quickly adding support for to the platform because we're building a product without clear competitors or comparators - but making UX feel seamless - teaching the user to use the product as they explore - is our primary focus. Presenting information-dense views with affordances to attract the eyes to particular aspects of the interface encourages the user to look at - and interact with - parts of the screen, and in doing so, I hope they learn. ** 13:40 Test for my website's sidebar hierarchy:
home ├╴pages ├╴c ├╴c-style ├╴ helpers ├╴making-c ├╴journals ├╴2020-10-10 ├╴2020-10-05 ├╴files
- How do I better visualize deep nesting? (The above isn't very clear.).
- How deep should a website go?
- What should be visualized? Connections? Graphs? Headings? What is important enough to visualize?
- I love the table style that I have going so far, and think it will apply wonderfully to
asciiart. It's a wonderful pattern to reuse.
- The website should feel as configurable and as interconnected as possible; things changing on one page should affect others, information should be shared whenever possible.
Thoughts on the framework so far: