Current #jjnotesfollow aliases:
# The canonical tug
tug = ["bookmark", "move", "--from", "closest_bookmark(@-)", "--to", "@-"]
# Show my current work-in-progress(es). To wip it, whip it good.
wips = ["log", "-r", "bookmarks() | description(exact:'')"]
I always associate summer with the months June, July, August โ thinking that end of August is end of summer โ but no, 7th of August is actually summer midpoint, weโre in the middle now, not near the end.
@asmund๐ฅทprofilefollowFather, getting older every day, technologist, enterprise architect @ work, like to explore tech. Like to keep it simple and work in the shell, write in vim, prefer Debian if I have the choice. Plays saxophone and clarinet. Enjoy motorcycle riding, photography, hiking. Christian.wrote:
There are many distractions. Much is way too verbose. A calm, quiet and โdistraction lessโ experience suits me better. I am not sure my thoughts will fit in 280 characters, but letโs try and see how far that goes.
TeXpresso for live latex editing is really impressive!
@carbonwriter๐งprofilefollow(\ (\
( โข โข)
โโชโชโโโโ
Full of mostly true stories, I occasionally write them down. Habit of talking to anyone. Bipolar. Author.wrote:
I love the "feel" of this place. It's minimal, but not too minimal. Nice work! I'm probably gonna be a little chatty on here. If anyone minds that, then just @ me :-) #launchnotesfollow
@carbonwriter๐งprofilefollow(\ (\
( โข โข)
โโชโชโโโโ
Full of mostly true stories, I occasionally write them down. Habit of talking to anyone. Bipolar. Author.continued:
Also, thank you for not turning my emoticons into emoji!! As someone from the pre-internet era, I appreciate that :-)
@procyon๐ฆprofilefollowlate is the hour in which this conjuror chooses to appearreplied to@carbonwriter๐งprofilefollow(\ (\
( โข โข)
โโชโชโโโโ
Full of mostly true stories, I occasionally write them down. Habit of talking to anyone. Bipolar. Author.:
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.
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?
We tought for years that there was a biological ceiling for sprinters or marathon runners for example, with research backing it, but every one record was shattered. I tend to be cautious of biological explanations.
I find myself building bespoke tooling for my own #swdevnotesfollow and #ainotesfollow workflows these days, not only because of the obvious reason of software being so much cheaper to build, but also because there are SO MANY options for solving any given problem that it feels impossible to evaluate all of them.
If it's not a crucial piece of tech for a work problem then it often feels like paving my own way is both cheaper mentally (kind of amazing that's true these days) and probably a better fit.
..then of course I have to contend with - "Is this going to be a maintenance nightmare in the future?" and then I still usually conclude "no, the maintenance will be aided by the same approach that the construction was".
It's interesting how dramatically and quickly the scales have changed in this equation - and for such a wide range of software.
For example, I am looking for a coding agent coordinator with a particular (but not all that insane) set of requirements. I used both Claude and Perplexity to show me options and break them down by fit against my requirements.
I got completely different lists! No overlap!
And no perfect fits.
It will become increasingly harder to find niche markets for software when those people can just build it themselves exactly how they want it. In the end, people want to accomplish tasks, and the AI is going to be building the software on-the-fly exactly for that task, why do we need generic software that may or may not be a fit?
Yeah. It makes me think that protocols for exchanging data between apps will become even more important in that landscape. But maybe, not - maybe each exchange is another bespoke AI-driven implementation?
Protocols, infrastructure, containers, those kinds of things. I was actually playing around with an idea for a minimal markup language + runtime that can be utilized by AI to spin up apps more easily, and brainstorming it with ChatGPT, I have a feeling something like that will appear soon to complement MCP.
At moms house for the holiday weekend so the kids can see Nana. She has a "premium Plex" account on her tv serving a truly massive amount of content. Allegedly the brother of a long time friend is offering the "service". She says that the service will go down when the host is having outages, so the infra is likely local.
I brought my year this weekend. We are going to dig in to this guys operation. Intuition dictates that there is some hand rolled accounting going on. I'd like to see it.
A bit of insomnia this early Tuesday morning. I call it โthe witching hourโ, whatever can go wrong, will go wrong and the brain is defenceless. Reality, of course, is more nuanced, but brain doesnโt care. :)
Makes sense to me, though I think one important (IMO) aspect of this evolutionary role is incurring liabilities. Yes, software can be created by a wider audience, but when things go awry, would they have the aptitude or contingencies in place to recover and take responsibility?
Maintenance of software/systems was a mere after thought in my experience. Adding new things made careers, bonuses etc. so there was no real incentives for maintenance. The article argues that LLMs will do it. I'll believe if and when I see it.
I still remember Max getting sandwiched between the two Ferraris in the first ever wet night race (Singapore 2017). Today he finally managed to win a race there. That's quite a long wait.
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.
#haskellnotesfollow#ainotesfollow
... 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.
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).
Returned after a ride on bikes around the lake with the boy. Did stop for workout, ๐๏ธโโ๏ธ did pull-ups, push-ups and squats. Love the place we live in.