if for some reason you find yourself flying from burlington vt to a dc/baltimore airport: this is a perfect time to enjoy larksโ tongues in aspic [the album]
Any conversation
An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using it.
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:The abuse (in my opinion) of the auto-translate feature is super annoying. Thanks goodness for โblockโ.
The best Mcp server I have as Claude Connector is Emacs running on my Homeserver. It has one tool - eval-elisp. Using it Claude can do almost anything. My top 1 pinned chat is โRun agent-start-claude-code using HotterEmacs in dir โฆโ - after that I have a ready to use remote-controlled session running on my homeserver.
ennek a laptopnak mindegy mรกr szegรฉnynek, annyi minden tรถrtรฉnt mรกr vele, most telepรผl rรก a Gemma 4 26B A4B QAT, az eredeti tervek szerint, amik lehet, hogy nem is a mi terveink, de arrรณl mi mรกr nem nagyon tehetรผnk, mert a kรถrรผlmรฉnyek รกldozatai lettรผnk
This laptop doesn't matter anymore, poor thing, so much has happened to it, now Gemma 4 26B A4B QAT is being installed on it, according to the original plans, which may not have been our plans, but there's not much we can do about it, because we've become victims of circumstances
I remain ambiguous. This morning I used pi+gpt5.6 to create a color scheme based on evergarden.moe. It works, and I havenโt checked how well it stay true to the style used in vim-bundled schemas. Before I wouldnโt have done this, and now I can. But I donโt know if it is good. github.com/โฆ/evergarden.vim
One idea that I've been thinking about is an or where it is a app so you get a new file everyday right except the app keeps track of all the files for you. the idea is that anytime you type anything it it basically makes a commit and use so anytime you type something it commits automatically after a quick pause after you stop typing.
That sounds ! Could also create summary titles with for the filenames in addition to their date so you can find what you were writing about easily. Also full text search.
I have made this longer than usual, only because I have not had the time to make it shorter ~ Blaise Pascal
So, should we all give AI agents more time so they'll write things shorter?
Too much sound deafens us; too much light dazzles us; too great distance or proximity hinders our view. Too great length and too great brevity of discourse tends to obscurity; too much truth is paralyzing. - Blaise Pascal
You reminded me of this other quote, from what I think might be my absolute favourite passage in B.Pascals Pensรฉes, thank you!
Hello to friends. Holla for tools.
๐จโ๐ป : , , and Pragmata Pro
๐ช : NotePlan
๐ง : Overcast
๐ง : Allume
๐๏ธ : Mark Two (EDC), Pen Type-B
๐ณ : Anisota
Really glad to be using Haskell for work - especially in today's climate with agentic coding.
Our team uses containers to keep our development environment consistent across team members, though, and most agent sandbox approaches want to either offload your work fully to the cloud or they want to sandbox the agent harness process itself.
We're not ready for full cloud based development (yet?) and sandboxing just the agent doesn't work for us when the agent needs to run docker.
... because letting the agent run docker gives them a too-easy escape hatch from their sandbox.
So we're currently stuck with using VMs. This turns out to be tricky but seems do-able.
My current approach is to provision a VM image and use Incus for the execution. My main goal is to keep my current workflow of local/non-agent dev working seamlessly and share the source with the VM/agent.
This means sharing my working dirs with the agent VM but overlaying artifact dirs from VM-owned block devices so we don't take too big of an IO perf hit.
I also don't want the agent to be able to
git push so that means we need some quirky git config to rewrite origin paths and thread through some agent specific PATs ("thanks" GitHub) for read-only repo access. These ALSO need to be threaded through to the development containers - they need to clone private repos.... in the end, this seems to work but I haven't lived with it for long.
There are still some quality of life issues to work out, but I think it'll work out.
At this point, I've removed all coding agents from my host - and that's nice.
Curious, why does using Haskell make a difference here?
It's tangential to the sandboxing topic, really. I started the first post with a broader intent in mind and then elaborated on the sandboxing setup I'm working on.
For AI-assisted coding, though, it's nice because Haskell provides a lot of feedback earlier in the development process compared to lots of other languages. It tends to work once it compiles (obviously not all the time).