No time spent creating new branches for new features.
No time spent switching between branches to address feedback.
I'm sorry but these are non-issues with git. The approach you've outlined makes collaboration on features impossible. Cherry-picking and rebasing does not scale for either teams, or lots of parallel workstreams.
Really? I mean, I get you want to recommend an infrastructure as code tool, but I really wouldn't consider it in the category of "[features] which you almost never need to consider alternatives."
The screams during turbulence are one of my highlights when flying. Doesn't happen very often these days unfortunately... 20 years ago flying used to be like going on a theme park ride.
The purpose of the battery isn’t to power the entire state for 15 minutes.
It can respond to market demand within milliseconds, and after coming online was responsible for dropping the average wholesale price of electricity by 90%.
> Eight years ago Japanese tourism was near 100% domestic.
Nope, calling bull on this. Not by a long shot. Japan has been a major international tourist destination, particularly in the winter for at least 20 years.
I asked donuts (gTLD owner of .family) whether my domain renewal could be reduced (from $385 per year to something more reasonable for a genealogy hobby). This was their response.
Maybe it’s not worth reading too much into the “we can’t change the renewal cost” line.
—-
Hi Nick,
Unfortunately, we can't change the renewal cost for santamaria.family
If we ever start to change renewals, I will be sure to reach out to help.
90% of our population lives within 100km of the coast between Melbourne and Cairns.
However agricultural usage extends far inland in the temperate regions and there has been a lot of opposition to mining activities in our “wheat belts”.
In my experience on the hiring side of the equation, recruiters often _demand_ a reason why an applicant was rejected. I'd prefer to diplomatically say they were a poor culture fit rather than explain that they were conceited, had poor english skills, or seemed high maintenance.
The fact that php.module ever existed in the codebase is a downright travesty. As soon as any privileged user was compromised (i.e. someone with "administer users" or "administer site configuration" permissions) the attacker had arbitrary remote code execution.
My projects had a patch to remove that entire module from core on each build.
The sad reality is that our government thinks only in timespans less than an election cycle. Any large-scale national infrastructure project is basically a non-starter now, the Liberals trashed the NBN and they will trash anything else that threatens their neo-conservative ideology.
I'm sorry but these are non-issues with git. The approach you've outlined makes collaboration on features impossible. Cherry-picking and rebasing does not scale for either teams, or lots of parallel workstreams.