Throwing heavy circles over my head is the most fun i have each day.
Any conversation
I have a toddler.
I come home from work, cook, feed, clean, wash up. We read stories and play. I put him to bed.
Then I put something on the television and my wife and I scroll on our phones until she goes to bed.
I am not so careless with the little free time I have.
I continue to scroll until about 1 am.
The next morning I do it again.
On the weekends, I get to drink wine.
i always have to resist dream futures that are way out of my league. no, Orit no! you can't be a priest your a girl!!!! noo!!! you can't be a cardinal either, stop!!
Hi all, this is my first introduction to textlog, stumbled upon it whilst browsing Fdroid.
What do you like to do on here?
Ordered JBL Charge 6, waiting for delivery today. Will mount into my bike and will listen to music while commuting 25km to the office. I'm a victim of marketing, seeing an ad, buying stuff.
I'm doing experiments with short attention-span students and code. Starting with python, and, oddly, now working in BASIC. As a C programmer of 40+ years, I find this aesthetically and pedagogically displeasing, but I am delighted to see them getting fully absorbed in writing
130 PRINT "You have been eaten by a bear!" : GOTO 900. Yes there is spaghetti, but it's their spaghetti and they seem to take delight in debugging it. Python will come later. "for you" now contains the same message multiple times
โฆ
added two more screenshots to - the "root" post view is incorrect, but when reply-on-reply, information goes up-then-down.
root post view IS correct, sorry.
I understand your confusion, but that's the formatting - quoted parent is below the child post - then that post's replies follow in the discussion view. The top post is always quoting its parent below it, the different bg makes it distinct. Just need to get used to it, same on X.
There really is no other way to include the parent otherwise, you have to break the hierarchy at some point, the other form would need to omit the parent body and show a 'parent' link but we want to include its body.
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).