gtaylor

Fastly has been wonderful to work with. Excellent support, being able to write VCL and deploy it to the edge has been great, and the network is fast and reliable. Also haven't had a Heartbleed type event yet.

I have not seen a strong correlation either way. It's all a game of generalisations and tradeoffs.

This! We may end up back in NC eventually, which has gone both ways in recent memory. Would be happy to try to help restore sanity to what used to be the more moderate of the Carolinas.

It's really easy to let exceptions raise and pass through in languages like Python. In Go you'll typically return and handle errors explicitly. This makes it easier to reason about potential failure modes and behaviors in some cases.

But it is very verbose error handling.

I have the opposite impression of Helm. I'm seeing vendors and other companies cranking out and sharing Charts at a rate I've never seen before.

There are some review issues in the main upstream Helm Chart repo, but that's due to volume (which is now higher than ever).

I can only speak for myself, but I had simply put all of my private stuff over in GitLab instead. For folks like me, this will result in no external change. Just a question of where I stash stuff.

Depending on payment processor and any volume discounts (or lack thereof) it is sometimes not worth getting less than a couple bucks. $5 sounds high as a minimum, though.

I really like how Album sharing works. We've got one that has photos of my kid, with much of the family set up with read/write permissions. At family gatherings they can just add pics they take on their own. Low-hassle and they're happy enough with it to stop bugging me to get back on Facebook.

With the caveat that I'd love to see Scylla succeed, I'm a bit bummed to see the conditions around this bake-off so slanted in Scylla's favor from the start.

Seeing a multi-AZ configuration compared to a single-AZ config is an immediate disqualifier, without getting into some of the other comments on item size disparity and YCSB quirks.

This was a really poor response from Scylla on these fronts: https://news.ycombinator.com/item?id=18677511

This is pretty neat. Would be interested to see aws-cni-vpc in there, too!

I think Calico is only used for network policy on the AWS VPC CNI plugin.

Reddit | Senior Site Reliability Engineer, Infrastructure | SF | Full Time | ONSITE or REMOTE (US-based only)

“The front page of the internet," Reddit brings over 330 million people together each month through their common interests, inviting them to share, vote, comment, and create across thousands of communities.

The Infrastructure team is looking for additional help in building out our internal, Kubernetes-based Infrastructure Product (more here: https://www.slideshare.net/GregoryTaylor11/develop-deploy-an...). This is a great opportunity to come in and help re-define how we develop, deploy, and operate services at one of the world's most trafficked web properties.

We're in particular need of senior-level Site Reliability Engineers. You'll be spending lots of time working with/automating/improving Kubernetes and advising other teams on building high-traffic, highly reliable services.

This position is on-site in SF (re-lo offered) or remote (US only). Happy to answer questions (greg.taylor+hn@reddit.com)!

Apply here: https://grnh.se/93eec9c21

This is correct.

I've been really impressed with the last few years. I still hold on to some little bit of skepticism, but it's shrinking more with every year of their open source + Linux work.

Couldn't disagree more. I am 32, have a kid, a diverse portfolio, and no desire to own a home. We have excellent mobility, I don't have to spend a moment thinking about unexpected housing expenditures, and I got a great deal on rent. I am optimizing for flexibility and am very happy in doing so.

Don't buy a house because you feel like it's what you are supposed to do!

ECS is their entirely custom container orchestrator. EKS is just hosted Kubernetes with AWS integrations.

Sleeping in until 8:30 sounds amazing. Much better than the current 6:00 my toddler prefers.

I really like them for Infrastructure or systems diagrams, too!

You learn a whole lot about each of them in the later books. The first book is a slower start to the series.

If you run a linter, the cases where you are doing this outside of __init__ will usually be pointed out. You can silence the warning/error on a case by case basis if you really need to do it.

Recent versions of libinput are good enough to where I find myself frustrated very rarely these days.

It depends on the email service provider. In general, you're in for a bad time. You can make it work, but you're always going to be fighting black lists and the occasional ESP who blocks your entire provider.

I went the other direction. Bought a Thinkpad due to how amazing they were in the past. Found that the build quality had gone way down. Was pretty disappointed as this expensive piece of hardware developed cracks on the casing within the first year.

Switched to an XPS 15 and have been very happy. Love the build quality, specs are good enough. Battery life is much better even on Linux.

YMMV!

Reddit is constantly out presenting, talking, and even writing about architecture, culture, and our unique challenges.

Netflix seems to be similar. Their open source record speaks for itself, and their technical blog and presence at conferences and meetups is outstanding.

Source: though these opinions are my own, I work on Infrastructure at Reddit.

The answer to that depends on your particular usage case and requirements. There is no simple, always-true response.

PyQt is very good

This is one of a few signals that may suggest ECS may not figure prominently in AWS future strategy.

That is a lot of language swapping. How long of a period did this happen over?

You can fork numpy and maintain Python 2 support.

If anyone over at DO is reading this, we've got some technical and conceptual overlap at Reddit. Would love to compare notes.