This month is the first I formally reckon according to the Tibetan lunar calendar.
It's an experiment in living the view
: : : :
It seems helpful, at the outset of some period, to state your orientation -- bearing -- attitude -- intention
: : : :
April 3rd, 2025
I suckered myself into reading some essays about AI yesterday, in roughly this order:
-
AI Ambivalence
"Here’s the main problem I’ve found with generative AI, and with 'vibe coding' in general: it completely sucks out the joy of software development for me."
-
The death of the junior developer
This one got me because it was referenced as "CHOP" in the "Revenge of the junior developer"
The author predicts that AI will totally obliterate junior engineers.
-
Revenge of the junior developer
The same author as "The death of the junior developer"
"Switch to chat. Ditch completions. Stop writing code by hand. Learn how validation and verification work in the new world. Familiarize yourself with the space, and follow the state of the art. Stop whinging and turn this into an engineering exercise. Stay on top of it. You can do it."
(This author makes a living selling genAI.)
-
On AI
An essay about not ceding ground
"I guess I'm with the Luddites now."
(I agree)
-
Is it okay?
An essay about Everything the sum total of human creative output in the commons.
"You gotta take care of your own soul, and I’m writing this because I want to clarify mine."
. . .
How exhausting.
I cannot imagine anything I would want to do personally that I would also be willing to hand off to an AI agent.
Maybe that's a personal problem.
: : : :
In happier news, I found a fledgling tui web browser: chawan
April 4th, 2025
Let myself get nerd-sniped, hard, by implementing nested string interpolation for clox.
There are worse ways to spend a friday afternoon.
April 16th, 2025
I followed a thread on "evergreen note-taking" and ended up producing a pile of connected notes:
I think I'm starting to circle around a sweet-spot intersection of music & math -- engineering, research, art
I'm still writing this site basically by hand (except for the phraxOS script). I don't want to try and scale it out too far, and I think this is important to get right.
April 18th, 2025
I really like doing stuff in these <pre> blocks, reminds me of the good-old-days of writing everything in plain text source files. This is a test internal link This is anh2
This is anh3
This is anh4
This is anh5
April 19th, 2025
I've been thinking about how to break what I do up into executable strategies, or "procedures"; basically discrete, focused chunks of activity. It's important that they're focused, or tightly contained in some way, because this makes it very easy to pour energy and attention into.
One idea: take 30 minutes with a blank octatrack project and do whatever I can with it. Or, take 30 minutes with on OT project that has some stuff loaded, go to a new bank, and do whatever I can in 30 minutes.
The point is not to make something finished, per se, or to make something slapdash, it's to do whatever. It's to practice being creatively and emotionally unblocked.
Let's try it!
: : : :
That, was a fantastic idea.
Next time I'll try to remember to record it all into reaper.
The thing is, I want my plaintext notes to look like an alien markdown language that nobody has ever seen before
Consider an adaptation of the para (?) method?
No Boilerplate has a useful video on the good parts of obsidian.
I agree with him on some aspects of it.
particularly:
- don't use or rely on directory structures
- do use tags
- do use links
- make links easier.
my gripe is that obsidian is too much like plain oatmeal.
I could start by making links a little easier
Possibly of interest: YSH