collinf

Yeah it's a total hog of attention. At the company I just left, you could walk through our office and 90% of people were just talking on Slack. What a waste of engineering time.

We were pretty invested in ChatOps which I thought was great. Being able to issue commands in any sort of war room situation with a group of people was definitely helpful for that sort of triaging. Of course, the downside being that depending on Slack to be up to do effective operations isn't super appealing to me.

Of course people have been doing this with IRC forever, but Slack is a definite improvement on this front over Skype.

It sort of bothers me that the kubeadm logo is just the K8s logo wrapped in the React logo.

That said, I’m a big fan of the improvements to the CRD’s. That was a pain point in the past.

> These interposing network elements, called middleboxes, often unwittingly disallow changes to TCP headers and behavior, even if the server and the client are both willing.

There is nothing worse than finding out that someone not even at the company anymore decided years before to deploy some crap like this. Drives me absolutely crazy to impose stuff like this where silos in companies means transitioning involves on the order of 4-5 different "components" need to change.

"A Manhattan is a Screwdriver but you replace orange juice with bitters, replace vodka with sweet vermouth, and add whiskey."

Can't wait to explain this one to my bartender tonight!

This is anecdotal, but I used to work at a large (Fortune 500) financial company. The CEO had no engineering experience, but every year they would do an annual summit of the goals of the company. Over 50% of the talk every year, they would drill down pretty deep into technical topics, I was always amazed that at that level he actually knew enough to be able to describe complex data engineering topics and machine learning models. Even if it was rehearsed, I always came off the talks super impressed with their ability to talk at that detail.

Also, Bezos was a Computer Science major and a developer for 4 years after graduation.

Another point I recently heard, and I can't recall the exact quote off my head but it was along the lines of: "Amazon at this point is really just a cloud company that is using it's cloud earnings to subsidize its other business arms to grow to a big enough scale where it can choke out all other competitors."

I still have that on iOS? Never noticed it going away and it’s still there for me. That feature really did take way too long for me to realize although.

Docker has a multitude of benefits for single machine multitenant deployment strategy, namely resource and file system isolation.

It also has the benefit of being self documenting of dependencies via layers, which is a nice thing to have. To be honest, running just about anything self-hosted can be deemed overkill when there are so many free hosted solutions. But that’s why we’re engineers because sometimes it just scratches an itch for us :)

In the article they said that both regions consumed writes and got into an inconsistent state during the process.

> This effort was challenging because by this point the West Coast database cluster had ingested writes from our application tier for nearly 40 minutes. Additionally, there were the several seconds of writes that existed in the East Coast cluster that had not been replicated to the West Coast and prevented replication of new writes back to the East Coast.

I would have to imagine that they have a huge market share of Developer laptops. Unless they are willing to jeopardize all of that or integrate developer first productivity into a tablet which nobody has done yet, MacOS will stay.

Freakonomics did a Podcast on this if anyone wants a pretty good listen. I listened and couldn't stop thinking about all of the applications to software in it.

freakonomics.com/podcast/in-praise-of-maintenance/