this will be the platform that fixes me
Any conversation
For 30 years, productivity sky-rocketed with the advancement of automation and computing. Meanwhile, a decline in longevity was observed, correlated to sleep depravation. Productivity improvement goes to the owners class' pockets, sleep benefits the workers health.
For 30 years, productivity skyrocketed through automation, yet longevity plummeted as a direct result of sleep deprivation. While these gains accrue to the owner class, sleep remains an undervalued element of the worker's health. We are trading life expectancy for chump change.
i was under the impression life expectancy has been steadily increasing over the last century, where are these quotes from? and which date?
โฆ
That said, in Canada working class started loosing life expentancy for the 3rd year in a row, and WHO figures show a decline in improvement of life expentancy globally. But hey, I am just a no-one on the internet spewing bs :)
a decline in the improvement of life expectancy isn't the same as a decline in life expectancy, it's just that it's improving less fast now, we might be reaching biological limits however?
You look in the corner, you see a guy quietly eating cigarette butts. It's ok. He's dealing with a lot of stress from work. He takes care of his family. Capitalism
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to:Likewise... you look in the corner, you see a guy quietly eating cigarette butts. It's ok. He's dealing with a lot of stress for lack of work, or food, or future. He wants to take care of his family. Communism.
We havenโt figured out yet. Maybe we never will.
Itโs using the
/firehose endpoint. Itโs an SSE endpoint publishing everything latest. Though I meant it to be used server-side, since itโs heavily rate-limited โ up to 3 conns under the same network, but I canโt control how clients decide to use it so.. ยฏ\_(ใ)_/ยฏOne idea that I've been thinking about is an or where it is a app so you get a new file everyday right except the app keeps track of all the files for you. the idea is that anytime you type anything it it basically makes a commit and use so anytime you type something it commits automatically after a quick pause after you stop typing.
That sounds ! Could also create summary titles with for the filenames in addition to their date so you can find what you were writing about easily. Also full text search.
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).