This is a good point and imo there is an interesting tension between adaptability and specialization.
Stable environments naturally drive populations towards more specialized actors in niches as they benefit from efficiency. Think of leverage in the financial economy or the dinosaurs.
When a big system disruption inevitably arrives, you better hope you still have some depth around with adaptable general populations that can survive the crisis and occupy the new environment. Think of Minsky moments and the K-Pg event for the dinosaurs 66 million years ago.
Another example would be stem cells vs organs and their specialized cell types.
It seems to me like you need enough regular change to avoid overspecialization and preserve the ability to survive large changes.
This is how future codebases will be analysed. Don't let perfect be the enemy of good. Evolution been doing Agile for aeons. Responding to change over following a plan ...
Ah; but how annoying it is to discover something like the inverted retina bug, only to figure out it is effectively unsolvable now due to all the follow-up architecture decisions built on it?
If you already have a version of GnuPG installed, you can simply
verify the supplied signature. For example to verify the signature
of the file gnupg-2.5.19.tar.bz2 you would use this command:
gpg --verify gnupg-2.5.19.tar.bz2.sig gnupg-2.5.19.tar.bz2
This checks whether the signature file matches the source file.
You should see a message indicating that the signature is good and
made by one or more of the release signing keys. Make sure that
this is a valid key, either by matching the shown fingerprint
against a trustworthy list of valid release signing keys or by
checking that the key has been signed by trustworthy other keys.
See the end of this mail for information on the signing keys.
* If you are not able to use an existing version of GnuPG, you have
to verify the SHA-1 checksum. On Unix systems the command to do
this is either "sha1sum" or "shasum". Assuming you downloaded the
file gnupg-2.5.19.tar.bz2, you run the command like this:
Another aspect which was too long for me to type on my phone earlier is that debt/Schuld is backward looking while liability/Pflicht is forward looking.
So while debt is incurred through past actions, what matters from an operational business perspective is your liability, i.e. your obligation for future payments/value transfers.
In english speaking business practice, debt and liability seemt to be used interchangeably. I have never used German in a professional setting and am only familiar with the colloquial usage of Schuld and Pflicht so I would be interested to hear how those differences play out in German business use.
In plural form "Schulden" is exclusively used for debt. The more common term for liability is "Haftung" which also translates to accountability (GmbH for an LLC means Gesellschaft mit beschraenkter Haftung). The singular "Schuld" can also mean guilt, blame or fault. But they are all pretty negative in their connotation.
The prevailing theory is that Anthropic doesn't have sufficient compute capacity to support Mythos at scale, which is the real reason it hasn't released.
This looks very cool! My concern is just that it's a lot of things bundled in one and I kind of have to trust you for all of them. I would prefer something that puts together a stack of better known components, like a docker compose of agent-sandbox and tailscale or something equivalent, etc ... ideally with each of those swappable.
Stable environments naturally drive populations towards more specialized actors in niches as they benefit from efficiency. Think of leverage in the financial economy or the dinosaurs.
When a big system disruption inevitably arrives, you better hope you still have some depth around with adaptable general populations that can survive the crisis and occupy the new environment. Think of Minsky moments and the K-Pg event for the dinosaurs 66 million years ago.
Another example would be stem cells vs organs and their specialized cell types.
It seems to me like you need enough regular change to avoid overspecialization and preserve the ability to survive large changes.
reply