I get so sick of people trying to solve problems that are already solved especially when that solution is really just self service because you want to bypass the safetys and evolved restrictions of the old solution. That's what most apps are trying to do, and I hate it.
This message is inspired by visiting #gmail on mobile. No, I don't want your app!
From the bygone era preceding #markdown and #StackOverflow, #emacs' message mode developed a marker for code areas within an email. With `message-mark-inserted-region`, by default in a message with a selection `C-c M-m`, you get something like this:
@RuthMalan MMM... do you know Meadows, or like me just her work? I ask because I am also working with a CS professor who is all about system/control theory
@Ten my wife is a librarian. I'm sending this her way :)
@thunderbird @talios ;Thanks! Any idea when I should expect that? Is the migration targeted for this year?
@worldsendless @talios We're working on a way to let people opt in from K-9 Mail to Thunderbird for Android, as our plan is to give people an easy migration path. We hope this answer helps!
Crossposting/resharing/retweeting in #Zulip https://orys.us/vp
A great web developer resource post pointing out the #webdev things that longer need #JavaScript https://www.htmhell.dev/adventcalendar/2023/2/
I am still using k9 for mail on Android. I haven't seen an Android app for Thunderbird yet. Will the cut-over from k9 be automatic, or will there be a Thunderbird Mobile app release soon?
@RuthMalan mastodon makes it so easy to curate the timeline, I don't worry so much about cluttering. I'm just sorry I didn't find out about you and #AdventOfSystemSeeing sooner! I just finished reading https://bookwyrm.social/book/386408/s/thinking-in-systems and it was life changing, for exactly the reasons #SystemSeeing!
December 1. Start of #AdventOfSystemSeeing 2023 edition.
Like last year, there will be daily prompts on the AdventOfSystemSeeing hashtag (making it easy to follow or mute).
The idea is to do daily (15-20 minute) exercises in a System Journal (notebook). These could be a “make your own advent(ure)” sort of thing, or you can follow the prompts on the hashtag each day.
Day 1 #AdventOfSystemSeeing
Without looking at one (not even a picture), draw a bicycle.
Annotate with observations and questions that your drawing raises for you.
(I have us do this exercise during of some of my workshops. It’s more interesting and useful than it sounds — probably.)
Day 2 #AdventOfSystemSeeing
On Systems
Jot down your ideas about systems. This will form a useful baseline to look back at, when we get to the end of this advent(ure).
You could use a Mind Map with branches such as "definitional concepts," "related concepts," "approaches to," "people to learn from," etc. Or a Concept Map. A set of doodles perhaps. Text. Or something else -- let us know what you tried (if you'd like to, of course).
It's the weekend. It'd be nice to have fun with it.
Day 4 #AdventOfSystemSeeing
Identify Focal Situation
Think of a situation you want to explore as we practice various systems approaches and views. It's good if it's something that matters to you, but don't stress too much about your choice, as you can always shift focus as you explore and refine your understanding. If it helps, think of a challenge you’re facing, that you want to understand better, and address/resolve/dissolve...
Briefly describe the situation.
Day 5 #AdventOfSystemSeeing
Sketch the Situation
Start to explore the situation you described on Day 4 - visually this time. I like Rich Pictures for this: identify who (people, organizations, systems) is involved in this situation, how they interact, (annotating to add) what their purpose and role is as it relates to this situation, what they care about, their concerns, and so forth.
Use words and images, but keep it informal and sketchy.
Day 6 #AdventOfSystemSeeing
Re-Center
Take a look over the visual situation description (rich picture) you drew yesterday. Pick a person or group that is significant to the situation you’re exploring, and center the next frame on them. Draw a Rich Picture of the people, systems, organizations, etc. that they're encountering, as broadly related to their concerns on the previous visual situation description (rich picture).
Day 3 finished, only a couple days late. 😅 Would have been sooner if I'd written fewer bugs
https://github.com/lambdasierra/adventofcode2023/tree/e1d26a64e2061502ce914907fdbb3b869600adea/clojure/src/advent/day03
#AdventOfCode2023 #Clojure #AdventOfCodeSpoilers #AdventOfCode
This was an excellent review of keeping things simple https://www.htmhell.dev/adventcalendar/2023/2/
Full Stack Clojure web app engineer