I’m worried that they put co-pilot in Excel

There are, however, definitely domains it can excel: things like entry-level call handlers... I think they're screwed in all honesty!

Edit: clarified some stuff...

It started out as, "AI can make more errors than a human. Therefore, it is not useful to humans." Which I disagreed with.

But now it seems like the argument is, "AI is not useful to humans because its output is non-deterministic?" Is that an accurate representation of what you're saying?

Think of it this way - an IDE can tell you what functions an object has or autocomplete something is useful to a beginner & learning. But that's not what puts food on the programmers table - writing code that solves real problems does.

Same in excel business use cases - the numbers and formulas don't matter directly - their meaning in a business context does. And that connection can be very tenuous. With code the compiler is the ultimate arbiter - it has to make sense on that level. Excel files it's all freestyle - it could be anything from your grandmas shopping list to a model that runs half a bank.

That being said, it's clear that in the current system, rich people can get richer faster than poor people.

We have a two class system a) workers who get paid per unit of work b) owners who capture any surplus income, who decide hiring/firing/salaries, who can sell the company and whose wealth keeps increasing (assuming the company does well) whether they do any work themselves.

Note: I see very few things which have inherent value - natural resources (plus land?) and human time. Everything else (with monetary value) is built from natural resources using human time.

---

If a company starts with 1 guy in a shed, he does 100% of the work, owns 100% of the company and ... it gets muddy here ... gets 100% of the income / decides where 100% of the revenue goes - if it's a grocery shop he can just pocket any surplus, if he's making stuff, he'll probably reinvest into better tooling or to hire more workers.

A year later, he hires 9 workers. Now he does only 10% but still owns 100% of the company.[0]

There's a couple issues here:

- He owns 100% of the future value of the company despite being created only 10% by him. Well, not exactly, he was creating 100% for the first year and 10% from then on.

- He still gets to decide who gets paid what. He has more information when negotiating.

- He can sell the company to whoever and the workers have no say in it. He can pass it on to his children (who performed 0 work there) when he dies.

The solution I'd like to see tested is ownership being automatically and periodically (each month) redistributed according to the amount and skill level of work performed.[1]

So at the end of year 2, the original founder has done 2 man-years of work, while the other 9 people have done 1 man-year of work each. This means the founder owns 2/11ths of the company while everyone else owns 1/11th. This could further be skewed by skill levels. I am sure starting and running a company for a year takes more skill than doing only some tasks. OTOH there are specialized tasks which only very few people can perform and the founder is not one of them.

The skill level involved would be part of the negotiations about compensation.

---

This is complex. I am sure somebody is prone to rejecting it based solely on that. But open a wiki page about e.g. bonds[2] and see how many blue words just the initial sentence has and ask yourself whether you could explain all of them (and then transitively all the linked concepts on their wiki pages).

Slavery is very simple but very unfair. Employment is more complex and less unfair. I have a theory that the more fair a system is, the more complex it is because it needs to capture more nuances of the real world.

---

[0]: Some people think this is right because owners take all the risk and employees take 0 risk. That is misrepresenting what really happens - sane investors/owners don't risk losing so much they would go homeless/starve if they lose it all. They can also optimize their risk by spreading it across many companies. Meanwhile workers get 100% of their income from one company and drop down to no income if the company goes bankrupt. They can also be fired at any time.

This was argued here: https://news.ycombinator.com/item?id=45731811 in the comment by kristov and the reply by me. I also have other comments there with relevant ideas.

[1]: What happens to monetary compensation? I don't know, I see multiple options:

a) Everybody gets paid monetary wages like today, plus (newly) a part of their reward is the growing share of the company they own. If we allow selling it to anyone, it has high monetary value but then ownership gets diluted to outside investors. If we allow selling it only back to the company, it has value only relative to the decision-making power it gave. If we don't allow selling it, its monetary value only comes from the ability to vote on dividends.

b) Everybody gets paid a portion of the income divided according to their share. This sounds simple but likely wouldn't give enough money to newly joined workers to survive. There could be a floor. (Or, because hard cutoffs suck, a smooth mathematical function from owned percentage to monthly compensation which would have a floor at minimum wage.)

[2]: https://en.wikipedia.org/wiki/Bond_(finance)

A confident statement that's trivial to disprove. I use claude code to build and deploy services on my NAS. I can ask it to spin up a new container on my subdomain and make it available internal only or also available externally. It knows it has access to my Cloudflare API key. It knows I am running rootless podman and my file storage convention. It will create the DNS records for a cloudflared tunnel or just setup DNS on my pihole for internal only resolution. It will check to make sure podman launched the container and it will then try to make an HTTP request to the site to verify that it is up. It will reach for network tools to test both the public and private interfaces. It will check the podman logs for any errors or warnings. If it detects errors, it will attempt to resolve them and is typically successful for the types of services I'm hosting.

Instructions like: "Setup Jellyfin in a container on the NAS and integrate it with the rest of the *arr stack. I'd like it to be available internally and externally on watch..com" have worked extremely well for me. It delivers working and integrated services reliably and does check to see that what it deployed is working all without my explicit prompting.