Preparing for opening up an app I'm working on for a public beta. Main is a quiet app that helps you maintain the value of your home:
Any conversation
โฆ
Yes the og is downloaded and re-served, to avoid leaking/tracking of client information. You need to edit and save to refetch, I did it for you now.
I've been building a Markdown variant called Zd that's focused on extensibility and simplicity. I'm curious what you would change about Markdown if you were designing it from scratch, what challenges you face as a user, or what you wish were easier to do when incorporating Markdown into your own projects.
Definitely tables are cumbersome.
Yeah, 100%. That is completely something I am punting on currently. It would be easy to just copy over the solution from (extensions to) Markdown, but it's hard to entirely narrow in on both what tables ought to do and how to make them do it.
If you had a magic wand, what would you have them be more like?
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).
@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:Productive weekend started four hours ago for me (at 06:00 EDT). Visited aunties and mum. Just got home, and waiting for wife to finish preparing to get on the road again. Next destination: nursing home (visit family, and โadoptedโ elders).
I have something that usually builds, tests, and deploys under five minutes. It has been over two hours and forty eight minutes and it is still going on today... ๐ซฃ
Whatโs the difference between a script-kiddy and a real ? Abstraction. You can program your whole life without learning how to meaningfully abstract problems into simpler pieces that TRULY make the problem easier to understand.
Iโm not talking about design patterns or vs . These tools can help. But to really simplify something for others, you need an intellectual empathy that many simply never figure out.
