michael-dean-k/

I was able to launch this website in <15 minutes. The setup is local and simple. I have a /writing file in my Obsidian vault, and then subfolders for /code, /publish, /working. /Code holds the site design, /publish my archive, and /working files have .gitignore to not push templates and notes and such. Claude Code handles the website, and different skills help me manage tags, do the menial ops stuff, and push to the Internet. All I have to do is sync a single folder to Github, and the changes are live (hosted on Netlify for free).

Compare this with my first website prototype. I was endlessly iterating on designs and fonts, and thought that I had to organize, filter, and polish my five year archive before I could get started. Probably spent hours on it before burning out on the haul. With this second version, the principle is essentially, "if it doesn't immediately produce something of long-term value, it's not worth systematizing." Now the approach is to move forward here, and slowly fill in the backlog as I'm inspired.

No need to widely share this yet. I'll make little changes day-by-day until it becomes my main place. So many things to consider. For example, I decided to add an initial on the name ("michael-dean-k"), but without hyphens ("michaeldeank"), my wife confused me with "Michael Dank."

I declared to my wife this morning that DeantownOS is getting retired. It’s been 3 months since I spiraled into Claude Code for personal systems, and I’m at the point in the curve where the amazement has normalized and I’ve accepted the fact that I’m in a trough of disillusionment. The question now is revise or abort.

The case for aborting ties back to Oliver Burkemann’s Four Thousand Weeks, which popularized the idea that all systems are methods to procrastinate from making hard decisions. They give the illusion that you can do everything, and since AI can meaningfully leverage the volume and range of things you can do, it tempts you to build galaxy-brained systems. The thing I think we fail to realize while in a vibe coding frenzy is the psychic cost to remember and maintain the stuff you build. Yes, it is appealing to “reclaim my computer” and rebuild everything I use as personal software (from Obsidian to Gmail), and it’s even possible, but it’s a new breed of Sisyphean struggle. Once you can mold your own software around you, it’s too easy to endlessly mold, to lose sight of the work and just tinker on your exoskeleton.

I’m obviously skeptical, but I’m still a believer; if I were to revise, to rebuild my Claude stack from scratch, I would have to develop a few heuristics to help me from short-circuiting.

The first one that comes to mind is “will this matter once I’m dead?” Ie: writing an essay matters, because I imagine one day my daughter will read that and get to know me better, or at the very least, future Me in 35 years may enjoy reading words of my past self. But to create detailed daily files that get spliced into atomic “routing files” that then then get saved again to a new destination folder, which exist either as (a) just context for AI, or (b) require some manual effort to prune into something that matters once I’m dead, is to create waaaay too many layers of abstraction between the source and the Work. When I read back my writing from the last few months, only a small is valuable enough to be saved as "logs" in my archive. I was writing for AI, not for my future self.

I made this assumption that atomic daily files are the kernel of a system, and it was an axiom I could never undo. There’s maybe another principle on “don’t build load-bearing infrastructure on an unproven axiom.”

Another one could be “don’t assume future you will have bandwidth,” to do X every day/week/month. Every day I had to review how my AI system proposed to route my logs, and eventually I'd ignore it and get backed up. This means that if something isn’t truly automated, I should be very cautious of it. It's possible to do one little step forever, but not a hundred. Not every promise has brush-your-teeth-scale reliability.

What I’m getting at is that it’s not about maximizing or neglecting systems, but about understanding the right principles so you build something that is actually in service of your life.

I want to be in conversation with my books. This was Montaigne’s whole thing. He did this for 10 years. I can’t help but think that Kindle/eBooks/digital reading is a better format for this. If I were only reading, ie: if I were retreating into a tower to retire and die, then I’d see the appeal of doing it all by hand. But this is maybe a 3rd of 5th or realistically 10th priority. I’m called to it, but given the range of things I’m juggling, efficiency actually does matter here. I know efficiency does bring invisible amputations, but also, if I’m not efficient here, I might just not do it in the first place. Since all my highlights sync to Obsidian, I can build a writing app that loads in highlights and then let’s me write directly to them.

I suppose the counter-argument is that I am juggling too many things. If I were really to choose, to pick the project I’d have to do, it would probably be to focus on building my business to support my family, but that also cuts me off from soul and spontaneity in the first place, and so this whole reading/writing for leisure thing is a healthy counter-balance.

I don't know if I buy the quote: "you don't rise to the level of your goals, you fall to the level of your systems." (And this is coming from a systems guy.) It's a beautiful piece of rhetoric. The rise/fall structure. The humility to stay grounded. But I just think when you really want to make sense of how to pull off hard things, it should be a little complex, a little more than what can be packaged into a meme.

Two opposite things need to happen at once: top-down destiny forging, and bottom-up monk-like routines. It's a negotiation: "What will I want to complete in 100 days?" is a very different question from, "What should I be doing today?" and you can try to force alignment, but that's not always easy, because what you feel like doing often diverges.

The quote above simplifies this whole dance into a blind trust in systems. A system is a servant, not a master! I write this to remind myself as I'm immersed in probably one of the biggest system rebuilds in my life (one where I'm suddenly able to fluidly create the containers I work within) ...

It is wild to think that probably 50% of my computer use these days are within GUIs I've designed for myself. To me, liquid GUIs are a bigger deal than autonomous agents. My whole conception of what personal computing can be is changing very fast, and it becomes alluring, almost addicting, to continuously evolve my own OS, to see what's possible. It's very easy now to get tangled in knots of systems and software that are all very impressive, lead nowhere, and become chores. What leads to aliveness, to your intentions?

An emerging maxim for me is to start with the goal and let the system emerge around it; otherwise, you feel the cold of the infinite tinker, especially if you are quarantining in the attic from COVID and you can't go touch grass because there appear to feet of snow outside and you are too achey to shovel out your car to go anywhere and so one way to relax when you're sick is to live-clone all incoming Substack posts into local JSON folders and redesign a better algorithm. But to what end?

I set up a chronofile, inspired by Buckminster Fuller's system, where he logged every 15 minutes for like 70 years. That's intense! I'm going to run an experiment. In the past I've operated under the premise of "capture as little as possible," as in, capture just what's worth it, because then you'll have a mess of notes to go through. But agents change this; all the yak shaving (tedious, endless work) is handled. This could lead to hyperlogging, 100-400 logs per day. I've done this before as a kind of Hermetic T1 ritual (from Franz Bardon), and it's an intense way to see everything crossing your mind. This scale of writing might be the best way to "meta-program" your psyche. Essays do this in a way, but an essay let's you go very deep on a particular idea (and you might be deluding yourself, or you might be articulating a take in an ideology that you'll outgrow in 5 years).

Paul Graham’s idea of makers/managers is helpful when thinking about AI agents. The cost of being unreasonably productive is that all your time will go into management. I’ve heard people celebrate this, as if elevating above the work itself and only making high-leverage decisions based on taste is the place we want to be. Disagree. Without actually being in the weeds and making thousands of unbearably slow decisions, you won’t develop taste, and (probably) won’t be a great manager either. I guess the ideal (for me) is to be in maker mode as often as possible, and then let my synthetic managers come in to process my deep work. (Currently have a “proseOS” where I can riff 5k words into a daily note, and then agents come in to route my logs to different interfaces). Ideally, you build the manager once and forget about it. But realistically, a maker can find fun in making manager bots and management apps, and it’s quite easy to slip into a managerial goon loop. What I mean is, similar to masturbating with no intention of ever finishing (aka gooning), it’s very possible to make your own task manager app, and a writing app, and an idea Kanban linked to Obsidian, and why not a new personal website, and a 1,000 day calendar because you can, and seriously anything you can think of, and it’s very possible to just numb out over how unbelievable it is that code, markdown, and interface are now liquids that shape around your every intention, but actually, you never quite finish anything. PKM procrastination is timeless, except now it’s multiplied to new levels. The brute velocity of execution means you’re bound to make many little mistakes, which eventually compound into your own megamachine that traps you with endless bugs and feature ideas and system decay. This is all quite dramatic. I love Claude Code and insist everyone IRL and IFL try it. But now that it’s shockingly trivial to build your own personal software for free, I imagine there will be all sorts of unanticipated psychic costs. For one, it’s dangerous if building your own tools is equal to or more fun than the work the tools are for. I’m sure that wears off. But I generally think this all leads to both extremes: individuals who are unbelievable prolific, and individuals stuck in a goon loop who feel unbelievably prolific.

The “wasted time” in AI-generation is generating reports and “canonical documents” that you think your future self will need, but will possibly never use. However, I think the core difference is that these documents have a way of compounding that is automatic in a way that second brains never did. Meaning, yes, I generated 8 documents on babies, but the 9th one, can be based on the thinking in the first 8. Shed the original, but maybe 9 is something like a core “README” that shapes all future interactions. That’s the thing. Through writing you are developing a particular lens that is not just sitting there, but being accessed.

A big shift in my way of working: instead of trying to scope a specific and ambitious batch of tasks I think should be done in a given day or week, all I commit to is time towards specific areas. The deadlines are less important (generally) than making sure I show up and do high-leverage work with 100% embodiment and enthusiasm. I just set up the Streaks app, and aim for 2.5 hours of work per day over 6 areas: writing, coding, reading, outreach, business, and culture. Each is a simple target: 20-45 minutes per day. At the very least, it gets me started. If I’m in a flow, I go over as long as I want (1-2 hours or more). If not, I just stop. The goal here is to rethink what work might look like while caring for my daughter (and my post-labor wife). I could potentially knock out 2.5 hours in a single nap cycle, or maybe it’s spread over 3-4 sessions at random times. It forces me to prioritize an important thing per day in an area that is an infinite game. It feels slightly unambitious, but I actually think an OS of this nature might be something I continue even when I “get my time back.” There’s a forced prioritization, as well as open space to either (a) diverge/explore, or (b) drill deep on things that actually matter.

I’ve been reflecting on how my writing will change once I have a newborn, and I keep coming back to this idea of releasing a “monthly EP of essay demos.” This means that I’ll send a post with 5-10 links to other essays that I “ghost posted” (publish without sending) earlier in the month.

I currently only have the S and L lanes of writing working. Either it’s a 2-minute log or a 20-hour essay. The goal is to prioritize the M (medium) lane, a 2-hour essay; instead of sending them out in real-time, I’ll batch them and let readers click into the topics they want. Feels like a strategy to be more divergent, more experimental, less formal, without overwhelming people and confusing them from the core mission of Essay Architecture.

I had Coco read through a week of my logs, and she shared three patterns she’d want to read more of: (1) unique, vulnerable experiences that show conflict and inner struggle; (2) lens on for self-improvement regarding life or writing; (3) culture commentary that helps make sense of big ideas. She was less interested in technical topics, or hypothetical scenarios (such as trying to imagine the handicap we’d have to give tennis pro Carlos Alcaraz for us to have a competitive match in tennis). The beauty of the EP strategy is that it gives readers a menu, and each will have their preferences.

Whenever you open an app you give it permission to shape the grooves of your attention. Through its interface, it suggests and implies a limited range of ways you can interact. This all sounds very abstract, and what I really want to say is that I think my Things app (the #1 best selling productivity app, I assume) keeps me in a kind of productivity hell. I have, what, 84 things to do today? Tasks lists should not be ambient all-day guides. I should leave it in the closet, go in there and whiff it for 5 minutes, max 10, commit to memory whatever is important, and then not go back until tomorrow.