Week Notes #31 - 2026

Tuesday - Aug. 4th

• Spent yesterday and today working on an intro piece about NeoDoc to post on the atmosphere.community discourse server.

  Posted a copy on the NeoDoc site as well.

• I put so much effort into writing the long intro pieces that I wanted to make stick that I'm wiped out.

  Was gonna try to do some parser work tonight, but I'm thinking I may just crash early.

Wednesday - Aug. 5th

• Finally got back to actually working on the NeoDoc parser.

• I've been kinda tired the past few days. Still am, but maybe less? Got a little headache going to. I think part of it was just from pushing so hard on writing a few days earlier.

Thursday - Aug. 6th

• Yeah, I'm feeling better. Was definitely a bit down. I'm increasingly thinking it really does take a full week for me to recover from the road trips.

  10hours both ways, sleeping on a mattress that is just slightly uncomfortable, and the stress of moving someone probably is a reasonable for needing time to recover. Just surprises me that it's a full week. I would have thought a few days would do it.

Friday - Aug. 8th

• Made a blog on pckt.blog. I don't expect to do a lot with it, but I wanted to see what it's like.

  Especially as a kind of scouting to see how NeoDoc could fit with it.

Sunday - Aug. 10th

• Spent the better part of the day recording and audio version of How creatives and devs can all finally escape the control of the silicon valley of evil and make a trillion dollars

  I really like the post and I've been thiking more about audio recording. I've got everything recorded. I look up how to say all the names I didn't know and hopefully got them right.

  I'm stuck in the editing right now. The way I did the recording was to just redo things immediately when I flubbed them. I've done that in that past for shorter pieces and it's been fine. When I edit I just listen when I flub delete the section.

  It doesn't take that long each time. It'll be shorted when I get around to setting up better hotkeys.

  But, what I realized I really need to do is set it up so that I only capture the good takes. Basically, start recording and then have two buttons. One for if the take is fine and one for if it's not. Then drop the ones that aren't. I won't be surprised to find that's already built in or there's an even better way to do it. Just need the spoons to look into it more.

  If I get the edit done, I'll send it to the author privately so see if they're interested. It's clear from the audio that I'm not practiced at it. Plus, I'm a white dude and I think the author is a black woman. So, it may be out of bounds even as an option. But, I figure I'll at least offer since some other folks might listen to the piece who otherwise wouldn't have read it.

  (In fact, part of the reason I recored it is that was the easiest way for me to get through reading it. Weird, but it works)

• Did a bunch of writing the past few days. Not as much work on the parser as I was intending, but I was in the flow with the writing so that's where the energy went.

  A thing that maybe I knew before, but feels like a rediscovery is how much writing takes out of my vs coding. Writing is way more. Probably something to do with with imagining myself in the mind of the audience. It's like ersatz social interaction.

Outro

Was kinda feeling under it for a bit, but feel back to nominal now. Sleep schedule is still wonky, but that's fine for now. Just have to not let it get too sideways.