It is not the thing in Japan. Japanese corporations are primarily sustained to continue existing, not to return shareholder value. They are very good at that.
Returning shareholder value wasn’t even a thing in America until 1970s. Corporations were originally formed to limit liability in the 1600s. I can’t say that is better or worse. There is a lot of novel approaches that come from this, but the idea of returning shareholder value that was sold to us by hedge funds, private equity, and vulture capital also drives enshittification. Even now, there is no legal obligation to return shareholder value.
Why would investors invest, if a company declares that it has no interest in returning shareholder value? I'm sure that many people do get a kick from supporting companies that they believe in, but generally investment is not done for purely altruistic reasons.
Ironically the case that established this principle is one where the investor was trying to purposefully sabotage the company from expanding into the market as they also owned a competitor (Dodge v Ford). So actually this “return shareholder value” was used precisely to put Ford into a straight jacket in terms of expansion while the Dodge brothers grew their business.
Nothing forces a company to cede control of its values to venture capitalists or to go public. And I suspect there’s a lot of private companies that own their destiny and are making moral choices at the cost of revenue.
The legality is an irrelevant distraction. The shareholders have a voice with, if nothing else, their money.
It feels like people are surprised that a public corporation is seeking to do whatever makes people believe it’s worth more. The people who buy or sell are voting on how they believe the company ought to be behaving.
I have been finding I spend more time writing when working with AI. While I do let it generate docs, it does not always do a great job and I end up reorganizing, reframing, or changing vocabulary. Those passes end up require rigorous thinking.
There has been some occasions where I cannot use AI as a thinking partner. It doesn’t have the imagination, intuition, or judgement. I have been relying more on my team in those cases.
This article reminds me of another method: grabbing paper and pencil and start doodling around to work out some ideas.
One of the things I ask AI to help edit my writing is a consistency pass, making sure my ideas hang together well. The real test is to see if other humans understand it.
I tell mine that line editing and formatting are the very last polish.
I think Rodney Brooke’s three laws of robotics apply here, particularly how the appearance of the bot promises its capabilities. It might have better for an obviously automated response to come back. No one might be listening but would not have been promising human empathy while faking human attention.
LLMs tends towards closed-worlds and bias towards decidability. Risk assessment is terrible, as are creating opportunities — no animal instincts to draw from.
Despite having this in the training data, I am constantly having to remind my coding agents to reason and design with grammars. On the other hand, once all of that is settled, and the task is no longer open-ended, then they are very good at driving towards completion.
Crafting the automation itself can be fun. That is one of my favorite part of designing systems running on Kubernetes.
I have also come to the conclusion that, right now, AIs lack imagination. So designing human-AI collaboration that lets human imagination in the loop would be interesting.
If we’re going by water, land, etc as an argument against wasteful activities … Coming from the permaculture world, I can tell you just how wasteful the pre-AI world is. The ideas in the mainstream environmental-friendly practices are themselves very wasteful.
Code as documentation works better when the code is declarative or a DSL. These capture intent and promises (as in promise theory) better.
When it is not, it has to be reasoned out and does not work well for documentation.
Other things that code and tests alone do not capture well:
- promises (as in Promise Theory) made to other parties. Claude already has PT in its training data.
- Constraints-inducing-properites, as in Roy Fielding / Christopher Alexander. While tests, and property testing can capture properties, there is no formal connection to the constraints that induces fhem. By constraints, I am not talking about business requirements and business value — those are better understood through Promise Theory. I am talking about things like at-least-once delivery or total ordering (from append-only constraint). Claude already has Fielding’s dissertation and Alexander’s works and ideas in its training data.
- grammars, as in pattern panguages (not just patterns) a la Alexander / Fielding are also not captured in code alone. These tell both humans ans AI how to extend a pattern, and how to identify anti-patterns (when they violate a constraint-inducing-property)
- LLMs are trained with many different worldviews and bounded contexts at the same time, and is very capable of translating across it. However, these need to be soelled out, otherwise it would talk in whatever it infers
Specifications written for the exact way components are wited together run into that stale doc problem. Although it takes much more human attention and token burn to describe things in terms of pattern language and promise theory, it becomes easier over time. The actual implementation plan tends to fall out more cleanly when all those other stuff are at least considered. This is where I have been spending most of my time.
reply