Damn, that actually sounds like a genuinely nice experience. I'd recommend books, and a battery pack or two (not sure if there's electricity available), a blanket (unless you got a sleeping cabin) and comfortable clothes.
unicorn, n. - The purest and rarest cob, identified by a singular majestic kernel. Sightings can be found between Ogallala and Dubuque through summertide.
Finally got around to setting up Remux on my phone so I can connect to tmux sessions when I'm not at my laptop. Even just for around the house, this seems like it'll be super useful.
This is for monitoring/poking agentic coding sessions while I'm not at my computer. So, typically Claude, Emacs, and an overmind process running my app locally in different panes of a tmux window.
Call me old fashioned, but instead of adopting one of the "agentic coding orchestration frameworks" that seem to basically be reinventions of tmux, I've been tweaking my tried-and-true tmux-oriented workflow to incorporate agentic coding harnesses in an ergonomic way. I'm currently still using Claude Code, but getting Pi-curious as local models advance.
I will be dead, and many years will pass after that, before local models are capable to match those of the big companies, unless their intended use is banal.
It seems like we've reached a point where mid-grade frontier models like Sonnet are good enough for most day-to-day tasks. And Sonnet-grade models are already runnable on the higher end of consumer hardware.
In which case, I can imagine a workflow where local models serve as workhorses for implementing plans that you may bump up to e.g. Opus or Sol to produce.
A #execnotesfollown=27;s=[n]
while n!=1:
n=n//2if n%2==0else3*n+1;s.append(n)
for v in s[:15]:print(f"{v:>4} "+"█"*min(v//3,40))
print(f"{len(s)} steps, peak {max(s)}")
What if AI will never reach full autonomy and humans are still needed to give direction and purpose and take responsibility - probably... not all humans like to be masters of AIs all day long and not all (who want to) can do that equally well.
Huge refactor today, moved from sync SQLite to Worker based, touched 88 files, pre-#AInotesfollow it would have taken a week or so, finished now in ~1:30h. And I wouldn’t have the confidence I have now that it went correct. It went well, though a bug or two might surface, we’ll see.
SQLite is embedded in the main thread same as the HTTP server. I noticed some requests dropping and because the queries have become more complex I figured it has to do with SQLite blocking for too much time. Moving it to a Worker makes the DB asynchronous and bypass this problem.
(defun textlog-post (beg end)
"Publish the region between BEG and END to `textlog-url'.
Interactively, requires an active region. Returns the URL of the
new post when the server reports one."
You have #kakounenotesfollow, there is no need. I tried Emacs out a while ago to see whether it could replace Kakoune (I wanted to draw arbitrary stuff like images, 3D views, etc., in the editor) but honestly, Kakoune makes everything so easy to integrate that it was hard for it to compete.
I laughed at this. I'm all for people crafting their own tools, but it really feels like everyone's reinventing the same handful of wheels for agentic development.
Reading Slow Productivity by Cal Newport, discovered via onboarding content in mymind mymind.com
@kev🧜profilefollowrunner. making games, music, software. getting into as much trouble as i can.wrote:
Off to handstand class. I have been known to recommend to everyone within earshot doing challenging and/or silly physical things in a community. Not bucking the trend here.