1,033 karma · joined October 3, 2020
I now ask exactly how management attributes time for bug fixes. If they aren't allocated to the person, team, and story point for the original feature, then I explain to them my story and why I won't work for them.
I am sure that some people really need these massive frameworks with build chains and universal rendering. I am just not one of them. I use JS for small logic here and there, mostly form validation and a bit of dynamic content. Most web software I know fits this description. I don't know why, but web developers are obsessed with making their jobs seem more complex than it really is. It's like everyone is scared that if someone realizes they just used HTML, JS, CSS, and a small set of scripts that people would find out they weren't real programmers.
Worse is that people envision scientists as unbiased saints. That's just not real. Real science is about one thing and one thing only. Money, aka grants. Grants get you labs and underlings which bring more money and maybe someday tenure. And once you have tenure, you can finally publish what you really think about what interests you instead of chasing funding fads. Except that part never happens.
That means you study the subjects that give funding. You give papers that increase the chance of more funding for more papers. Your accuracy? Doesn't matter. Funding matters. No one is going to check your work anyhow beyond simple peer review. Someone tries to recreate your work or recalculate your numbers? Tell them you lost the data. It's a bit embarrassing but no one is going to call you on this stuff anyhow.
There is only one solution to the replication crisis. Funded third-party replication for all experiments. Money is the root of this problem. It has to be the solution. How many scientists are going to publish "mistakes" if they know that four different teams at four other universities are going to automatically attempt replication?
As for the collusion, I might believe you if this were the first time. After all, it was such an enormous, public incident. But it is not the first time and it will not be the last time either.
There was only one problem with Java. Even on new machines, you would get noticeable random pauses doing simple things. This never happened in C++ apps even with full MFC bloat. The GC just wasn't that good yet. Programmers would also include FAR more code and libraries because it sped development up. Even today, C++ applications only include libraries if they absolutely have to because of how painful it is.
All of C++'s disadvantages become advantages when you look at them from the lens of performance. Manual memory management means that even if you are slow, you are consistently slow. You don't get the peaks and valleys that really irritate humans who are incredibly sensitive to rhythm. Memory leaks are honestly not even a problem unless you have long running servers. Even then, you could honestly just restart. The near-complete lack of standard libraries and complete lack of a package system highly reduced the amount of fluff you had. If you wanted it in your software, you had to do it yourself. This led to very simple, non-pretty, static interface that just tried to look like Word without the Toolbar of Death. The best optimization has always been to Do Less Stuff.
It's only going to get worse too. The same companies who think C++ is too complex for their programmers are going to laugh at Rust. People in Java or .NET shops aren't going to move over. "Native" is increasingly becoming a JavaScript space which has all the terrible performance of JavaScript usually combined with the slowness of internet connections. For good and ill, package management is now standard.
Microsoft Office used to run fast on a 486 with megabytes of ram. Think about that. Are you a more complex or intensive program than Word? I bet that ePCR has far higher specs. The program running on it isn't inherently more complex. It's literally a form filler, but it isn't used because of how ridiculously bloated even the most basic software has become. In the 90's, you could have made that machine by installing Windows on a machine and programming a VB program in a few weeks that hooked up to a printer. It would have been more responsive than a state-of-the-art ePCR that sits unused today.
It takes a level of maturity that most people never reach to handle real diversity of opinions. This is why universities used to be small places with only highly interested intellectuals trained to handle that diversity. And even they weren't great at it. Modern universities are a joke, and they are better than most organizations.
This is why you can't have second-class citizens like this. They are terrified to go for help if they even know how. It's even worse for undocumented workers. At least they can quit though. H1B workers are tied to their sponsors, which has to stop.
I think Linus's handling of the Linux kernel is an excellent example of stellar technical leadership in a parallel track. It is what technical companies should look like. Engineers do their thing without worrying about administrative tasks like HR bullshit, salary negotiations, hiring, firing, and fights over who makes the coffee.
What scares me is how ingrained in every SV company this is now. Nearly every company monopolizing some corner of my Internet life continuously spouts this rhetoric in terror. It makes me wonder what they are afraid of.
"If you don't like X, then start your own." I watched Hatreon get shut down by Visa and probably every other processor. Is their name stupid? Yes, but that's not the point. I would bet you dollars to donuts they worked ten times harder than Patreon to comply with US laws and regulations. They knew they were going to be under a microscope. It didn't matter one bit.
Everyday, the Internet and the companies who sit on it are becoming more central to our lives. We are already close to an informal Social Credit System in the US. How long will it be until watching the wrong politician's speech on YouTube means you can't get a mortgage? Can't get a middle class job? Is that where we want to be? It's not where I want to be. It's not where the vast majority wants to be, and it's scaring us.