Viewing profile — diggs

I did, and the fixation on React’s age struck me. Was it the core premise? No. Was it a central theme? Yes.

I don’t care that React isn’t new or innovative anymore, that’s a good thing in my book. Give me old and boring any day.

An infinite timeout works in theory, but it is impractical at scale.

Every time this topic comes up, it seems people invariably divide into one of two groups. In the first group are those who trust in the odds and play the probability game. In the o…

A use case that I wish authorization service providers would talk more about is support for "list" queries e.g. What resources of type foo can the user read? In really simple cases…

This is a misleading and dangerous service. You provide a distributed lease, not a lock. A distributed lease by itself doesn’t provide mutual exclusion. Distributed leases are typi…

There's so much more to CI/CD than the build definitions (e.g. dashboarding, log viewing/retention, access control, manual interventions, secret management, test reporting, etc.) a…

I had a little chuckle at this. One day you will too :)

I am yet to work on a team with a simple, reliable and repeatable build process. Most build processes (from basic scripts or Makefiles all the way up to CI/CD product-specific pipe…

Agreed - I’ve spent months working on a deep tech problem before I could even show a functional core, let alone putting it into production. Some problems take time, experience and …

Recognition and trust have never been a problem for me. Have you hired at this level before, or merely assuming? As always there is nuance, as other commenters have touched on.

“Someone that avoids talking about what they did, and focuses too much on "we"” This is very interesting. I naturally use “we” when discussing past products and achievements. I do …

My first experience with event sourcing was having a new hire at a previous company try to shill it. It was a smaller company and he had previously built a career consulting on ES.…

Object tags instead of named resources look like a neat and flexible concept, and is something I hadn't considered before. It is quite jarring transitioning from the filesystem exa…

The beauty isn't in the UX of the API per se, it's in the reduction of historically complex file system APIs down to a simple set of primitives and behaviours that enable massive t…

There's also no deduplication with client-side encryption.

Deleting a bucket in an object store is surprisingly non-trivial. See Amazon’s UI - it works fine for small object counts but is very buggy for larger buckets.

I recommend using a static site generator and hosting on S3. It's the cheapest way to do it and will survive a hacker news storm. It's also easily managed in version control and ze…

Sorry, I should have perhaps put a disclaimer in my original comment. I work for a company called StorReduce and built our replication feature* (an intelligent, continuous "sync" e…

That depends on how you're storing the files. I was really just trying to highlight that for deduplication across files you need to deduplicate before you encrypt.

This approach works well enough for relatively small amounts of objects. Once you start getting in to the millions (and significantly higher) then it begins to break down. Every "s…

How about if a single byte changes? Now the encrypted output looks 100% unique, and you have to treat it as an entirely new file. You lose the ability to do diffs on a file by file…

When flying, so quite a bit for me, actually :)

Our server software is typically deployed as close to the source data as possible. This lets us move only deduplicated data over the WAN. It also supports our encryption model wher…