in .
Any conversation
I have developed a beautiful free app that lays out Instagram feed photos as a perfect masonry grid every time, no matter which photos you provide it. It's completely free to use if anyone wants to check it out
Very cool! At least the landing page is amazing! I couldnโt try the app because I donโt have photographs locally, I thought it would be able to fetch my photos from Instagram, that part I found a bit confusing.
It's to create the post FOR Instagram, so does need to pull from your photos on a device ๐
Ok I see! Curious wouldnโt that be a good paid plugin for WP or standalone?
Tweaking the algorithm. Really want posts like i.e genuinely long discussions, stay longer instead of getting burried away by newer posts.
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.
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).
It didnโt work out, we found competition offering the same service for free so the fell apart. Need to find something else to do as a side project to textlog. ๐ Thinking of a code editor thatโs focused on the new agentic workflows, so you have it on the side regardless of your agent tools and it monitors the git diff and offers a nice panorama view. Iโve done an extension for VSCode similar to this idea.