gagejustins

Oh man, this is awesome. I learned a lot from collecting this data and one of the big takeaways for me was how diverse the set of news sources on HN is (to your point, very little "traditional" journalism here). Glad you're doing this!

"I hope you come away with a new appreciation that trade-offs exist, there is no free lunch despite the implementation language or algorithms used. Optimizations exist, but you can’t optimize for everything. In distributed systems you won’t find companies or projects that state that they optimized for CAP in the CAP theorem. Equally, we can’t optimize for high throughput, low latency, low cost, high availability and high durability all at the same time. As system builders we have to choose our trade-offs, that single silver-bullet architecture is still out there, we haven’t found it yet."

There's something highly unnatural feeling about video chat, I think it's very fundamental, and I have a hunch that research will bear this out eventually

I would also add: 1. new SQL entrants: PlanetScale, Cockroach 2. PaaS SQL: Spanner, Aurora

Weird, everything I've read said the contrary, e.g. https://www.nytimes.com/2003/04/23/business/edgar-f-codd-79-...

From what I'm told, they've been pushing it very aggressively to existing customers, and growth has been slowing over the past few quarters. Pretty impressive all in all, given they had to start from scratch fairly recently

This is great, now I can know how much money I'm losing all the time!

Hello everyone, author here. I wrote this post after wondering why Oracle is such a ubiquitous name, but almost no developers I've worked with have ever used it. After some research and conversations with a former employee, it turns out that the story is really interesting: Oracle was basically the first company to commercialize a RDBMS. And today they have what might be the fastest, most performant database at scale – if you're willing to pay for it.

~hello everyone, author here~

I know posts with ThOuGhT LeaDeRshIp titles like this are usually annoying, but I thought it would be interesting to write down some of the lessons I've been gathering as I've spent more time covering and using specific databases. My background is in data science / analytics with a couple of years of more traditional full stack here and there.

Broadly we've seen this pattern with infrastructure in general – it's a lot easier to set up a server than it used to be, all things considered. Now obviously if you're a tiny startup, you're more comfortable outsourcing everything to Heroku, and if you're a hyperscale enterprise, you probably want more control on exactly what your database is doing.

The thesis here is that on the tail end (hyper scale), things are getting more under control and predictable, and developers there want the same "nice things" you get with platforms like Heroku. Elsewhere in the ecosystem, more and more parts of the stack are getting turned into "simple APIs" (Stripe for payments, Twilio for comms, etc.). And perhaps most interestingly, as serverless for compute seems kind of stuck (maybe?), it may be the case that serverless for databases – whatever that ends up meaning – is actually an easier paradigm for application developers to work with.

For a more secure approach, you might find Vantage interesting: https://www.vantage.sh/

this is the nicest thing anyone has ever said about me :)

although all credit for this one goes to Taimur!

Thanks :) here's the link: https://retool.com/blog/salesforce-for-engineers/

Thanks :)

We're just focused on writing content that's interesting to developers, and somewhat related to internal tools :)

Hello! Author here - I had a few friends who worked at Accenture in the past, and always wondered what they do...and why they're worth so much. I dug in (we did the same for Salesforce and SAP previously on HN) and found...some weird stuff. Accenture has a pretty wild story, from being decently early on in computers to a contentious company split, and now to a massive publicly traded consulting firm. Hope you like it!

At DigitalOcean (where I didn't overlap with Ben) we obviously thought a lot about how to improve the DX around interacting with cloud resources, both GUI-based and programmatically. Great to see someone taking that idea to its natural next step :)

This is cool! We used the word "love" a lot at DigitalOcean as one of the key/core values for how we thought about customers and community. Curious - how do you think of blogs and content marketing w.r.t this? Is that a "big marketing effort" or does it fit into community?

Thanks for posting this Joseph! I wrote this post after a few years as a Data Scientist watching other teams struggle to work with the data my team was producing. SQL is probably the easiest "language" to pick up, but being a good data literate teammate takes more than technical chops. Getting good at finding bugs, writing informative tickets, answering your own questions, and optimizing query performance can go a long way!