You’re not tied to ollama. You can choose other options like llama.cpp, vLLM, etc.

shareholder value

And a net positive for billionaires.

Monopoly

Intake feelings nonjudgmentally without inserting your opinion, understanding, or analyzing it so that the other person feels heard.

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

lmfao

Why does the military advertise the most towards the poor?

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

What’s wrong with ollama?

all good. same

acquisition?

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

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.

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 .

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.