China and Russia are likely responsible for some of these battlefronts, too.
1,294 karma · joined October 13, 2020
China and Russia are likely responsible for some of these battlefronts, too.
We'd have massive consistency across the software industry and yet that would be an absolutely terrible idea.
Quality is expensive, but lack of quality is also expensive.
Low-quality software causes customer churn, increases implementation time for new features, causes more incidents, negatively affects your reputation, etc.
Moving fast is the right thing sometimes. But overall, quality is the way.
"Number of bugs will drastically increase" is simply wrong.
Type checking prevents bugs before they ship.
One is: how do you effectively manage changes to a codebase over time? Git has a model that, for day-to-day use, has primitives like "commit", "branch", and "tag". You also have to understand the difference between your working copy, what is staged for commit, and any other commit in history. These, in combination with the operations you can do with them is actually somewhat complex. This is the thing I am saying people need to learn. And people quite often complain about it.
The other is the organization of git's porcelain layer, the arguments and flags each subcommand takes, and how stuff is presented back to the user. I think git stands to make significant improvement here. Be that as it may, the tool exists as it is. So your options are to use a different VCS entirely, use a different frontend, or learn how to use git as-is.
If you choose to use git but deliberately avoid learning e.g. what a rebase is and why it's useful, you are choosing to be an ineffective developer. Could it be better in some ways? Yes, but it isn't.
I don't think the car analogy is particularly compelling. The "primitives" of a car are already much simpler than git's. The fundamental primitives of a car are "go faster" and "go slower", along with some supporting things like managing your headlights, windshield defrosting, wipers, and horn.
While additional tools are being added to cars to make them safer (e.g. a backup cam or collision detection), the complexity of those tools is increasing rapidly which makes them more prone to failure. And a driver is absolutely not excused from causing an accident just because one of these safety tools failed. You still have to know how to safely operate your vehicle in a variety of conditions.
They're doing brick-laying work until they aren't. Most problems are easy to solve and don't require very much fussing over. The expertise comes in knowing which problems are worth fussing over and which aren't.
Technology is becoming ever more present in our lives, not less.
Reducing software engineering to a low-skill trade when there is, in fact, mountains of complexity is surefire way for software to be a heap of shit. And in a lot of ways it already is.
Git definitely has some warts but you are right. It is an industry tool for expert, professional use. Some complexity is inherent to the problem of version control.
Learning how to use your tools is part of ANY trade.
Unfortunately a good chunk of the industry doesn't have the discipline to do this.
If you have ever worked in a project where there was discipline around committing, you know there is lots of value in doing so (rebasing becomes easier, you unlock the power of bisect, log is actually useful).
Something being uncomfortable and something being harmful are very different.
I suspect most of the MTG infinite loops are something like "A triggers B, B triggers C, and C triggers A". Asserting that the loop will never resolve is not a violation of the halting problem.
Also, this kind of thing may be a net benefit for DHH. It's publicity. Time will tell.
To address your point, I am not disputing Duke's _right_ to make purchasing decisions for any reason they like.
But it is still stupid and childish. I'm calling that out.
> Why should you care about Duke’s organizational disruption anyway? It’s a private school and you don’t work there.
Because Duke is attempting to normalize toxic behavior. They think this is going to help. It won't.
This behavior might achieve "compliance" but it doesn't actually move the needle. It's why places like San Francisco appear to support underserved communities, but when push comes to shove they blockade housing initiatives.
This is almost certainly some liberal, white woman's way of looking like a good person without having to risk anything. After work it's back to the gated community!
1. people who commit crimes -- even heinous ones -- deserve a second chance and reintegration with society (except, perhaps, for a select few crimes which may not even be especially heinous in the broader context)
2. people who hold unacceptable opinions are irredeemable
Regardless of what you think about DHH's opinions, it strikes me as magnificently childish to cause this kind of organizational disruption because of an opinion. The guy isn't funneling money to Nazi concentration camps. He has an opinion, and it's different from yours. Grow up.
If you make GNU coreutils the first binaries in PATH, you can expect subtle, _very nasty_ issues.
The last one I encountered was `hostname` taking something like 5 seconds to run. Before that, there was some bug with GNU’s stty which I don’t remember the specifics of.
I'm still against this particular rule because it sets a very problematic precedent.
There are other non-problematic ways to hold them accountable. Like fining ISPs for the taxpayer dollars they were given, plus interest.
There is no valid reason to turn this into yet another performative piece of race-bait.
We don't need to play silly "affirmative action" games to keep them accountable.
All software is not life or death. But software can be something people come to rely on.
If I choose (unknowingly) to rely on software not done well and it bites me, I personally would rather not have relied on it at all.
With America's obesity problem, maybe China thought this virus could knock the US down a peg or two.
You may have avoided the silly argument about code formatting. But if that tendency lives in your engineers, they will find another nit to pick somewhere else.
In my opinion this is not a problem best solved by technology.
From my experience this is absolutely not true. Comcast had zero issues intentionally crippling my internet connectivity because the modem I owned only supported DOCSIS 2.
I received letters for months that I needed to upgrade my modem to support a “the best speeds”. Then I didn’t, and my speed dropped to less than a megabit per second.
I could have waived it off as a coincidence, except a couple of months later I was telling the story at a happy hour and it turns out the exact same thing happened to another guy right around the same time.
Comcast does not care if you have a shitty experience. They don’t care if you call. Me not upgrading and calling support about it is just the cost of them doing business.
I take your point. Even so, Steam is leagues ahead of everyone else in this regard. I have Steam games I bought 10 years ago that I can still play on my current desktop PC. That is absolutely not the case with consoles. It isn't even the case for mobile for me, since I switched from Android a few years back.
There is no Steam (let alone any other game store) on iDevices. Just Apple's store.
As a consumer, I don't wanna pay for a game on Apple's store just so I can have a shitty iPhone experience. Especially when nearly every other game I have is on Steam and I can play on whatever device of mine I want.