I love the idea of taking well understood analog concepts and applying them to the digital remote workplace, but man, forced sync calls coming in on a whim without my control to ignore them sounds like my absolute worst nightmare.
If you haven't already, take a look at the section "Solving Distraction: Presence + Statuses + Calendar" in the article - I dive into our attempt to solve this problem.
Do you think our solution is insufficient? If so, any ideas on how we could further solve it?
I think having to clutter my work calendar with "I'm working" entries is a pretty clumsy way of signaling that I don't want people to randomly speak over Beethoven in my headphones. I my company introduced this, I would invariably "forget" to start the software at all, or would leave it on DND status permanently.
Personally I just don't see the benefit over a chat message saying "time for a quick call about <topic>? <zoom link>".
If I have the choice, I will not be starting any project with them in the future after the crap they pulled with CircleCI 2.0.
"We're introducing this new, 2.0, version. It has some benefits, but is also missing a lot of features and bug ridden. It's easier for us though, so you're going to have to waste a couple days converting from 1.0 to 2.0."
My feelings as well. What we really need is a ansible script or a docker file, which would build a Jenkins instance which everyone could use. You would of course need different tools for various build setup and technologies, but CircleCI is far from point and click anyway. I really which I would spend all the time I wasted on their config to build the above. This way everyone could run 5000$/mo of CircleCI on a 50$/mo bare metal.
You might want to try Azure Pipelines. It uses a dual model of Microsoft-hosted build agents running several OSes including macOS, and self-hosted build agents running on infrastructure of your choosing. The team I lead uses for Windows-, Linux-, and macOS-based builds, Microsoft-hosted and self-hosted build agents.
If I finally decide to pull the plug I will probably invest time to build my own setup around OS tooling. Main benefits would be much lower price and independence from lock in. And it's not like one has to build their own solution here. There are tools available.
This is a lot of upfront work, and signing up for continuous maintenance, computing costs, dealing with vendor-specific oddities, and a host of other concerns. Whatever is gained from this (being able to sign AWS phobic clients) must be substantial.
There are some large companies that don't want to run on Amazon, so they are probably trying to court that business... but I'm surprised they went with Azure instead of Google.
I don't have to speculate, that's definitely why they went to Azure:
Retail clients have pushed Snowflake Computing to make its software available on Microsoft’s (NASDAQ:MSFT) Azure cloud.
Snowflake CEO Bob Muglia (a Microsoft vet) says that a number of retail customers “particularly a large one based in Arkansas” have “a fairly strong opinion” about the Azure availability.
The Arkansas reference is likely to Walmart, which prefers not to use competitor Amazon’s cloud.
For me, endurance racing (WEC) is quite a bit more fascinating and impressive than F1. Racing a car on the cutting edge of race technology for 2 hours is one thing, but 24 hours is a whole different ballgame.
The other thing that WEC has that Formula 1 doesn't is the chaos and excitement caused by multiple classes of car competing at the same time. It's not just a matter of negotiating your car around all the other cars that are pretty much identical to yours. You have to negotiate around cars that are both slower and faster. Dealing with traffic is a major aspect of WEC, and it's something that's entirely lacking from F1.
If you like the chaos and excitement of WEC you should come on over to WRC. $5/month for 3-hours of live streaming HD content per Rally, including full on-board cams for every major driver and stage:
I mean c'mon, Kris Meeke with an accidental exit into a car park with just a few corners to go while leading Rally Mexico. You can't get much more exciting than that!
Absolutely. I mean, could you imagine F1 drivers having to negotiate the track with the 911s, Astons & Corvettes? They'd throw a damn hissy fit.
Not only does it make the race exciting from logistics/entertainment perspective, but at any given time there are multiple first place battles occurring. It's hugely entertaining.
It's not that anyone has forgotten, it's that a lot of people never learned how to in the first place. Every programmer community is riddled with these problems but the NPM world seems to be the worst. The ruby gem "american_date" annoys me to no end. It's just a highly-specific implementation of Time#strptime. Gah
True. I would like to have used a nice JS library or something so you could drill down better. Putting numbers on the charts would have been nice to get a sense of the actual sizes (especially on the ones with very small slivers.) Will keep this in mind for next time!
