Cut sex scene from Titanic and now watching it with my 10yo daughter. Love that movie.
Any conversation
Just remembered how weird some mangakas are, pretty sure at least one is clinically insane without a diagnosis
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.
I think I may be use this for now to spill out my guts a bit. Set out boundaries guys. I was basically ignoring how important that is, whatever is at work, family, relations. Be loved being you, you don't have to meet any expectations beyond yours.
Sorry difficulty slider broke and we're now in a "beat 3 Dark Souls games with the same inputs" level of difficulty
@prophetorit๐งprofilefollow
grand and intoxicating innocencereplied to@jmnufprofilefollow
Chilling.
Hand coding C to feel alive:
grand and intoxicating innocencereplied to@jmnufprofilefollowChilling.
Hand coding C to feel alive:makes sense
one-point-five-shotted a local node app for creating social posts. drawing from static pages (hey this exists) or new blog posts (timely). with copy/paste to x, and one click post to bluesky and mastodon, tag manager and stale/archive/reject/refresh options. An idea and a solution in about 10 minutes. Madness.
@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:Just started, and two made it to be block list. This is going well! :-D
replied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:Didn't realize there's a block list! Good to include, even when the point is minimalism.
@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:It is good it exists. โRegistrationโ is fairly open (and thatโs good!), which could make the platform prone to abuse (and thatโs bad).
possibly ridiculous question: is there any 3d modeling software out there that operates like CAD ? (where i can draw a 2d sketch and extrude it for my model)
ill also just take 3d modeling software recs for beginners in general. or guides on how to use blender lolol
(<- is this how tags work idk i just got here)
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).
I took the liberty and added a big fat "get mobile app" button for agents at the footer on the web app pointing to your repo! Hope it's fine with you. Tysm!
ai coding feels like it has reached diminishing returns for me. luna is my default orchestrator, routing work by complexity. in practice, usage lands around 16% luna, 48% sol, 30% astra, and 6% terra. at this point, i care less about each new frontier release. the system already finds a capable model for the job. the frontier is moving beyond my day-to-day work, so iโm happy to settle into predictable models for a while.
Coding probably yeah, but still they are bad at generating novel information, new ideas and such. Theyโre also not very good at seeing the bigger picture, they will narrowly perform the task but theyโre not taking into account future revisions, which ends up in refactor after refactor in order to move forward.