while we wait for this to be true
we could add our bits together
remember to not sleep forever
return when your dreams are through
Start with cringy poem, end with cringy pseudocode. At least it comes naturally.Any conversation
I find myself building bespoke tooling for my own and workflows these days, not only because of the obvious reason of software being so much cheaper to build, but also because there are SO MANY options for solving any given problem that it feels impossible to evaluate all of them.
If it's not a crucial piece of tech for a work problem then it often feels like paving my own way is both cheaper mentally (kind of amazing that's true these days) and probably a better fit.
It will become increasingly harder to find niche markets for software when those people can just build it themselves exactly how they want it. In the end, people want to accomplish tasks, and the AI is going to be building the software on-the-fly exactly for that task, why do we need generic software that may or may not be a fit?
Yeah. It makes me think that protocols for exchanging data between apps will become even more important in that landscape. But maybe, not - maybe each exchange is another bespoke AI-driven implementation?
Protocols, infrastructure, containers, those kinds of things. I was actually playing around with an idea for a minimal markup language + runtime that can be utilized by AI to spin up apps more easily, and brainstorming it with ChatGPT, I have a feeling something like that will appear soon to complement MCP.
@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 interface needs some work. For example, I would like the
textarea that I am using right now to be as wide as the header above. Also, where is the character counter?โฆ
@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:Fixed! The character counter is impossible tho as we don't have any client JS.
didn't want to invite all the bots from day one :P we're if someone wants to implement API authentication and mutation endpoints they are free to try
Sigh. On the heels of , I just went into our garage to find a panel of insulation fallen to the ground, riddled with mouse droppings. ๐คข๐ซ
Cleaned it up (gloved and masked, naturally), but probably means we need to re-insulate the whole garage. Which will undoubtedly uncover a leak or some other issue. The fun never ends!
we also launched Norma! :)
It checks AI-generated code for security, quality and maintainability while the agent is still working, rather than after a pull request opens. The output is deterministic. Here the demo link: portal.qualityclouds.ai/demo
I can't figure out what's leaking on my '73 F250. Shows up slowly at the back of the oil pan. It's pretty clear because I've recently changed fluids and scrubbed the engine.
It was definitely brake fluid for a while after it was overfilled but that has evened out. The oil level is steady after when checking every 10 miles or so.
I think anyway... hard to know with these ๐ฌ
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).
