The software defined storage company croit.io announced it in their Workation in May 2023. AI is just another tool and people have to understand that it's not going away. As a company, you still need people to make use of this tool.
Maybe try forcing it to properly plan ahead, break it down into small steps, and ask you to approve the plan.
Of course add a CLAUDE.md, put clear development guidelines into it, let it verify the git changes he did against this guidelines and of course things like a lint.
It will go off rails, especially after compaction, but you can make it correct mistakes on it's own.
I've never really been bothered that much by writing boilerplate. That said, LLMs might be able to completely solve the more complex issues as well and then you'll only be writing code in your free time.
For AI, you want DAOS storage. It runs in userspace, you can use FUSE and it's the fastest storage on the planet when it comes to bandwidth (see io500).
There are good companies supporting it like croit, and with their software it's easy to manage as well.
While DAOS looks cool, from their roadmap it looks like they still don't have a fault domain larger than a server... Their erasure coding profiles also look pretty thin. I'm ex-Meta, our infra had vastly different availability and reliability requirements but that looks like it'd be painful to support at scale.
As a German family, we opted out of the system to gain back freedom as a family. With regular school, you are bound to external schedules like vacation, when you have to get up,...
We learned, that it's around 1 hour per day to achieve what kids learn during most of the day in regular schools. Doing homeschooling therefore is much more efficient time wise.
in addition, we can train our kids to be self and critical thinking, something that does not exist in regular schools.
There are more reasons to consider, but these are our most important factors.
croit | Senior Ceph Engineer | 100% remote | Full or Part-time
croit is the developer of the easiest way to deploy and manage Ceph based scale out storage. To help and support our customers, we are looking for Ceph enthusiasts that want to join our team. Especially if you are an US citizen or if you like to support Sales with clever solutions, please reach out to contact@croit.io
Small objects are very inefficient in s3. Aggregate them together and form bigger log objects is critical to go from a small system log to a real environment.
For me as a user, systemd is far better than old init systems. The logging alone is worth it to switch to it. Add more ram to the embedded board and welcome to the future.
Weird. In my professional life, I've found systemd's logging to be woefully lacking when compared to systems that just run every daemon through syslog (or -even more retro- "each daemon writes stdout & stderr to disk, which then gets sent to your log sink of choice").
What I usually find is that a ton of information never, ever makes it into journalctl, so I always need to go to the actual log files on disk. [0]
On top of that, journalctl just fucking giving up when logs have been rotated is totally bogus. (If this has been fixed, then the fix hasn't made its way to the systems I work with.)
ALSO, have they fixed the issue where minor data corruption just totally fucks your log file to death... rather than what happens with regular log files and you get an unreadable section that's bracketed by good data?
[0] Yes, you could reasonably say "Well, those services are not correctly configured to log to journalctl!". But my point here is that I see this happen so often that journalctl is like my tenth stop for log messages, rather than my first.
reply