Take a look at https://sqliteviz.com/ to do exactly this.

I've a similar background, and have worked recently w/ a handful of teams with atrocious, self-imposed developer experience. I think that applying concepts like SLOs and error budgets to relevant developer-centric activities can really help focus the team and other stakeholders well before the experience passes some threshold of terrible.

This is practically a tenet for me now:

If you tolerate painful problems you are capable of fixing, you're a masochist. If you expect others to tolerate them, you're a sadist.

I often work with people who are more than happy to have someone fix problems. But I also work with people who don't just denigrate such work, but are obstructionist. You're expending energy to stop other people from making the system better. There's something deeply wrong with such people.

> You're expending energy to stop other people from making the system better. There's something deeply wrong with such people.

One explanation is emotional attachment to a system/technology/solution/process they helped put in place. If someone wants to improve it by heavily modifying or God forbid getting rid of it, they will fight back because they feel personally attacked for it. It is wrong, but it happens a lot.

I don't know if it would help or not to mention that the existing system helped to get the company to where it is today, when delivering the "now is the time to get rid of this" pitch.

Acknowledging how long the existing system has been live would hopefully be a reminder that you're not trying to erase their achievement.

It will help, but the receiving party has to be reasonable enough (or "emotionally mature" enough) to fully grasp it. It's usually not the case with people that go nuclear on these topics.

I haven't quite had 'nuclear' but I know what you two are talking about. "But we would have gone out of business 3 years ago if that weren't written!"

Yes. Three years ago. And it's not three years ago.

"What brought you here won't bring you there". As cheap psychology as it might sound, it's actually true most of the times.

> You're expending energy to stop other people from making the system better. There's something deeply wrong with such people.

Lurking somewhere inside everyone is a sublimated death wish.

Which, come to think of it, is exactly how cloud providers manage their free tier.

Same here: we host Maven Central with fastly and are willing to help out any way we can. @sonatype.com

Gmane has NNTP feeds for all their mail list archives: http://gmane.org/features.php

For the winter Olympics, I had a VPS provisioned with a Toronto-based provider: setup Apache w/ a password protected mod_proxy. Voila, I could watch live curling and luge in the office. Total cost was less than $30 USD.

Nothing to say about Hadoop/Java homogeneity, but a Zookeeper alternative I've been looking at for the same reasons is Dozerd from Heroku (https://github.com/ha).

From the linked document, it looks like the bulk of the alleged content is for various adult titles. Who wants to go to go to court for allegedly sharing "Don’t Tell My Wife I A$$ed The Babysitter" (1257 users)?

Given the choice of an publicly embarrassing allegation vs. paying "damages", it is no surprise that so many are settling rather than going to court.

I've been using this last spring, initially as an offline reference when flying, etc. Since then, it's become my primary reference when working with jQuery. It's perfect for what I need: instantly looking up usage details for specific methods.