commit 42e47e57a2867118ad7b619e3d410b71c8da497b
parent ad6620033d9e36451207aae9c85bf59498804811
Author: Jake Bauer <jbauer@paritybit.ca>
Date: Fri, 14 Apr 2023 22:38:14 -0400
*
Diffstat:
7 files changed, 148 insertions(+), 218 deletions(-)
diff --git a/content/garden/buying-what-you-need-when-you-need-it.md b/content/garden/buying-what-you-need-when-you-need-it.md
@@ -1,11 +0,0 @@
-Title: Buying What You Need, When You Need It
-Summary: Buying What You Need, When You Need It
-
-# [%title]
-
-A quick post discussing the tendency of people, especially when getting into a new hobby, to buy a bunch of equipment up front, then abandon the hobby or, at the very least, realize that they didn't need all this /stuff/.
-
-For example, if you want to start off a new year by changing some habits, you might want to put up a physical (i.e. not on a computer) habit tracker. Instead of buying some corkboard and thumb tacks and mounting it in a place nearby so you can remember to fill in your habit tracker, simply pin up the piece of paper with some blue tack or a magnet. This way, if you find that this method doesn't work for you, you're not left with a corkboard you're probably not going to use much anymore.
-
-[Physical Habit Tracker](https://cblgh.org/habit%20tracker/)
-
diff --git a/content/garden/clippings.md b/content/garden/clippings.md
@@ -3,135 +3,45 @@ Summary: Clippings
# [%title]
-A collection of notes and clippings from articles that don't yet fit anywhere else, but which I still find valuable.
-
-## On Writing
-
-While the only bar for publishing what you write is the one that you set for yourself, you need to find a balance between perfectionism and just publishing the damn thing already.
-
-Things to write about are everywhere, you just have to get better at recognizing the opportunity.
-
-## Building/Creating
-
-> Ever find yourself about to ship something that isn't good enough?
-…"We can always come back and fix it up later".
-You can, but you won't.
-New priorities pull harder than old ones.
-
-> A lack of quality rarely qualifies as a bug, and it's hard to justify the time, effort, and tradeoffs required to come back with a polishing cloth down the road.
-
-[Don't Defer Quality](https://world.hey.com/jason/don-t-defer-quality-aaa105e4)
-
-
-> Selling out is usually more a matter of buying in. Sell out, and you're really buying into someone else's system of values, rules and rewards.
-
-[https://web.mit.edu/jmorzins/www/C-H-speech.html](https://web.mit.edu/jmorzins/www/C-H-speech.html)
-
-
## Notetaking
-> In taking notes, it’s the journey that matters (the habitual process of taking notes, synthesizing ideas, and re-articulating them) not the destination (a highly-organized and tagged library of notes for recall).
+> In taking notes, it’s the journey that matters (the habitual process of
+taking notes, synthesizing ideas, and re-articulating them) not the destination
+(a highly-organized and tagged library of notes for recall).
[https://blog.jim-nielsen.com/2022/reading-notes-june/](https://blog.jim-nielsen.com/2022/reading-notes-june/)
-[https://www.baldurbjarnason.com/2022/on-online-collaboration/](https://www.baldurbjarnason.com/2022/on-online-collaboration/)
-
-
## Web3
-> Web3 is a fun buzzword used by a group of people who believe our use of the web will evolve into a digital land-grab where you can monetise absolutely everything with the help of environment-destroying technology.
+> Web3 is a fun buzzword used by a group of people who believe our use of the
+web will evolve into a digital land-grab where you can monetise absolutely
+everything with the help of environment-destroying technology.
[https://chaos.social/@cityroler/108697761132980120](https://chaos.social/@cityroler/108697761132980120)
-
## Society and Humans
-Humans naturally build consensus when in groups, even when they don't intend to.
+Humans naturally build consensus when in groups, even when they don't intend
+to.
-> And that’s all great and intuitive… until you get to humans. Humans, he said, demonstrate the opposite principle: more interactions equals dumber behavior. When we come together and interact as a group seeking consensus, we lose sophistication and intelligence. Ants get smarter while we get dumber.
+> And that’s all great and intuitive… until you get to humans. Humans, he said,
+demonstrate the opposite principle: more interactions equals dumber behavior.
+When we come together and interact as a group seeking consensus, we lose
+sophistication and intelligence. Ants get smarter while we get dumber.
-> At its simplest form, it means that if you take a bunch of people and ask them (as individuals) to answer a question, the average of each of those individual answers will likely be better than if the group works together to come up with a single answer.
+> At its simplest form, it means that if you take a bunch of people and ask
+them (as individuals) to answer a question, the average of each of those
+individual answers will likely be better than if the group works together to
+come up with a single answer.
-- Kathy Sierra, _The "Dumbness of Crowds"_
[https://headrush.typepad.com/creating_passionate_users/2007/01/the_dumbness_of.html](https://headrush.typepad.com/creating_passionate_users/2007/01/the_dumbness_of.html)
-
-## Words
-
-> Robot
-
-The term originates from Czech "robot"/"robota" for drudgery, servitude. Also was a system of serfdom in Central Europe under which a tenant's rent was paid for in forced labour.
-
-Perhaps automaton and derived term auton are nicer and give off less "slavery", "capitalism", "forced to serve" vibes.
-
## A Collection of Wikis
[https://library.kiwix.org/?lang=eng](https://library.kiwix.org/?lang=eng)
-
-## Focus
-
-Focus is the ability to keep awareness on the person or thing engaged with until a conscious choice is made to move the awareness onto the next thing.
-
-Awareness can be thought of as a ball of light within the mind that we can control to focus on various different parts of our minds. If the ball is in the angry part of the brain, then we will be angry, and so on. This is a useful metaphor that can give us greater control of what we choose to spend our awareness on and when, and can be a "rehoming point" to help us more easily refocus when our awareness drifts (think about shifting the ball of light, instead of trying really hard to focus on something else). The ability to focus is the ability to control where awareness goes in the mind.
-
-Being focused is something that needs to be practiced. TikTok/Instagram, etc. influence our ability to focus because we are training ourselves to switch focus every 30-60 seconds and this is one reason why so many of us feel like it's so hard to stay focused.
-
-Find opportunities to practice concentration. Give things your undivided attention and catch yourself when your mind starts to wander. The more you practice this, the easier it will become.
-
-Mindfulness is a byproduct of focused awareness.
-
-[AoM Podcast 832: The Power of Unwavering Focus](https://www.artofmanliness.com/character/behavior/podcast-832-the-power-of-unwavering-focus/)
-
-
-## Uxn
-
-Just a collection of resources related to Uxn:
-
-[https://100r.co/site/uxn.html](https://100r.co/site/uxn.html)
-
-[https://wiki.xxiivv.com/site/varvara.html](https://wiki.xxiivv.com/site/varvara.html)
-
-[https://github.com/hundredrabbits/awesome-uxn](https://github.com/hundredrabbits/awesome-uxn)
-
-[https://compudanzas.itch.io/introduction-to-uxn-programming](https://compudanzas.itch.io/introduction-to-uxn-programming)
-
-[https://wiki.xxiivv.com/site/uxntal.html](https://wiki.xxiivv.com/site/uxntal.html)
-
-[https://wiki.xxiivv.com/site/uxntal_cheatsheet.html](https://wiki.xxiivv.com/site/uxntal_cheatsheet.html)
-
-[https://wiki.xxiivv.com/site/uxntal_reference.html](https://wiki.xxiivv.com/site/uxntal_reference.html)
-
-[ircs://irc.esper.net:6697/#uxn](ircs://irc.esper.net:6697/#uxn)
-
-
-## Passwords
-
-What if we only had a handful of passwords that we memorized in our heads, and for all the other accounts we simply used email-based password resets as authentication.
-
-I would probably have the following passwords in my head:
-
-* Full disk encryption
-* Computer login
-* SSH key
-* Email
-* Financial institutions
-* University
-* Maybe Merveilles.town or SourceHut too
-
-And if I needed to log into anything else, I'd simply reset the password, auto-generate a new one, paste it in, immediately forget it upon logging in, and repeat for any time I need to re-authenticate with that site. It would be an interesting way of doing things.
-
-[https://text.causal.agency/017-unpasswords.txt](https://text.causal.agency/017-unpasswords.txt)
-
-
-## Servers
-
-Using one big server instead of several tiny "cloud native" or "kubernetes cluster" container things or whatever the buzzword is for it today is often cheaper, simpler to manage, less prone to incomprehensible failures, and just as if not more powerful and capable than the latter.
-
-[https://specbranch.com/posts/one-big-server/](https://specbranch.com/posts/one-big-server/)
-
-
## Cycling
Various cycling-related resources
@@ -146,42 +56,70 @@ Various cycling-related resources
[Bicycle Shops in Ottawa, Canada](bicycle-shops-ottawa.html)
-
## Software Simplicity
-Simplicity is not about the number of parts something has, it's about how intertwined they are.
+Simplicity is not about the number of parts something has, it's about how
+intertwined they are.
-Mutable state or immutable state both contribute to complexity because the more state you have, the greater the number of possibilities in your program. This grows non-linearly. Branching also grows complexity non-linearly. Timelines/threads that need to communicate also contribute. There are 1,000,000 different ways that two processes can execute 12 steps, for example.
+Mutable state or immutable state both contribute to complexity because the more
+state you have, the greater the number of possibilities in your program. This
+grows non-linearly. Branching also grows complexity non-linearly.
+Timelines/threads that need to communicate also contribute. There are 1,000,000
+different ways that two processes can execute 12 steps, for example.
-More state also means more code to handle consistency. It is hard to reason about program outcomes when there is lots of state.
+More state also means more code to handle consistency. It is hard to reason
+about program outcomes when there is lots of state.
Mutable state is worse than immutable state because there is change over time.
-Naturally, reduce complexity by removing constructs that contribute to it. Keep mutable state small so that it's easier to manage.
+Naturally, reduce complexity by removing constructs that contribute to it. Keep
+mutable state small so that it's easier to manage.
Simplicity is hard. It requires conscious effort to maintain.
-Object Oriented Programming is uniquely hard to make simple. OOP has state and procedures that manipulate this state which can get very complex and hard to limit or restrict. OOP leads to additional complexity because more code is needed to manage this state. Languages that don't fall into this trap seem to be Actor-style languages and SmallTalk (the original OOP language, from which OOP seems to have been corrupted into whatever the heck it is today). Pure functional programming eliminates state and is naturally highly parallel sizable because it avoids state.
+Object Oriented Programming is uniquely hard to make simple. OOP has state and
+procedures that manipulate this state which can get very complex and hard to
+limit or restrict. OOP leads to additional complexity because more code is
+needed to manage this state. Languages that don't fall into this trap seem to
+be Actor-style languages and SmallTalk (the original OOP language, from which
+OOP seems to have been corrupted into whatever the heck it is today). Pure
+functional programming eliminates state and is naturally highly parallel
+sizable because it avoids state.
## Software Complexity
There are three areas:
-* Domain complexity - complexity inherent to the domain (e.g. rocket science software will be more complex than grocery list software)
-* Architecture complexity - how you choose to architect your software (e.g. building on the web vs. native application)
-* Development complexity - mistakes or inefficient programming (e.g. using threads)
+* Domain complexity - complexity inherent to the domain (e.g. rocket science
+ software will be more complex than grocery list software)
+* Architecture complexity - how you choose to architect your software (e.g.
+ building on the web vs. native application)
+* Development complexity - mistakes or inefficient programming (e.g. using
+ threads)
-Essential complexity is the essence of the problem as seen by the users. It is complexity that cannot be avoided because it is the very nature of what the program needs to do.
+Essential complexity is the essence of the problem as seen by the users. It is
+complexity that cannot be avoided because it is the very nature of what the
+program needs to do.
-Accidental complexity is all the rest that the developer would not have to reason about in the real world (e.g. manipulating registers, memory management, unnecessary abstractions, over re-use of data types, data hiding, etc.).
+Accidental complexity is all the rest that the developer would not have to
+reason about in the real world (e.g. manipulating registers, memory management,
+unnecessary abstractions, over re-use of data types, data hiding, etc.).
-A useful data structure for managing complexity is the tree since it can store exponentially more data for each unit of depth.
+A useful data structure for managing complexity is the tree since it can store
+exponentially more data for each unit of depth.
-A useful way is to program in a data-oriented way where you program at different data interpretation levels (e.g. byte->char->json->http) without needing to define an API inside your program. You are free to move up and down the levels without indirection.
+A useful way is to program in a data-oriented way where you program at
+different data interpretation levels (e.g. byte->char->json->http) without
+needing to define an API inside your program. You are free to move up and down
+the levels without indirection.
-Don't prematurely add complexity to code because "one day you might need to use another database engine" or something like that. Wait until you actually need that other database engine to make the changes. You will have to rewrite some things for the new database engine, but your code overall will be simpler.
+Don't prematurely add complexity to code because "one day you might need to use
+another database engine" or something like that. Wait until you actually need
+that other database engine to make the changes. You will have to rewrite some
+things for the new database engine, but your code overall will be simpler.
-Avoid abstraction barriers: places where abstractions become black boxes, hard to interact with or reason about.
+Avoid abstraction barriers: places where abstractions become black boxes, hard
+to interact with or reason about.
[My Response to Out of the Tar Pit](https://ericnormand.me/podcast/my-response-to-out-of-the-tar-pit)
@@ -189,47 +127,82 @@ Avoid abstraction barriers: places where abstractions become black boxes, hard t
[What is an Abstraction Barrier](https://ericnormand.me/podcast/what-is-an-abstraction-barrier)
-
## Programming Language Design
-Power corrupts. The more powerful a language, the harder it is to understand what the software does. Compare: C++ vs. C.
+Power corrupts. The more powerful a language, the harder it is to understand
+what the software does. Compare: C++ vs. C.
-An ideal declarative programming language is one that can formulate some kind of formal specification from an informal specification. It would be able to know exactly how much state is needed, and manipulate only that state doing only the necessary control operations.
+An ideal declarative programming language is one that can formulate some kind
+of formal specification from an informal specification. It would be able to
+know exactly how much state is needed, and manipulate only that state doing
+only the necessary control operations.
-Using multiple languages that each have different restrictions can be useful. Restrictions can help frame problems of different domains in ways that would reduce complexity for those programs.
+Using multiple languages that each have different restrictions can be useful.
+Restrictions can help frame problems of different domains in ways that would
+reduce complexity for those programs.
## LispCast 163 Notes
-Alan Kay indicated that it's impossible for an app designer to be able to anticipate the needs of millions of users. An extensional system in which end users do most of the tailoring and even construction of new tools themselves is ideal.
-
-"There would be millions of personal machines and users. Where would the applications and training come from? Why should we expect an applications programmer to anticipate the specific needs of a particular one of the millions of potential users? An extensional system seem to be called for in which the end users would do most of the tailoring and even some of the direct construction of their tools." - Kay
-
-These days you simply buy or download an app and train yourself to use it, there is little customization of your workflow to fit your needs, only fitting yourself inside of another's ideas of how you should work.
-
-Alan Perlis: "It has been such a long time since I have seen so many familiar faces shouting among so many familiar ideas, discovery of something new and programming languages like any discovery has somewhat the same sequence of emotions as falling in love, a sharp elation followed by euphoria, a feeling of uniqueness, and ultimately the wandering eye."
-
-"A twentieth century problem is that technology has become too "easy". When it was hard to do anything whether good or bad, enough time was taken so that the result was usually good. Now we can make things almost trivially, especially in software, but most of the designs are trivial as well. This is inverse vandalism: the making of things because you can. Couple this to even less sophisticated buyers and you have generated an exploitation marketplace similar to that set up for teenagers." - Kay
-
-This is basically saying "things were better when they were worse", but it's worth exploring why he feels this way instead of dismissing it as the angry rants of an old man against today's youth. Perhaps it's so easy to make bad designs because of a lack of constraints in our modern systems. Perhaps education is highly lacking and we have "armed neanderthals with guns and tanks", as it were.
+Alan Kay indicated that it's impossible for an app designer to be able to
+anticipate the needs of millions of users. An extensional system in which end
+users do most of the tailoring and even construction of new tools themselves is
+ideal.
+
+"There would be millions of personal machines and users. Where would the
+applications and training come from? Why should we expect an applications
+programmer to anticipate the specific needs of a particular one of the millions
+of potential users? An extensional system seem to be called for in which the
+end users would do most of the tailoring and even some of the direct
+construction of their tools." - Kay
+
+These days you simply buy or download an app and train yourself to use it,
+there is little customization of your workflow to fit your needs, only fitting
+yourself inside of another's ideas of how you should work.
+
+Alan Perlis: "It has been such a long time since I have seen so many familiar
+faces shouting among so many familiar ideas, discovery of something new and
+programming languages like any discovery has somewhat the same sequence of
+emotions as falling in love, a sharp elation followed by euphoria, a feeling of
+uniqueness, and ultimately the wandering eye."
+
+"A twentieth century problem is that technology has become too "easy". When it
+was hard to do anything whether good or bad, enough time was taken so that the
+result was usually good. Now we can make things almost trivially, especially in
+software, but most of the designs are trivial as well. This is inverse
+vandalism: the making of things because you can. Couple this to even less
+sophisticated buyers and you have generated an exploitation marketplace similar
+to that set up for teenagers." - Kay
+
+This is basically saying "things were better when they were worse", but it's
+worth exploring why he feels this way instead of dismissing it as the angry
+rants of an old man against today's youth. Perhaps it's so easy to make bad
+designs because of a lack of constraints in our modern systems. Perhaps
+education is highly lacking and we have "armed neanderthals with guns and
+tanks", as it were.
[LispCast: The Early History of Smalltalk](https://ericnormand.me/podcast/the-early-history-of-smalltalk)
[The Early History of SmallTalk](http://worrydream.com/EarlyHistoryOfSmalltalk/)
-
## LispCast 142 Notes
-The problem with powerful languages is that it breeds individualism. Because it's so easy to develop a solution that fits your needs (does 60% of the whole), you don't collaborate or contribute to a team that's trying to solve the same problem. We end up with 100s of libraries that roughly do the same thing, but not quite. People become obsessed with bootstrapping but never take these concepts to their "final point". No boring/mundane work is done to finish or take the project to completion. This is common in "rockstar" programming.
+The problem with powerful languages is that it breeds individualism. Because
+it's so easy to develop a solution that fits your needs (does 60% of the
+whole), you don't collaborate or contribute to a team that's trying to solve
+the same problem. We end up with 100s of libraries that roughly do the same
+thing, but not quite. People become obsessed with bootstrapping but never take
+these concepts to their "final point". No boring/mundane work is done to finish
+or take the project to completion. This is common in "rockstar" programming.
-(I argue this is good. Not only does it create programmers knowledgable and skilled in solving more problems (reducing division of labour), it reduces the need for dependencies and eliminates the control that another entity has over your software.)
+(I argue this is good. Not only does it create programmers knowledgable and
+skilled in solving more problems (reducing division of labour), it reduces the
+need for dependencies and eliminates the control that another entity has over
+your software.)
-Companies would rather have several replaceable programmers than have one skilled but important programmer who isn't as easily replaceable.
+Companies would rather have several replaceable programmers than have one
+skilled but important programmer who isn't as easily replaceable.
(This is why this sort of power is good actually.)
[What is the Curse of Lisp?](https://ericnormand.me/podcast/what-is-the-curse-of-lisp)
-
-## Suburbia
-
-Suburbia is bleeding North America dry. Not only has it led to vast networks of asphalt which need to be maintained to support a car-addicted and car-dependent society, it also results in the creation of boring, same-y,
diff --git a/content/garden/index.md b/content/garden/index.md
@@ -20,12 +20,8 @@ garden. Explore at your leisure.
## 🌱 The Greenhouse
The Greenhouse is the place where new things are incorporated into the garden.
-It is the sprouting place for seeds that may eventually develop into projects.
-
-* [AoM Podcast #825: Tactics and Mindset Shifts for Making the Most of
-Life](tactics-and-mindset-shifts-for-making-the-most-of-life)
-* A [collection of notes and clippings](clippings) from articles that
-don't yet fit anywhere else, but which I still find valuable.
+It is the sprouting place for seeds that may eventually develop into projects
+or wiki pages.
### Intake
@@ -37,11 +33,9 @@ Here are links, documents, and other things I found interesting that I want to g
* [The Super Tiny Compiler](https://github.com/jamiebuilds/the-super-tiny-compiler)
* [Write a Shell in C](https://brennan.io/2015/01/16/write-a-shell-in-c/)
* [Build Your Own Text Editor in C](https://viewsourcecode.org/snaptoken/kilo/index)
-* [Why APL Is a Language Worth Learning](https://mathspp.com/blog/why-apl-is-a-language-worth-knowing)
* [Virtual Machines 0](https://elly.town/d/blog/2021-12-24-virtual-machines-0.txt)
* [Virtual Machines 1](https://elly.town/d/blog/2021-12-29-instruction-encoding.txt)
* [Economy and Pleasure](https://wiki.xxiivv.com/docs/economy_and_pleasure.txt)
-* [Learn Ada Core](https://learn.adacore.com/)
* [Principles of UI](https://notes.yip.pe/notes/notes/Principles%20of%20UI%2C%20A%20Thread)
* [What The Hell Is Forth?](https://blog.information-superhighway.net/what-the-hell-is-forth)
* [Reading Assembly Is Easy](https://www.timdbg.com/posts/fakers-guide-to-assembly/)
@@ -63,13 +57,11 @@ growing into full blog posts or projects.
* [Notes on A Philosophy of Software Development](philosophy-software-development)
* [Run Your Own Email](run-your-own-email)
* [Avoid News Media](avoid-news-media)
-* [The Attention Economy is Ruining Your Life](the-attention-economy)
* [Computer Science's Education Problem](computer-science-education-problem)
* [Good Computing Systems Let Users Mold Them](good-computing-systems-let-users-mold-them)
* [Nothing is Permanent](nothing-is-permanent)
* [The Fediverse Has Problems](fediverse-has-problems)
* [Computers as Place](computers-as-place)
-* [Buying What You Need When You Need It](buying-what-you-need-when-you-need-it)
### Projects
@@ -104,6 +96,8 @@ Notes on:
General documents, notes, and other bits and pieces I find valuable.
+* A [collection of notes and clippings](clippings) from articles that don't yet
+fit anywhere else, but which I still find valuable.
* [Laptops I Might Like](laptops-i-might-like)
* Benchmarking: [Fedora 36 Spins - Resource Usage Comparison](fedora-36-spin-resource-comparison)
* [Amateur Radio](amateur-radio)
@@ -141,7 +135,7 @@ I have categorized my opinions to make them easier to find:
* [General Programming Tips and Advice](general-programming-tips-advice)
* [Programming Philosophy](programming-philosophy)
* [Bad Assumptions Made By User/Profile Systems](user-profile-systems-bad-assumptions)
-* Programming languages: [C](c), [Clojure](clojure), [Haskell](haskell), [Raku](raku), [LaTeX](latex)
+* Programming languages: [C](c), [Clojure](clojure), [Haskell](haskell), [Raku](raku), [LaTeX](latex), [uxn](uxn)
* Tools: [git](git), [Vim](vim), [plan9](plan9), [Make](make)
### 🖥️ System Administration
diff --git a/content/garden/tactics-and-mindset-shifts-for-making-the-most-of-life.md b/content/garden/tactics-and-mindset-shifts-for-making-the-most-of-life.md
@@ -1,35 +0,0 @@
-Title: Notes from AoM Tactics and Mindset Shifts for Making the Most of Life
-Summary: Notes from AoM Tactics and Mindset Shifts for Making the Most of Life
-
-# [%title]
-
-[Podcast #825: Tactics and Mindset Shifts for Making the Most of Life](https://www.artofmanliness.com/character/advice/podcast-825-tactics-and-mindset-shifts-for-making-the-most-of-life/)
-
-
-Getting a physical letter is a tangible and permanent reminder that someone in the world appreciates you.
-
-Don’t make every thing A Thing™.
-
-100-year-old plan: consult your 100 year old self: what would they have cared about in the moment.
-
-Figure out what is actually important and let the rest flow by.
-
-Take time, think: Where am I, who am I, how did I get here, what point on the horizon am I currently chasing. No point = stagnant, living days that look the same as the last and are unremarkable.
-
-Think about life in minutes - seize the minutes here and there to do something instead of thinking that just because there isn’t a block set aside nothing can be done and wasting it on idle tasks like scrolling reddit or twitter that probably wont even make you feel good. Can use it to get some small portion of the task done.
-
-Most people unwilling to make hard decision to chase their dreams so they make no decision and end up down path of least resistance not using their time well.
-
-Spend less time on routine activities so we can spend more time doing the important things, especially routines that are not required of us (e.g going to 3-4 different grocery stores to get the absolute best deal on each different product you want).
-
-Tie mundane things to existing habits to form new habits out of those mundane things.
-
-Details matter but don’t forget to step back and see the whole forest instead of getting lost in the trees.
-
-Practice intentional incuriosity. There are plenty of things that don’t matter to us, so there’s no reason to get involved or become knowledgable about it. It doesn’t lead you anywhere/help you.
-
-Break rules/norms to see what happens... do people actually care about X, Y, or Z. You’ll find out if they do or don’t. If it is, you say sorry, don’t do it again, and move on with your life.
-
-Creative people start by making terrible things, its ok to release those because thats how you improve.
-
-People are too focused on themselves and their lives that they will likely not notice you or judge you, and if they do they will likely forget very quickly.
diff --git a/content/garden/the-attention-economy.md b/content/garden/the-attention-economy.md
@@ -1,17 +0,0 @@
-Title: DRAFT: The Attention Economy is Ruining Your Life
-Summary: DRAFT: The Attention Economy is Ruining Your Life
-
-# [%title]
-
-Is there even such a thing as "the attention economy"? I don't really know if that's an appropriate way to talk about this anymore, but more research needs to be done.
-
-[Need to Read "How to Do Nothing"]
-
-[https://www.theguardian.com/science/2022/jan/02/attention-span-focus-screens-apps-smartphones-social-media](https://www.theguardian.com/science/2022/jan/02/attention-span-focus-screens-apps-smartphones-social-media)
-
-[https://twitter.com/vgr/status/1047925106423603200](https://twitter.com/vgr/status/1047925106423603200)
-
-^ This is an extremely stupid take, but with some good points if you mental-gymnastic your way into a different interpretation
-
-[https://www.wired.com/1997/12/es-attention/](https://www.wired.com/1997/12/es-attention/)
-
diff --git a/content/garden/uxn.md b/content/garden/uxn.md
@@ -0,0 +1,25 @@
+Title: uxn
+Summary: uxn
+
+# [%title]
+
+A collection of resources related to Uxn:
+
+[https://100r.co/site/uxn.html](https://100r.co/site/uxn.html)
+
+[https://wiki.xxiivv.com/site/varvara.html](https://wiki.xxiivv.com/site/varvara.html)
+
+[https://github.com/hundredrabbits/awesome-uxn](https://github.com/hundredrabbits/awesome-uxn)
+
+[https://compudanzas.itch.io/introduction-to-uxn-programming](https://compudanzas.itch.io/introduction-to-uxn-programming)
+
+[https://wiki.xxiivv.com/site/uxntal.html](https://wiki.xxiivv.com/site/uxntal.html)
+
+[https://wiki.xxiivv.com/site/uxntal_cheatsheet.html](https://wiki.xxiivv.com/site/uxntal_cheatsheet.html)
+
+[https://wiki.xxiivv.com/site/uxntal_reference.html](https://wiki.xxiivv.com/site/uxntal_reference.html)
+
+[ircs://irc.esper.net:6697/#uxn](ircs://irc.esper.net:6697/#uxn)
+
+[https://text.causal.agency/017-unpasswords.txt](https://text.causal.agency/017-unpasswords.txt)
+
diff --git a/content/links.md b/content/links.md
@@ -46,6 +46,7 @@ Useful links that I've collected and wish to share or remember for the future. E
<li><a href="https://www.youtube.com/watch?v=HB5TrK7A4pI">"We Really Don't Know How to Compute!" - Gerald Sussman</a> - Though we have been building and programming computing machines for about 60 years and have learned a great deal about composition and abstraction, we have just begun to scratch the surface. [...] New design principles and new linguistic support are needed. I will address this issue and show some ideas that can perhaps get us to the next phase of engineering design.</li>
<li><a href="https://vimeo.com/731219273">Handmade Dev Show - Ink & Switch (2022)</a> - A discussion with the head of independent research lab Ink & Switch, Peter van Hardenberg, about how today's computing platforms are working against the needs of professionals.</li>
<li><a href="https://www.inkandswitch.com/local-first/">Local-first Software</a> - A new generation of collaborative software that allows users to retain ownership of their data.</li>
+<li><a href="https://specbranch.com/posts/one-big-server/">Use One Big Server</a> - Using one big server instead of several tiny cloud container things or whatever is often cheaper, simpler to manage, less prone to incomprehensible failures, and just as if not more powerful and capable.</li>
</ul>
</details>
