Yello folks!
Any conversation
What's your Minecraft skin?
โฆ
really? (โ โโ _โ โโ ) I just saw it before and felt like it described me sometimes (โ โขโ ย โ โฝโ ย โ โขโ ;โ ) what game is he from!??!
or show, or any other media,,
That's so funny, I've never seen anyone get into it by this quote alone, he's the antagonist of the game The Elder Scrolls III: Morrowind.
The quote is even better when you hear it in context, but don't spoil the experience, you ought to play the game and hear it for yourself.
What do you normally play?
Today I wanted to share some Music from my youth :)
www.youtube.com/watch?v=8Hn-pNxtByM
When I read about in reputable , I relate to almost everything that is described (keeping in mind that no two autistic people are alike). However, I always read the sections on with bewilderment. I don't identify either with the obsessive need to make eye contact, which UK and US books often mention as behavior, or with the difficulties in making it.
Unless I am attracted to the person I almost never maintain eye contact while talking to them. Iโm from Greece btw, doing eye contact is normal, I see others do it, so I diverge there.
โฆ
Definitely people here do intense full locked eye contact, which I canโt do, unless Iโm attracted to the person as I said. Even then Iโll move a bit around the face because itโs uncomfortable even then. But others just lock in completely I see them doing it.
OK. I guess that Greece may be similar to Spain. I feel comfortable hanging with greeks, in Greece and elswhere. Then, if I don't look at the eyes, but others do. I guess that I'm very good at masking that I don't look at the eyes. I never got a comment related to eye contact.
I donโt think itโs something people notice immediately and consciously think this is wrong to make a comment, they will probably just not feel the same connection or feel something is off about you in general or think that youโre busy thinking other things. Itโs not the only case to not make eye contact with someone, you might just not like them. Thatโs probably what they will sense.
Any users around?
I have been customizing it to the way I work, as it is meant to be. Bent it in a way that I enjoy holding it, so to say.
Maybe someone will find those useful, so I took the time to get it published.
Gruntfooot is a footer customization, where you can try new colors/glyphs in real time and also has theme support.
But maybe we'd all be a little saner if we remembered what we're actually doing: building tools to make our lives and the lives of others easier.
This resonated a lot. Iโm glad I read it now, before going totally insane lol. But I disagree that itโs just a glorified spreadsheet. The UI/UX matters, how you present the data, how they can change and so on, all of those things play a role. The good thing with AI is iteration is cheaper than ever, so you can experiment and process the results quickly. But yeah sometimes I just do things here because I just have to be doing something, I canโt leave it alone.
Agreed. The "just" makes the statement sound dismissive, but I do agree with the underlying sentiment that most software boils down to CRUD apps that help people organize information and complete tasks more efficiently. I think the path to developer enlightenment is realizing this truth without despairing over it.
New in agenttop.dev : panels open in your . ๐คนโโ๏ธ
โข Any panel can now split into its own pane, live, beside the table.
โข Works with all the popular multiplexers: , , ๐ฎ๐ป๐ฑ ๐ธ๐ถ๐๐๐.
โข run a panel on its own: agent-top mcp, agent-top slow, agent-top fails, agent-top advice.
โ The # MCP panel also lists the orphaned MCP processes that outlived their agent and are still eating memory.
we also launched Norma! :)
It checks AI-generated code for security, quality and maintainability while the agent is still working, rather than after a pull request opens. The output is deterministic. Here the demo link: portal.qualityclouds.ai/demo
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).