brings so many issues. It really accelerates. Not only the good parts but also the bad parts. Combine this with a product person that doesn't even know what a refinement is. I'm 41, maybe I'll study to pivot, maybe I'll get into trading. I can't handle it anymore.
Any conversation
I'm so fed up with the series of tabloid articles claiming Koji was a stand-in actor in koitoki. the 'insider' seems to be part of the staff since they had access to details like the location of the wrap-up party. Idc who they are and how true their information is, the intention is obviously malicious. it's just disappointing that a person like that is blending in with the people my oshi works with, viewing him as nothing more than a subject to sell to trash tabloids.
WezTerm for local and remote multiplexing really is the ideal experience - it's so much better than using zellij, tmux, zmx, and friends.. I don't think they pitch this feature hard enough on their site.
I think the in-terminal multiplexers have their place - e.g. if you need to access from mobile (no WezTerm there) or on machines where you simply don't want to install WezTerm for some reason. WezTermrm could probably eliminate that last one by packaging just the mux server.
prepare for boredom. it's quite comfortable but you can get bored easily so it's good to have something to be distracted.
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to@ossmprofilefollow
:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to@ossmprofilefollow:Enjoy it! I am jealous, really. Let us know how it goes!
@prophetorit๐งprofilefollow
grand and intoxicating innocence
always onlinereplied to@ossmprofilefollow:
grand and intoxicating innocence
always onlinereplied to@ossmprofilefollow:perfect time to sleep.
Nice! Was an opportunity to install F droid also, didnโt know it can be installed like a normal app, I was under the impression it was an OS replacement. This is neat, perhaps we can deploy textlog app there? cc
"If you don't think of yourself years ago as an idiot... Perhaps it is because you still are one."
In that spirit I started to write down my own thoughts. I think I am meant to call it a blog. Years from now I can read my old words and cringe at them.
www.gruntsoft.com/words/
Avui tenia una reuniรณ llarga de moltes hores, d'aquelles en les que una escolta passiva รฉs suficient durant la major part del temps. He aprofitat el temps per implementar una sincronitzaciรณ en dues direccions entre el meu calendari i el meu sistema de notes en markdown (Emacs Howm). He fet el pla amb Argon (tinc pocs tokens al dia amb la subscripciรณ que tinc), amb feedback meu, i desprรฉs Gemini Flash l'ha implementat quasi a la primera.
Today I had a long meeting of many hours, one of those where passive listening is enough for most of the time. I took advantage of the time to implement a two-way synchronization between my calendar and my markdown note system (Emacs Howm). I made the plan with Argon (I have few tokens per day with the subscription I have), with my feedback, and then Gemini Flash implemented it almost on the first try.
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).
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.