I’ve never heard of SeaweedFS, but Ceph cluster storage system has an S3-compatible layer (Object Gateway).
It’s used by CERN to make Petabyte-scale storage capable of ingesting data from particle collider experiments and they're now up to 17 clusters and 74PB which speaks to its production stability. Apparently people use it down to 3-host Proxmox virtualisation clusters, in a similar place as VMware VSAN.
Ceph has been pretty good to us for ~1PB scalable backup storage for many years, except that it’s a non-trivial system administration effort and needs good hardware and networking investment, and my employer wasn't fully backing that commitment. (We’re moving off it to Wasabi for S3 storage). It also leans more towards data integrity than performance, it's great at being massively-parallel and not so rapid at being single thread high-IOPs.
Ceph is a non-starter for me because you cannot have an existing filesystem on the disk. Previously I used GlusterFS on top of ZFS and made heavy use of gluster's async geo-replication feature to keep two storage arrays in sync that were far away over a slow link. This was done after getting fed up with rsync being so slow and always thrashing the disks having to scan many TBs every day.
While there is a geo-replication feature for Ceph, I cannot keep using ZFS at the same time, and gluster is no longer developed, so I'm currently looking for an alternative that would work for my use case if anyone knows of a solution.
> "Ceph is a non-starter for me because you cannot have an existing filesystem on the disk. Previously I used GlusterFS on top of ZFS"
I became a Ceph admin by accident so I wasn't involved in choosing it and I'm not familiar with other things in that space. It's a much larger project than a clustered filesystem; you give it disks and it distributes storage over them, and on top of that you can layer things like the S3 storage layer, its own filesystem (CephFS) or block devices which can be mounted on a Linux server and formatted with a filesystem (including ZFS I guess, but that sounds like a lot of layers).
> "While there is a geo-replication feature for Ceph"
Several; the data cluster layer can do it in two ways (stretch clusters and stretch pools), the block device layer can do it in two ways (journal based and snapshot based), the CephFS filesystem layer can do it with snapshot mirroring, and the S3 object layer can do it with multi-site sync.
I've not used any of them, they all have their trade-offs, and this is the kind of thing I was thinking of when saying it requires more skills and effort. for simple storage requirements, put a traditional SAN, a server with a bunch of disks, or pay a cheap S3 service to deal with it. Only if you have a strong need for scalable clusters, a team with storage/Linux skills, a pressing need to do it yourself, or to use many of its features, would I go in that direction.
I'm not posting to convince people they should use it, just that it's a really cool piece of open source infrastructure that I think is less well known, and I resepect it. It is very configurable and tunable, has a lot of features, command lines, and things to learn, and that does need people with skills and time.
That said, it doesn't need constant management; it's excellent at staying up even while damaged. As long as the cluster has enough free space it will rebuild around any hardware failure without human intervention, it doesn't need hot spares; if you plan it carefully then it has no single point of failure. (The original creator introduces the design choice of 'placement groups' and tradeoffs in this video[1]).
Most of the management time I've spent has been ageing hardware flaking out without actually failing - old disks erroring on read, controllers failing and dropping all the disks temporarily causing tens of seconds of read latency which had knock-on effects, or when we filled it too full and it went read-only. Other management work has been learning my way around it, upgrades, changing the way we use it for different projects, onboarding and offboarding services that use it, all of which will vary with what you actually do with it.
I've spent less time with VMware VSAN, but VSAN does a lot less, it takes your disks and gives you a VMFS datastore and maybe an iSCSI target. There can't be many alternatives which do what Ceph does, and require less skill and effort, and don't involve paying a vendor to manage it for you and give you a web interface?
That's was not my experience. Deploying and configuring ceph was a nightmare due to the mountain of options and considerations, but once it was deployed, ceph is extremely hands-off and resilient.
My experience with plain Claude Code is that I can step back and get an overview of what I'm doing, since I tend to hyperfocus on problems, preventing me from having a simultaneous overview.
It does feel like being a project manager (a role I've partially filled before) having your agency in autopilot, which is still more control than having team members do their thing.
So while it may feel very empowering to be the CEO of your own computer, the question is if it has any CEO-like effect on your work.
Taking it back to Claude Code and feeling like a manager, it certainly does have a real effect for me.
I won't dispute that running a bunch of agents in sync won't give you an extension of that effect.
You're citing the article mid-sentence. The full sentence is:
> Imagine if we could represent our entire organisational structure programmatically instead—not a static picture, but a living, breathing digital representation of our company that can be versioned, queried, tested, and automatically verified.
So yeah, the organisation is living and breathing by virtue of the humans inside of it.
But the representation of its organisational structure refers to a picture of an org chart.
Non-tech people also aspire to have the entire org structure represented digitally.
But in static, proprietary binary formats in file repositories that can only be manually queried.
Our code is already checked into version control and can be programmatically accessed via CI, agents, etc. Our software production environments can already be queried programmatically via APIs. Our issue trackers have hooks that react to support tickets, pull requests, CI. Then there's an airgap where the rest of the org sits with Word documents and pushes digital paper around. Artifacts delivered to customers that must be manually copied, attached, downloaded by hand.
The dream is that modern software development practices would propagate throughout companies.
Oh, the LinkedPocalypse of early 2026. I remember this time fondly as my family huddled around the campfire in the living room as we watched, for a glimpse, all humanity fade and return and fade and return as a broken light bulb that would flicker, not knowing its time was up.
“Why don’t you just watch tv?” you might ask. Can’t. Service update bricked my Samsung TV’s wifi capability.
I think the point is that its believed they were foreigners who were part of iranian proxy forces (e.g. iranian backed militias in iraq), so weren't doing it for money but out of some sort of loyalty to the iranian regime or ideology.
Usually mercenaries mean people doing it for money not ideology who get paid significantly more than your average soldier.
My mom retired as an independent translator 5 years ago.
She worked freelance 40 years from age 25 to age 65.
In the 15 years that preceded her retirement, she would get less and less work.
Partly she's an introvert who relies on her network to provide work, and her network gradually retired.
But machine translation was the big killer.
Before LLMs, the early versions of Google Translate killed paid translation.
As the market adapted to machine translation, and as the internet became a globalised platform for knowledge work, it also opened up to lower grade translation, and there were suddenly many more translators willing to work at a lower wage.
Prior to Google Translate there were semi-automated systems that would fuzzy match from large databases.
But it'd still rely on a human-in-the-loop for adapting the sentences.
With Google Translate you'd get a super sketchy translation out, very crude and not at all correct or idiomatic in the target language. Any distance between the source and target language (e.g. English -> Chinese) and it'd be one big joke. With plain Google Translate it still is. But the market spoke: Probably you don't need a very good translation most of the time. Especially not if the shitty one is free.
In her later years she moved to transcription of board meetings. She'd type up everything that was said.
I work for a company now that automates transcription via the whisper model and generates summaries that can be adapted by the customer. You pay per minute of transcription, and you can regenerate summaries as much as you want after that until your prompts give the right results.
All of this manual labor that provided for my childhood is gone now.
I couldn't imagine being a professional translator today and not use AI extensively.
But unless I have a legal reason to consult with a professional translator, I probably don't even need one, since LLM-based translation is as good as it gets with just plain LLM usage, and near perfect with automated translation tools that will help you pick both the mood, formality and alternative formulations for your translation.
High-grade translation is massively parallelisable, and a human-in-the-loop is entirely for final proof-reading.
I love how terraform can describe what I’ve got. Sort of. Assuming I or my colleagues or my noob customers don’t modify resources on the same account.
I don’t love how unreliable providers are, even for creating resources. Clouds like DigitalOcean will 429 throttle me for making too many plans in a row with only 100+ resources. Sometimes the plan goes through, but the apply fails. Sometimes halfway through.
I’d rather use a cloud-specific API, unless I’m certain of the quality of the specific terraform provider.
I look at the 1990s picture of Brewster Kahle and think: He surely didn't get paid as much as me, but what did I do? Play insignificant roles in various software subscription services, many of which are gone now. And what did he do? Held on to an idea for decades.
The combined value of The Internet Archive -- whether we think just the infrastructure, just the value of the data, or the actual utility value to mankind -- vastly outperforms an individual contributor's at almost every well-paying internet startup. At the simple cost of not getting to pocket that value.
If you think that's fucked up, do you know how little we pay teachers? Especially preschool-K? Clearly money is just a metric for how much moneying the money had been able to money. Goodhart out it another way: "When a measure becomes a target, it ceases to be a good measure.
I was a CS teacher for the past two years, so yes. I did it for quality of life reasons while my son learned to walk. But I almost doubled my salary going back to being a software dev.
Though President Ebrahim Raisi’s sudden death in May 2024 prompted a new electoral cycle with six vetted candidates, all were affiliated with the regime and loyal to Supreme Leader Ayatollah Khamenei, ensuring little real policy divergence. The Guardian Council filtered out all but hardline male clerics and a nominal reformist, creating the illusion of choice while reinforcing conservative dominance. Moreover, the presidency in Iran holds limited authority — ultimate power resides with Khamenei, who, since 1989, has steadily centralized control in his hands, rendering both elected institutions and their leaders largely symbolic. In short, the article contends that no matter who wins, Iran’s domestic and foreign agendas — especially its nuclear program and regional interventions — will remain unchanged, as they are guided by the Supreme Leader's ideology.
There are many reasons why you can have violence in the streets, especially in a climate of enormous foreign manipulation. An enemy state was setting off car bombs just a year ago...
Any recommendation for an in-cluster alternative in production?
Is that SeaweedFS?
reply