totally

Yes, but there's another dimension here. If another team breaks your build in a monolithic repo, you may or may not be able to resolve this quickly. You're in a contract with them about the state of the repo and thus your service.

With microservices, the production version of their service would conceivably be stable. It moves the contract from the repo to the state of production services.

I understand that a thing is worth what someone will pay for it, but to balance that out a bit, no conversation about compensation is complete without consideration of actual needs.

When colleagues, whose compensation is as wildly out of proportion to their needs as mine is, complain that they're entitled to more, it's at best a negotiating stance and at worst a black hole of insatiable greed.

Obviously this is some game theory mojo, and we'll never get everyone on board with it, but imagine for a second a world where everyone isn't vying for "more", but for "enough".

In the zero sum game we have here, compensation becomes a moral issue.

If you're into this, you might also like:

Inviting Disaster: Lessons From the Edge of Technology: https://www.amazon.com/gp/product/0066620821

Daily (manual) biker here (~70 miles per week).

These ebikes are a clever hack. In China they skirt motorcycle laws. In the US they can make use of bike paths. You can make good time and your commute is generally the same duration regardless of traffic. At least, that's true in Silicon Valley.

Last I checked (a few years ago) pedaling the ebikes is like pedaling a tank. Batteries and motors a heavy bike make. So you're using the motor and there's not a lot of cardio happening.

I ride my bike because I want to live longer/better. I don't think you get that with these, but there's definitely a niche for them.

> January 7, 2014

This is years old. Am I missing why this is newly relevant?

What's with all the backslashes?

So HA only updates when chef runs (every 15 mins or so)? And when nodes are deleted, I guess something else has to clean them from chef? You'll also have to add these hosts to monitoring config.

I implemented something similar with puppet/mcollective/SQS years back. Poor man's service discovery. Here are some other options that, if you can handle the complexity of running Zookeper (or similar), are probably a bit cleaner:

http://jasonwilder.com/blog/2014/02/04/service-discovery-in-...

> And there's no need to list off software. I'm not sure it's possible to be in this site's target demographic and not know who he is.

Taking opportunity to clarify what we're talking about is just good communication.

> However, in this instance a previously-unseen software bug was triggered, and instead of retaining the previous known good configuration, the management software instead removed all GCE IP blocks from the new configuration

> Crucially however, a second software bug in the management software did not propagate the canary step’s conclusion back to the push process

I'm sure the devil is in the details, but generally speaking, these are 2 instances of critical code that gets exercised infrequently, which is a good place for bugs to hide.

Wait, this isn't new.

Hm, maybe fracking should be subject to EPA regulation and disclose the chemicals used in the process afterall.

relevant:

https://codeascraft.com/2012/05/22/blameless-postmortems/

> Because we have experience mitigating DDoS attacks, our response procedure is now habit and we are pleased we could act quickly and confidently without distracting other efforts to resolve the incident.

The thing that fixed the last problem doesn't always fix the current problem.

Do they still exclude all 3rd party binaries?

David Byrne has a book where he rides a bicycle around cities around the world and makes similar observations.

http://www.davidbyrne.com/archive/art/books/bicycle_diaries/

"Not once have I regretted spending unbounded amounts of time investigating something fishy"

While I agree with the gist here (heed warning signs, proactively preempt failure), there are literally hundreds of "fishy" things, many/most of them low impact, that I could investigate on a given day, and my time is bounded.

At the semi-formal dance of distributed systems, meandering investigation should be chaperoned by ruthless prioritization.

"all of them have" ... "in my experience". I posit that you don't have experience with everyone who's lost money on kickstarter and uttered that particular phrase. And not knowing the sample size of your experience, I don't really trust your opinion on people, except that some are oblivious and some are jerks. Some are. People's oblivion does not stun me anymore. I don't expect drivers to stay on the road. People do things that are terrible for their health, and can generally be counted on to make objectively bad decisions, especially my mother. But the thing is, if you get all the human souls in a room, and get them to guess how much a mountain weighs, the mean average is consistently closer than any individual guess. So I guess some people's idiocy is a counterbalance to the wise people. I hope I've filled your heart with hope just a little bit.

Must one be a "self-righteous jerk" to say "I don't even expect to get anything when I back a project!" ?