At scale though…

That’s a good point. We’ve been using the UML diagrams as a tool to catch behavioral red flags, but the reuse and implementation details of that are left undefined.

Maybe the answer lies in also explicitly spending a few passes focusing on code health, explainability, maintainability (while keeping brain on). This is something I go through at end and then retry verification tests, but not something we explicitly require in our process at the moment.

But in the end you have to know what good looks like and be able to call bullshit. Hmm I guess strong first principles are still the foundation of being good at something, no matter how the tools change. And practice, feedback, and constraint exposure are what turn that into actual effectiveness.

We require you to submit markdown plan before working on a feature, which must have full context, scope, implementation details. Also verification tests mardown file of happy path and critical failure modes that would affect customer, and how tests were performed. Must be checked in with the commit. More complex, large features require UML diagrams of architecture, sequences, etc. to be checked in too.

If your plan or verification docs have wrong context, missing obvious implementation flaws, bad coupling, architecture, interfaces, boundary conditions, missing test cases, etc then PR rejected.

Every developer’s performance is judged as a systems engineer. Thoughtless features without systems docs and continued lack of improvement in your systems thinking gets you PIPed.

So close to 100! Wonder what the Guinness World Record is?

C and python simultaneously.

Not for everyone, but they are aiming at increasing hardware ownership costs so more people can’t afford local AI

OpenAI/Anthropic is incentivized to prevent this.

They are also big enough and unregulated enough that they could use their power & political/industry relationships to drive up the price of local AI ownership (RAM, GPUs, etc)

May go the Gentoo route. majority of my friends use that as their primary os. peer pressure + compiling your OS is fun

Battery life is limited by cell modem drivers being closed source and having to be reverse engineered.

I have been looking into an alternate hybrid radio device using Reticulum. Though with that comes a new less convenient user experience for a lot of apps.

Socialized losses are the norm. People’s energy bills are already paying for the nearby data centers .

The company behind os level age verification is Meta: https://github.com/upper-up/meta-lobbying-and-other-findings

You can use Netbird reverse proxy to connect your domain to any device on your mesh. Netbird cloud supports the reverseproxy too now if you don’t want to self host netbird on a VPS.

You can use Netbird Cloud’s reverseproxy to point your domain to a device on your wireguard mesh.

That way your home server can be under 3x NATs and dynamic IP and you’ll still be fine.

Later if you want to own the netbird you can self host it on a VPS if you’re willing to migrate all devices to your self hosted wireguard mesh.

You mean they’re complying with Meta’s age verification at OS level lobbying?

https://github.com/upper-up/meta-lobbying-and-other-findings

That’s why my side project energy has been focused on making decentralized solutions infrastructure more appliance-like reliability and boring. So app environment on top can have as close to equivalent advantage as centralized solutions.

ZorinOS is nice to Windows users if you want ui similarity

Sounds awesome! No rush, I’m a big believer in taking the time to do it right, not twice.

Just wanted to let you know that I find value in that + feel like it could help adoption especially in the self hosting community.

Would I be able to sign into multiple servers simultaneously? In case I have 2 friends hosting this on their own separate servers?

I care about that more than federation.

I’ve been trying to make sense of why multiple systems end up like this and how to design better. At an individual and small community level there’s decent good people. But once group size or resource pooling goes beyond a certain size more than human attention span, etc then rough edges are blown up.

It’s like small groups can operate on trust and direct feedback but once you get too big then rules and proxies start to dominate. And after that people optimize for those local rules instead of total system health.

Also in small groups you have individuals you tie to systems, but once too big you drop that association in addition to empathy when interacting with the system.

Maybe we need a more modular society focused on local good.