cpitman

It's also an unusually expensive airport to fly in and out of (https://www.fayettevilleflyer.com/2011/04/07/nytimes-blog-na...). I was flying for business, like most of the traffic, so everyone is price insensitive.

Introduce features to users as they continue to use the tool. They don't need to know everything as soon as they start using it, and you want to have the ability to introduce new features later on anyways!

I doubt it, it is common practice for us to use personal e-mail addresses for open source contributions (since many of us have pre-existing community involvement before working for Red Hat). And we remain culturally distinct from IBM.

As a side note, really often we get asked to measure our open-source contributions, or get measured by some sort of analysis of a project. It is always an under-estimate because of all the non-redhat.com accounts that we use.

Surprised to hear this is uncommon, I received allergy shots >20 years ago and it was the only allergy treatment (after many attempted medications) that had a sizable impact.

Besides the delivery vehicle, what are the differences between allergy shots and these droplets?

One more use case is that you sometime need to do something, not just specify idempotent configuration. For example, you might have a nightly task to run a script on multiple servers that dumps a data file, then copy those files to a central server.

Ansible can easily be used for both "I need to configure a thing" and also for "I need to script activity".

Reading through their website (https://ansible-semaphore.com/), it seems like it comes down to responsive UI with material design, and being written in Go.

It's not clear what this offers over Ansible AWX (https://github.com/ansible/awx), which is the traditional Ansible UI.

Calling it dog-whistles instead of calling out specific issues with the argument implies that the problem isn't what he is saying, but that he is saying things that sound like things said by other people.

IE, calling it crypto-fascist dog whistles is saying "I think he is a fascist because he says things I think fascists say, but isn't actually coming out and saying fascist things". Which, in the end, means that no one can say things that fascists might also say, without sounding like a fascist.

It seems like calling it a collection of dog whistles is directly addressed by this paragraph:

"The trouble is that Nazis are human beings, and they have many benign thoughts along with their antisemitism. So I might avoid repeating some ordinary, unthreatening statement uttered by someone with a Nazi reputation, lest you think that I sound like a Nazi. Soon only actual Nazis and a few weirdos who don’t care what other people think are willing to repeat these unthreatening statements — which now appear rather threatening. In this regime of self-censorship, even arguments defending academic freedom (which is not a traditional Nazi commitment!) or aesthetic judgment (a commitment shared by many people, including a few Nazis) can look like signs of crypto-Nazism. This increases the costs of honest discussion."

For Enterprise SSO, the market that Okta focuses on, Azure AD is by far the biggest player. They get their foot in the door at companies with Office365, which then makes it a really easy move for companies to consolidate all SSO there. Other responses are commenting on features, but AAD is everywhere.

The only other hosted solution (other than Okta and AAD) I have ever seen at my clients is Ping. In comparison, all the other players are nowhere as nearly established.

It looks like the value of this business unit has dropped though, UPS acquired their LTL operation for $1.2 billion in 2005. Maybe they just about broke even with the operating profit?

This complaint alleges that AWS is shutting down Parler for the benefit of Twitter. That seems like a stretch, does AWS really have an interest in Twitter succeeding above any other social network, especially when both run on AWS?

As already pointed out, these are not the same. Javascript based custom functions in Google Sheets are actually really error prone, meaning that they will just _randomly fail to execute_. Cells will be stuck with a "loading..." message until you trick Sheets into recalculating the value. In the next couple months, I'll likely be ripping out as many custom functions as I can.

And these are not for particularly complicated functions.

I'd really love to have this feature in Sheets. It would simplify a lot of what my sheets do, and also make it more accessible to a Sheets power user that gets scared off from code.

This seems at odds with the multiple open source kubernetes distributions on the market. The problem isn't that Docker is open source infrastructure, the issue was that it remained too low-level as a container daemon, didn't manage to build a large community around swarm, and then were really late to embrace kubernetes.

There easily could have been an alternate history where Docker Inc was the first one out of the gate with an enterprise kubernetes distribution, been a positive part of the community, and been a success.

This rings true. Systems I manage have gone from using fairly complex configuration management scripts that stand up the full stack, to using really basic scripts that create systemd units to run containers.

The important difference between them is not the syntax they are written in, it is their model for how to configure systems.

Ansible is imperative. You give it a list of things to do, and it will do each one, in order, whatever you say.

Puppet is declarative. It runs through your entire script to build a model of how things should be, compares the target system to see how things are different, then uses a combination of implicit and explicit dependencies to order changes and apply them to the machine. Because it is building a model, it is able to detect defects like two different modules trying to configure the same thing two different ways.

The declarative models make it so that doing the right thing is easier then doing the wrong thing (ie, making idempotent configuration is easier then exec'ing out). But the imperative model makes doing everything easier (ie, it doesn't guide me to make idempotent scripts, but makes it super easy to automate any old task list).

That is what makes Ansible easier to adopt, the very low level of mental overhead to understand what it is doing. Conversely, it probably also makes it harder to scale, both because performance is basically single-threaded and synchronous and harder to enforce good standards.

PS I work for Red Hat, but have used both Puppet and Ansible extensively.

Totally fair, anyone in the Microsoft development ecosystem has to learn to be incredibly skeptical of anything new. Anytime I spent on adopting Silverlight was essentially wasted. I had one client that had adopted a random WYSIWYG released by Microsoft to design WCF services, when anyone experienced in the ecosystem knew it had abandonware written all over it.

Of course, other ecosystems have their own versions of this. But Microsoft might be the only one that essentially controls an entire ecosystem and still manages to give devs whiplash.

Isn't that the node-red solution talked about in the article?

There is an in-between option, at least for some use cases: Over time iteratively create a more complete set of constraints/heuristics, use them to generate one or more candidate solutions, and then manually tweak them.

Each round of iteration, look at which missing constraints caused the most manual tweaks, and improve from there.

Sure, but I'm asking if a physical casino could operate without cash out being an incentive? Say you get a certain number of chips for free each day you come, and then you can pay for more chips.

The article is implying though that actually winning money is not required for people to become addicted. It's as if you go to a casino to play slot machines, with no expectation of ever being able to cash out. You just get high in winning and losing chips, with no attached monetary value.

I wonder if an actual casino could get away with that business model.

My experience is that you can often find low hanging fruit, relatively easy changes that will have high impact. For example, I've created checklists for some of the processes that we do often, especially when it involves coordinating with a customer. Creating the initial version maybe required a few hours, but since then has been used 100's of times to shave 1-2 weeks off of work and reduce errors/surprises.

Another example is really basic automation. You probably have people/teams around you that are not developers. They probably are spending time doing really basic repetitive tasks. One team I work with regularly would take a spreadsheet, then for each row create a folder and docs in Google Drive. I wrote them a Google Apps script that could do the task with a click. Not quite as impactful as the checklists, but each script like that saves someone a couple days a year.

Any idea how to preserve the ability for people to go to "their" representative under that model?

FWIW, both of those examples are not only the executives of a university, but also of a hospital system. The vast majority of college presidents make well under that, with a median in 2015 of 300k (https://www.clevelandfed.org/newsroom-and-events/publication...).

Which is why they would never do that. They would instead start with high prices then bring them down, ie you "saved" money.

I assume that was a typo for "Heptio", who were acquired by VMware in 2018.

It looks like the referenced figures are already inflation adjusted and per-capita, so it really is 3x as expensive to educate students today then in 1970.

The article is the one that compared the two, saying that he now makes "more". It is completely correct that you cannot directly compare W2+Benefits to Contractor Revenue. The rule of thumb is to add 50% to a W2 salary to include health insurance and other benefits.

So he is nearly there, but not yet.

That is the last option in the list, in the article.

I grew up wearing shorts while there was snow on the ground, but Cleveland was the first city where I understood why scarves and gloves are a thing. Brutally cold wind.

But on the flipside, their street maintenance was amazing. It was snowing almost all the time during the winter, but the road were always clear.

Isn't Seattle the City Council where even the allegation of someone having worked with or been friends with Republicans becomes an election scandal?

edit: found the article that first brought this up to me (https://www.seattletimes.com/seattle-news/politics/in-seattl...)