Recent submissions

Comment · 1 year ago
That, and it would be an FBI van, not an NSA van. But the point holds.
Comment · 8 years ago
True in some regards, but it’s also incredibly easy to learn how to do things the wrong way, if you have no one to learn from.
Comment · 8 years ago
Make the changes on a non-active replica database (assuming your database supports replication), then promote the replica to be primary. If you don’t have replicas, the concept of “zero downtime” is really at risk as your primary database becomes a single point of failure.
Comment · 8 years ago
Comment · 9 years ago
You've never been to a grocery store? Avocados are by no means exotic...
Comment · 9 years ago
Dynamodb experienced a severe outage in us-east in September of 2015, dropping the service to three nines of uptime on just the single event. During the incident there was little-to-no knowledge of when service would be restored, so companies that relied on the service were flying blind.

Such an outage can sometimes be mitigated when operations are internal to a company; but with DynamoDB, one has to build internal failover or implement a complex cross-region replication scheme. The complexity and reliability starts to reduce the attractiveness of the hosted service in general.

Comment · 9 years ago
Conpletely agreed; using DynamoDB for primary storage suffers from needing to design data models around the underlying technology. This is true for secondary keys as well, and is even constrained by the odd pricing model that DynamoDB follows.

I've been happy using DynamoDB as a large-scale caching layer, but even that only fits very specific use case criteria.

Comment · 9 years ago
The biggest issue faced with DynamoDB from my perspective has been the problem with any hosted service - that is, the operational stability is in the hands of others entrusted with operating a massive multi-tenant system, and any outage cannot follow your own operational recovery mechanisms unless you plan for failover yourself. And the moment you plan for failover, you need to evaluate why you don't just handle the primary system as well.
Comment · 9 years ago
you should play dwarf fortress.
Comment · 10 years ago
Why would you even ask this? Please don't contribute to the ageism debate. My hunch is the programmer was qualified for the job.
Comment · 10 years ago
Comment · 10 years ago
"Sliding into management" might sound like it's an easy path, but it's an entirely different profession. Only those who are interested and have the ability should ever consider this route.
Comment · 10 years ago
Which means the employee has to realize income tax on the stock immediately under an 81-b or after vesting, correct? That would be an annoying and surprising tax bill, if the employees are mostly familiar with ISOs or NSOs.
Comment · 10 years ago
This is just from angel list. So essentially just early stage startup salary ranges, presumably?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton