I think the difference is that they expect to not break tests most of the time. So most of the time this just saves time.
It’s like when you merge a documentation PR while the tests are still running: You’re pretty sure that the tests won’t break. With this solution however you’ll still be pinged if they do break, later.
If one developer doesn't break it 98% of the time, then for 200 devs you have a chance of .98^200=2% of not breaking it. And for one person trying to quickly get the fix ready while he might have an urgent family situation you have 199 devs who can't get their stuff in, of which at least 20 are under pressure to deploy their fixes quickly themself. It sounds like creating a hard problem for individuals for solving a mediocre problem for the team.
From personal experience, statistical clustering seems to set the narrative.
You don’t even need to hit a 2% success rate to get people agitated. Consecutive failed builds that happen every few weeks will eventually happen when someone really needs to get something out Right Now and that incident will come to define their experience, especially if it happens two or three times. Even if it’s just to people they know instead of themselves.
Anything that happens once a day happens “all the time.” For some people, that’s true for once a week. For others, if it happened twice in two weeks and once every six weeks thereafter.
The dev does have the option of reverting their change.
If significant numbers of devs found the whole process stressful, I wonder if it would help to make the reversion happen automagically after, say, 24 hours, if the dev hasn't committed anything in that time
Devs who have called in sick or over the weekend or attending a wedding or long-planned vacation don't have to think about it.
> The dev does have the option of reverting their change.
Stopping the world seems like an automated process. So should reverting be. In fact, there should be no stopping the world at all, just reverting if the dev can't fix it within 72 hours. There might be cases where automatic reverting doesn't work, but those should still be managed through organizational processes, not by stopping the world.
I'm an unusual American, in that I consider healthy work-life balance to be top priority, at least for everyday employees (founders and such have a different path).
I do try to make room for the idea that my understanding of this is likely superficial, and that there may be things that I am missing, here.
I dont see why this would block other devs merging in their work. And what kind of teams do you work in where you can't politely ask for someone's help when you have to deal with a personal issue?
The whole point of the UI is so that your workflow is simplified without having to understand the exact inner workings of it all.
GHDesktop’s simplicity means that most of time I don’t have to call 4 commands to just check out a new repository or PR because one click runs all those 4 commands and more.
As simple as it is, lately I rarely have to use the CLI (which however I still use because I rebase and fixup)
The fact that “takes you away from the terminology” sounds like people complaining that Windows 95 users don’t know what MKDIR means: That’s the whole point of UIs.
Bad for so many reasons (including abuse of GitHub issues, spam, and the ability to change the URL the short link points to)
If you want your own private shortener, I have a better idea:
Use GitHub Pages and create a `/1/index.html` (where 1 is the short link name) and add a “refresh” meta tag in it. Completely static and no build/JS necessary.
This could be opened up to others by combining it with issues and GitHub Actions, but who wants that?
Another better idea for a private URL shortener is hardcoding a list of URLs in a CloudFlare Worker. Much faster and with real 301 redirects.
Restaurant owner in Italy here: We usually don’t offer pizza at lunchtime because it takes time and wood to fire up the oven and keep it at temperature. Low request volume means it’s not worth it, at least for small pizza places.
If you want pizza for lunch you head to a bakery or “bar” and they have squares (not “slices”) ready for you to pick up.
Technically it’s a family business that I grew up into and I ended up being a developer because at 14 I made the restaurant’s website with Macromedia Fireworks and Dreamweaver.
Is there anyone shipping an ARM motherboard and ARM chip? I think the "openness" is also defined by what the market offers. All I see are non-extendable notebooks.
Also until you can run non-linux "desktop software" on one, it will always feel like a "tablet"
> Is there anyone shipping an ARM motherboard and ARM chip? I think the "openness" is also defined by what the market offers. All I see are non-extendable notebooks.
Pretty much all ARM application processors use soldered BGA packages over sockets, and there also isn't the same tradition of defining a standard pinout for a generation or two (or five) of chips like there has been for x86 (e.g. LGA1151, AM4, etc.).
You can't really design a motherboard without this, so each design tends to have a custom breakout board or carrier card that's designed to be used in relatively specific installations.
> Is there anyone shipping an ARM motherboard and ARM chip? I think the "openness" is also defined by what the market offers. All I see are non-extendable notebooks.
The closest analogue to what you described in the ARM world would be plugging either a Computer-on-Module or System-on-Chip into a carrier board. Today's ARM deployments are presently largely focused on energy efficiency, so they make heavier use of integration than typical x86 deployments.
> Also until you can run non-linux "desktop software" on one, it will always feel like a "tablet"
There are millions of linux users around the world that would challenge your assertion that desktop linux doesn't qualify as anything beyond a tablet. In any event, Windows already runs on ARM and some rapscallions have already got it up and running on a Raspberry Pi despite Microsoft's present prohibition on doing so. I'm sure Microsoft will free up the licensing in due time as market demand presents itself (if only to allow interoperability with M1 Mac VMs).
That’s the issue. Linux runs everywhere and is not a consumer product, that’s why I exclude it.
Until you can build your own general-purpose PC and can decide to make it ARM, it will not be considered an equivalent option, it will just be another tablet, “chromebook” or “board for hackers”
I honestly don't follow you at all. We're now at a point where every major consumer operating system now has an ARM version available.
You can build your own general purpose PC with ARM today. It's not done regularly because ARM chips historically tended to be less powerful, so the type of person that went out and built their own PC wouldn't want to build an ARM PC. This is now rapidly changing given chips like Apple's M1 and the upcoming Arm Cortex-X1 are surpassing their x86 competitors in performance orientated benchmarks.
Once Microsoft gets their act together with their own version of Rosetta 2 and we reach the X2 generation, you'll start to see a rapid shift towards ARM desktops with X1 chips in the mid-tier segment. Eventually the premium "gamer" tier will follow as M1 has proven that it's possible create an ARM SoC that surpasses top tier x86 single threaded performance at a fraction of the power budget and mountains of thermal headroom. This will be accelerated by the fact Nvidia is purchasing ARM and now has massive incentive to get Nvidia discrete graphics cards paired up with ARM SoCs.
I recently had a coworker point out to me a grammatical error I keep repeating, flush vs flesh, that he had reminded me of a year ago.
I recently pointed out to a different coworker some whitespace inconsistency in a pull request in a similar fashion as I had pointed out a while back.
In digging deeper into both situations where I was the reporter or the reportee, the issue came down to legitimate lack of agreement on whether it was indeed a mistake.
Yea, unless you're professional writers, and I don't mean coders, that's not the right kind of things to focus on in pull requests. I mean, if someone happens to be great at code but really terrible at English, like you can't imagine they passed high school grammar, maybe it's a good idea to help them improve. But the average college educated developer writes well enough to write succinct and readable code comments and documentation. Or should be able to.
Even when we learn from a mistake it may still happen in the future. Hopefully we have reduced its frequency but it can still happen.
For example, I sometimes write "too be honest…". I've known it is wrong for decades, but occasionally am still not able to see it. Still happens about one out of every fifth time.
> I recently pointed out to a different coworker some whitespace inconsistency in a pull request in a similar fashion as I had pointed out a while back.
Ask them how you can help them not to make the same mistake again. Not knowing the specific situation makes it hard to offer specific advice, but in software there are specific tools (e.g. IDEs, linters, CIs, tests, etc.) that help people avoid known mistakes. Sometimes having better docs or specific checklist (e.g. "your bug must have these fields filled in before we can work on it") helps.
If that doesn't help, ask the manager the same - emphasizing you are not attacking the person but looking for a way to stop wasting time on correcting the same repeating mistake which adds to costs and decreases productivity. That may generate some resentment (so trying to resolve it directly first is prudent) but if you avoid framing it as a personal fault it would usually help.
The problem to be solved is why the person doesn't learn or change when they know about the mistake, not the mistake itself.
You might start by directly asking, "Why do you keep making this mistake?" It might be because they're careless, or lazy, or maybe they really don't believe it's a mistake (they just acknowledged the mistake to get you to go away). Or maybe they just need a little help, such as automated reminders to get them to check for those mistakes.
Sadly, there are people who will not learn from either kindness and teaching, or harshness and harrassment. In the workplace, you can make an appeal to the manager, but perhaps only after discussion with coworker has failed to produce the desired results.
Do you also feel a general lack of leadership and/or authority? Many things are best resolved by bringing the hammer down, but if no one is qualified to wield it you will be wasting your life trying to protect order from chaos.
