Having worked at a couple of banks, this is absolutely true.
HN user
nickbauman
[ my public key: https://keybase.io/nickbauman; my proof: https://keybase.io/nickbauman/sigs/mCQ2O0KpuJ-VN3cmi3OB2rLgzLSxfahek_1aesTAwNI ]
Comment was not meant to cover Lydia; just generally how money emerged. And this is a "cartoon" version of the story.
Huato doesn't seem to have read the first line of page 22, as Graber actually refutes the claim that money and debt co-emerged. As far as the Cato institute's criticism is concerned, that section is almost entirely free of specificity, unsurprisingly considering how right-wing Cato is in general. All accounts are flawed to some degree, these criticisms you point to are almost entirely ideological or non specific.
David Graber's book "Debt, the first 5,000 years" goes into this in great detail. Highly recommended.
Thanks for posting! Burke uses the term "barter", which is wrong. Before coinage, people used credit. Barter was extremely rare.
Coins (specie that had a direct connection to a ruler, usually with the name or visage of the ruler struck on them) were invented to facilitate war. They were given to soldiers to allow them to participate in the economy of the conquered. Since the free peasantry wouldn't trade with them (unreliable: they "died for a living"). The ruler demanded to be paid taxes in his own coin. This solved several important problems: reduction of military unrest against the ruler, free peasantry became a reliable source of goods and services, and the ruler could make war as needed. A market economy emerged as a side effect.
This is interesting. I sat next to a German manager of DaimlerChrysler (which really dates me, I know) on a flight. He agreed with the idea of worker unions being inside the company and having a seat at the table. He also disliked the practice of building cars "offshore" because, he said "the knowledge of building the car leaves the country".
JSX has an Async "tag"...
Let that sink in.
<Async></Async>
The most radical are Co-Ops. The workers own the company. They're called Worker-Owners. Where management is a skill, not a rank. The problem with this model is three-fold:
• Outside investment can undermine the Co-Op's autonomy (many don't allow it) • Raising capital is hard; usually you're bootstrapping (worker-owners must divert some of their income) • Sometimes worker-owners get caught up in the democratic process of collective decision-making and get frustrated
On the other hand:
• A real Co-Op is real community. They exist to support the humans through work. You're all in this together. You can be "kicked out" by vote, but when you do, you give up your share and all that share money accumulating is yours. • You are "The Man" in the worst and best way you can imagine If something is wrong with the company, you can change it. • No more perverse mgmt incentives.
The biggest Co-Op is the Mondragon. They are very successful, too.
What's the title?
The big German companies invite the unions in because they are a source of innovation too. And managing the connection between the people who actually build the cars and the people who design/plan them is important.
I was just going to say this too: JSX is a DSL. And a particularly screwy one!
I'm sure this has some amazing features that really help with project and personal productivity mgmt compared to other systems.
But let me ask you a question. If I want to get your attention, which one of the following techniques will work best:
1) Write you a snailmail letter 2) Send you an email 3) Send you a text 4) Write it on a yellow post-it note on your refrigerator
The answer is 4. Because it's the most difficult to ignore and leverages our ancient human physiology. It's not an accident that Kent Beck (Author of "Extreme Programming: Embrace Change") used post-it notes stuck to a wall that had every story written on it that mattered to the team within eyesight of every developer.
The problem is that when we get together to put information into a Jira or a Trello or whatever, we're making THE TOOL happy. What matters is the state of the tool, not the state of the system you're working on.
I believe your comment might be a bit too broad for the claims you're making.
Arguably, the most advanced "tech stack" for moving trains around rail systems today (at scale, with the highest safety rating) is based around the Sicas ECC electronic interlocking by Siemens.
However, this article is merely about the technology used for collection of fares for the NYC metro rail system.
I believe this as well. And I happen to know of one of the largest rail systems in North America changes its topology weekly. I'm not sure "throughput over latency" is as much of a mindset as those here who say it is.
This is a perfect example of path-dependent policy. Because the decision was to select for freight, other kinds of rail are "unfeasible". I'm using scare quotes to suggest that it's not really unfeasible, it's a choice.
And since trucking capacity has been maxed out in the US for quite a while (Amazon is the big mover for this situation, even before covid), you can bet this path dependence is biting us now.
No it doesn't have a world class freight rail network. The North American rail infra is incredibly primitive. Most of it is "dark territory" (no track sensors), unlike Europe. I used to write rail automation software for a German firm. They were appalled at the state of affairs here. One of the most lucrative rail systems in the US had an average speed of their trains in the single digits MPH!
Yes; I have a friend who is part of a small team that wrote a very successful stock market trading gateway in Java. Turns out the JVM's GC can be tuned in very specific ways based on your needs. And there are ways to avoid having to do JVM GC in critical areas of the code as well.
I thought the increase in nearsightedness originated in kids not playing outside as much (and thereby not focusing their eyes over longer distances) resulting in eyesight that's more attuned to shorter distances.
Our nuclear storage problem will not change whether or not we build more nuclear power plants or shutter them. The problem will remain "forever" regardless.
So I am for new nuclear power projects because we will need generations of people that can steward the waste regardless. And it's important to keep the ability and technical expertise with these materials for centuries. If the industry is abandoned the risk of a mishandling the waste will increase every year.
Surprised Cloudflare was mentioned so late in the article and almost a footnote. I think that's not representative of its impact of their strategy on the industry.
Wow, using the old Common Gateway Interface, no less!
We still can't read Linear A, the language of Minoan Greece.
I think it's possible with the rise of more and more "successful" dictatorships the Internet will become the domain of the state and we'll probably lose a lot very very quickly.
So... that happening.
Yeah otherwise laws don't mean anything, right? It's free-for-all. From "stopping at a Red light is optional" to Vigilanteism. Can you explain how that would work? Would you want to live in that kind of state?
If you live in a society, you agree to abide by its rules or to move to a different society that better suits you if they will accept you. Otherwise you are a renegade. I don't see how this is avoidable.
A state is considered intact if the government has a monopoly on the legitimate use of force. A state can become predatory if they abuse that legitimacy, but other than that, if the government loses its monopoly, you have what is referred to as a failed state.
The sleep monitor is amazing this doesn't work for me.
Agree on all counts. It's very hard to put time horizons on anything. But I started wearing a Series 3 watch (3 generations old now) when I started a project my client in 2019 insisted I wear it as I was writing code that utilized HealthKit data from the Apple Watch. Check my past posts I'm NOT an Apple fan boi at all. But compared to the competition, there's nothing coming close to the integration and the UX out there. My partner has a Rage 4 and it's just garbage in comparison. It misses and drops, the display is like from the dollar store. HealthKit is absolutely bulletproof. Every single decision in that API is gold. Every time I think something might be poorly done it's my misunderstanding or they made the best choice you can make. Deep respect.
I've never seen documentation efforts pay off in organizations that do not have documentation as a deliverable artifact to outside stakeholders.
I've never used commit comments to store important information about the systems I'm working on. OTOH I can see people working on Linux needing that a lot more than I do.
Feel free to twiddle if that floats your boat though. I will refrain from twiddling, thank you.
Generally, time spent twiddling with the repo is time not spent delivering code. It's a distraction. Yes git has all these features that lets you do that and those feature matter when you're committing to the Linux repo which has thousands of eyes and your commit history has to help you communicate to a very wide audience. But the vast majority of us are not using git like this. I've used git bisect so rarely all this is overkill.