รบgyhogy az idรฉnre beรญgรฉrt informatikai projekjeimet mรกr eleve vaporware-nek nyilvรกnรญtom a kรฉsedelmes indulรกs miatt
so I'm declaring my promised IT projects for this year as vaporware from the start due to the delayed launch
Any conversation
I got an email from battle.net to confirm my age. Apparently some content may be restricted to minors in the region my account is from.
You would think that the account having been created 19 years ago, and with some CD-keys of games from the late 1990's having been added to it would be enough proof, but oh well.
รrdekes ez a 4, 2-es irodalmi, valamint programozรกsi hagyomรกny, amire Douglas Adams hรญvta fel a figyelmet, nรกlam ebbลl a hagyomรกnybรณl 4 a pszichiรกtriai, 2 a rehabilitรกciรณs tรฉma, ami รฉrdekes mรณdon maga is 4, 2-es, ami olyan, mintha rekurzรญv kezdene lenni, de mรฉgsem az teljesen www.textlog.hu/a-4-adel-es-2-szuzett/
This 4, 2 literary and programming tradition, which Douglas Adams drew attention to, is interesting. In my case, 4 of this tradition are psychiatric and 2 are rehabilitation topics, which is interestingly itself a 4, 2, which seems to be starting to be recursive, but it is not completely www.textlog.hu/a-4-adel-es-2-szuzett/
azรฉrt aranyos, hogy egybลl sandbox-ba kell tenni (a Virtualbox egy sandbox), hogy szรฉt ne barmoljon mindent a gรฉpen vagy a szerveren, vagy mรกshol, azรฉrt alapvetลen bรฉkรฉs kis รกllatkรกk ezek az ai chatbotok, na
It's cute because you have to put it in a sandbox right away (Virtualbox is a sandbox) so it doesn't mess up everything on the machine or the server or anywhere else, but these AI chatbots are basically peaceful little animals, right?
I'm Nobody! Who are you?
Are you - Nobody - too?
Then there's a pair of us!
Dont tell! they'd banish us - you know!
How dreary - to be - Somebody!
How public - like a Frog -
To tell your name - the livelong June -
To an admiring Bog!
I gotta confess, I vibe codet a Kirigami-based application and I liked it. I am a anti AI person, and cannot wait for the bubble to burst. Yet I see it can empower people that do not know a tech stack, and get good enough results out of it. However i also see, it makes you lazy (and frustrates as soon as it gets somewhat complicated). It seems it is being adopted everywhere. This is scary... if it becomes necessary, will you be able to find a job where they don't require you to use AI?
@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:Hmm, I think @stagasprofilefollow
creative technologist
creator of textlog is on vacation, or otherwise engaged with other affairs...
creative technologist
creator of textlog is on vacation, or otherwise engaged with other affairs...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).