14,997 karma · joined May 16, 2012
A more interesting graph would be to show me the 30 year return at each point along the way. My gues is that stocks would still mostly come out on top, but not the runaway you see here.
I say that as a manager of narcissistic assholes who are always “brutally honest” and feel that their honesty excuses their brutality.
I guess they’ve that rule.
No one to day learns that anymore. The vast, vast majority have no idea and I don’t think people are dumber because of it.
That is to say, I think it’s not cut-and-dried. I agree you need to learn something, but something’s it’s okay use a tool.
It lacks a moral component.
And disgorge your profits, pay a fine, go to jail and agree never to work in the securities industry ever again.
After one of the trashed my app in Cursor, and I pounded on my keyboard "WHY WOULD YOU DO THAT!!!" and the model, ignoring my rage and frustration, responded with a list of 4 bullet points explaining why in fact it did make those changes.
As a software development manager, I find the most important quality I need in my direct reports is honesty. If you are not honest with me it makes it very difficult to do my job.
That some developers have been conditioned to dishonesty is a shame on our industry.
As a former Republican, and a Reagan conservative the utter cowardice and corruption of the Republican party nauseates me. No principles, no ethics.
As a professor I had once put it, "This is difficult material. I don't expect you to understand it from just one lecture. You need to read the material before the lecture, but it will only be after you've struggled with the problem sets that I would expect you to understand it."
Some subjects are conducive to the Socratic method but hard sciences and mathematics for instance are not. Ultimately you are trying to speedrun 500 years or so of discovery and research and while motivating problems often help, sometimes you just need to read the book, listen to the lectures and put in some effort.
And Java devs on a Scala codebase is effectively the norm once your project enters BAU/maintenance phase.
The classic "I'll write my own csv parser - how hard can it be?"
Garbage in, as they say...
In 2006, GIMP had a ton of features, but compared to Photoshop’s UI it was positively awful.
I think the productivity was in some part driven by minimum wage laws. At lower wages, developing, installing and maintaining ordering kiosks and smart phone ordering apps makes less sense, because fast food cashiers are so cheap. When fast food cashiers become more expensive (and the technology costs come down) kiosks and apps make more sense. The same amount of food sold without the cost of cashiers is the resultant increase in productivity.
So my theory in a nutshell was that cashiers added little value. Substituting capital for labor led to labor productivity gains.
https://en.m.wikipedia.org/wiki/Benford's_law
“The discovery of Benford's law goes back to 1881, when the Canadian-American astronomer Simon Newcomb noticed that in logarithm tables the earlier pages (that started with 1) were much more worn than the other pages.”
We were told in an off-hand way that logs could be to any base, even ‘e’, but not to worry about that for a few years.
Studying birds gave us some data, but mimicking them wasn’t what got us jumbo jets.