241 karma · joined December 9, 2013
Doing so however carries a lot of risk and one needs to have a certain mentality to be able to actually do it (I certainly don't have that).
1. Cache of file attributes in the Kernel (this is controlled by "stat-cache-ttl" value - https://github.com/GoogleCloudPlatform/gcsfuse/blob/7dc5c7ff...) 2. Cache of directory listings 3. Cache of file contents
It should be possible to use (2) and (3) for a better performance but might need changes to the underlying fuse library they use to expose those options.
And you can consider using gVisor to minimize container breakouts to a great extent.
> “Honestly, I didn’t see them. I think that was divine intervention, moving those wires away from me,” he said.
If you read the article, he explains the reasoning.
I wasn't trying to spread FUD. I did state that the arrests weren't because of the drug.
Of course this is impossible to do in fixed formats like PDF, but 4 years back I specifically worked in Kindle content to make PDF books reflowable :)
1. Your build pipeline has a lot of hermetic actions.
2. To speed it up, you execute these actions remotely on isolated environments, cache the results and reuse when possible.
Pretty neat.
You might want to look into https://goo.gl/TB49ED and https://console.cloud.google.com/marketplace/details/google/... if you need a managed service to do just that.
This is a popular sentiment, but its not "for free". There's cost involved in storing, transcoding and service videos to millions/billions of users and in the development of those technologies.
Shopify, Uber used to be at the top of the list.
So instead, I usually try to setup the dev stack and walk through multiple use cases of the product, usually narrowed down to the area I would be working on. I would make sure my stack is so that I can iterate really really fast (I've a few quirks that I tend to use like weird aliases etc etc) and all this while also simultaneously working on small/minor bug fixes. I do this for atleast 3-4 weeks atleast, then I get a feel for the code and where things are. After that, I personally feel confident enough to take on bigger projects on that codebase.
Has worked out well for 3 large codebases at 3 different companies so far.
I know a couple of friends who work there and they frequently mention having access to raw email contents with minimal supervision. That's now how I want my email to be treated by the company hosting my email services.