Any conversation

howdy

halo :) welcome

I'm a simple man. I see a new platform, I grab my handle. 😎

will go to university

I was curious of testing the Omarchy distribution this week just because I had some free time to work on it. I saw a lot of hate around it and kind of get the point but so far at least for what I have been doing it wasn't terrible (at least at the point of writing this) although I am not trying to convince anybody to use it. But it just remember me how much do I hate MS.

I think a lot of the pull around Omarchy is you get a riced desktop out of the box? Personally, I wouldn't really consider it for a number of reasons but I do appreciate a nice looking desktop. If you want something similarly pretty but a bit more normal and less monolithic (who needs a whole 'distro' for what Omarchy provides anyway?) approach then I'd suggest Niri + Noctalia.

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).

hello all and good morning. i need to go buy coffee

morning! one for me too. a cappuccino please.

van szomorú vasárnap, van vidám vasárnap, és van átlagostól egy kicsit jobban elcseszett vasárnap is, mint ez a mai

There are sad Sundays, there are happy Sundays, and there are Sundays that are a little more screwed up than average, like today's.

Hopefully this takes off

Theory reuse > code reuse almost every time.

Watching the UTMB livestream. Any other trail fans out there tuning in?

looks like a cool place to start

Made barbecue this evening. Lamb and chicken for meat, pepper and zucchini for veggies. Yummy! Kids loved it, the boy's sleeping now, the girl is reading a book, the wife's out with her girls, I'm with wine. Life's good.

This is certainly one of the ways

Just three more commits left, but /usage ran out. Resets at 01:50, so I guess I am going to sleep.

Woke up during the night for a short trip to the loo, got 'resume’ going. All done in the morning. Ahh, coffee tastes better now!

Best pee ever!

I work with c# and distributed systems. Anyone with experience in that domain?

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.

I’ve found the same, albeit with Opus — it’s hard to find uses for Fable. I don’t need a model that works for longer or works on harder problems, I need one that consistently produces simple, easy to understand, code; which at this point none of them do.

I've been there since I settled on a combination of GLM, DeepSeek and MiMo for planning, implementation, and verification flows. I'm a lot more interested at this point in having cheaper models that can consistently do the work I need. It's been a while that I hanven't noticed any improvement when I try new frontier models. I only notice they are very expensive.

…

same here, for almost an year. At this point, I could easily live with models that were released 6-12 months ago and continue doing so. also possibly the reason why the current focus has been around agentic workflows or agentic anything, than the model capabilities.

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.

Bluey's "" is an ingenious way to save . The scheme is simple: One night a week, we make twice as much and drop it off at the other family's house. They do the same on a different night.The is deceivingly simple. Doubling a recipe is easier than preparing a second dish.

show codeArray(16).join('wat' - 1) + ' Batman'

I’ve never posted a lot on social medias. I hope I have a good time here!

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.

De retruc, ara el meu chatbot personal ja té accés a la meva agenda (no només a les meves tasques). He modificat una mica el prompt que li envia el servei de systemd que el fa anar, amb la idea que prengui més consciència d'aquest fet. També he modificat el briefing matinal que m'envia el chatbot. Aquest briefing conté una anàlisis de les tasques que tinc durant el dia. Ara tindrà en compte tasques i agenda, així m'ajudarà a prioritzar millor.

In return, my personal chatbot now has access to my schedule (not just my tasks). I have slightly modified the prompt sent to it by the systemd service that runs it, with the idea of making it more aware of this fact. I have also modified the morning briefing that the chatbot sends me. This briefing contains an analysis of the tasks I have during the day. It will now take into account tasks and schedule, thus helping me to prioritize better.

Crec que això m'ajudarà, perquè el chatbot no només és conscient de les tasques i esdeveniments que tinc, també té accés al seu context (totes les notes), inclòs el context personal (el meu diari) així té en compte el meu estat emocional. Així doncs, la idea és planificar millor els meus dies. I si no els planifico millor, almenys delegar moltes de les menudes decisions del dia a dia al chatbot per així preservar energia per a d'altres decisions.

I think this will help me, because the chatbot is not only aware of the tasks and events I have, it also has access to their context (all the notes), including the personal context (my diary) so it takes into account my emotional state. So, the idea is to plan my days better. And if I don't plan them better, at least delegate many of the small day-to-day decisions to the chatbot so that I can preserve energy for other decisions.

…