diggs

6 ms·

1.
by diggs 3y ago
I did, and the fixation on React’s age struck me. Was it the core premise? No. Was it a central theme? Yes.
2.
by diggs 3y ago
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.
3.
by diggs 3y ago
An infinite timeout works in theory, but it is impractical at scale.
4.
by diggs 3y ago
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 other, those who demand absolute guarantees. Neither group se
5.
by diggs 4y ago
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 you may model this as a one-shot check on a logic
6.
by diggs 4y ago
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 typically accompanied with a fencing token (which your service c
7.
by diggs 4y ago
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.) and while some of your points resonate very st
8.
by diggs 5y ago
I had a little chuckle at this. One day you will too :)
9.
by diggs 5y ago
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 pipeline configurations) are complex, brittle, opaque and p
10.
by diggs 5y ago
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 foresight to solve and the solution only dovetails at the en
11.
by diggs 5y ago
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.
12.
by diggs 5y ago
“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 this in recognition of the fact that things are ve
13.
by diggs 5y ago
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. Every problem we had he would come up with an argument for
14.
by diggs 5y ago
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 example to the introduction of tags though, as something q
15.
by diggs 7y ago
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 throughput and scale while still being broadly appl
16.
by diggs 9y ago
There's also no deduplication with client-side encryption.
17.
by diggs 9y ago
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.
18.
by diggs 9y ago
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 zero maintenance. For extra points you could add a C
19.
by diggs 10y ago
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" effectively). We currently have a patent pending fo
20.
by diggs 10y ago
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.
21.
by diggs 10y ago
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 "sync" operation has to start from scratch, comparin
22.
by diggs 10y ago
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 basis or proper deduplication across all files.
23.
by diggs 11y ago
When flying, so quite a bit for me, actually :)
24.
by diggs 11y ago
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 where we encrypt using a pluggable key management service e.g. A
25.
by diggs 11y ago
If you're open to using something proprietary and commercially supported then depending on your scale you should check out http://storreduce.com . We're a growing startup in this space. We do real-time compression, encr
26.
by diggs 12y ago
What a coincidence, I found myself writing a little Go lib for exponential back off yesterday, and was wondering what the purpose of introducing jitter was and what effects it would have. I need it for interacting with the Twitter stream ap
27.
Go-eval – eval()for Go, kinda(programmingtipsandtricks.com)
1 points by diggs 12y ago|0 comments
28.
Evaluate Go code at runtime(programmingtipsandtricks.com)
1 points by diggs 12y ago|0 comments