I hear you. Centralization without regulation comes with a huge cost. I’m trying to use more decentralized services and self host replacement for all google services gradually. And eventually replace phone with a lora msg and gps device that only has phone capabilities when on wifi.

Simultaneously I’m trying to “Return to monke”. interact less with technology and more with people and nature.

Products are being created for rich people. Poor people are being cut out of the economy.

lmfao

WW3?

Why does the military advertise the most towards the poor?

Surveillance.

There’s nothing more dangerous than someone with nothing to lose. Mass surveillance and authoritarianism is their hope to contain the population they’re about to fuck over even more.

All according to plan

Zorin OS is a good one if you want a nice UI transition from Windows or Mac.

What’s wrong with ollama?

what if you go outside

all good. same

acquisition?

Or LLM cleanroom copy it, like the internet did when claude code source was leaked into other languages like rust

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.