OMP + OpenCode Zen + Ox Alpha is too good to be free.
Any conversation
Putting a slide deck together (outside of work), despite agreeing with Tufte on this matter. Iโll also create a handout that tells the story better than the slides and deliver that, too, but was asked to produce a slide deck, and I think thatโs part of the โeffort theater.โ
Using Beamer for the slides, but not a theme that looks like Beamer because humans have eyes.
Ikea has rules for naming products (so in theory, you could figure out what it is from the name) -> www.ikea.com/โฆ/6f564c4d-2ccc-46de-โฆ545a3948dc79.html
@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:Maybe implementing a subset of Markdown would be a good thing. I am thinking about bold, italics, inline code, and code block, mostly. Oh, and links.
โฆ
replied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:Thatโs a great set (and then no more!)
@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to:I think so. It could even be made a setting, defaulting it to off. I think it would be useful, especially is self-hosted for a tech community.
@stagas๐คธprofilefollow
creative technologist
creator of textlogreplied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:
creative technologist
creator of textlogreplied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:Instead of what to add I'm always asking myself what can be avoided or what can I take out. Adding features is easy. Minimalism is hard.
@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to@stagas๐คธprofilefollowcreative technologist
creator of textlog:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to@stagas๐คธprofilefollowcreative technologist
creator of textlog:I agree that minimalism is hard. Thatโs why the subset was explicitly recommended small. Yet, I believe it is extremely useful to have.
@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerscontinued:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerscontinued:Cool! Letโs test it with a link to Google.
@stagas๐คธprofilefollowcreative technologist
creator of textlogreplied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:
creative technologist
creator of textlogreplied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:I've tested MD and honestly I don't like it. Bold/italics add unnecessary noise/clutter and the font is already monospace, suited for code, so inline code & code fences are not needed. If 3rd party clients want to implement them it's fine but I'm sensitive to visual noise.
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).