georgebashi
Joined 15 years ago
Karma
832
Submissions
72
Member since
Feb 5
Recent submissions
Comment · 3 years ago
Can you provide an example of this issue? This has not been my experience.
Comment · 7 years ago
Yelp | Site Reliability Engineer | San Francisco or London | Onsite | Full time
We’re looking for people with a passion for uptime - people with the tenacity to make meaningful contributions, solve hard problems, and have fun while doing it!
You’ll design monitoring and alerting patterns that keep us stable. You’ll build autoscaling infrastructure to meet our ever-increasing demand. You’ll empower engineers with the tools to safely push code multiple times a day. And you’ll play a key role in keeping Yelp fast, stable and growing.
Apply here: http://bit.ly/yelp-sre or email me with any questions at [email protected]
Comment · 8 years ago
The maximum validity for a cert was recently changed to two years.
Comment · 10 years ago
That doesn't change the fact that sending code to a third party is explicitly disallowed by many employers.
Comment · 11 years ago
Yes, they wrote a blog post about it here: https://blog.cloudflare.com/how-we-extended-cloudflares-perf...
Comment · 11 years ago
I do the same using jrnl (http://maebert.github.io/jrnl), which lets you do things like star, tag, and view entries from specific days - while still keeping everything in a plain text file.
Comment · 12 years ago
Depending on your home country, you should be able to get a temporary passport issued by your embassy here, which would allow you to travel home.
Comment · 12 years ago
Are there alternatives to penlight you'd recommend?
Comment · 12 years ago
Don't worry, there's several!
http://int3.github.io/doppio/about.html https://github.com/nurv/BicaVM https://github.com/YaroslavGaponov/node-jvm
The doppio demo even lets you run javascript-in-java-in-javascript (rhino->doppio->browser)!
Comment · 12 years ago
This is a summary / cheat-sheet for diagnosing performance problems with the "USE" method. It's explained in much more detail here: http://www.brendangregg.com/usemethod.html
Worth checking out the rest of the site too, really useful stuff for performance engineers.
For reference, the definitions are:
* utilization: the average time that the resource was busy servicing work
* saturation: the degree to which the resource has extra work which it can't service, often queued
* errors: the count of error events
[ my public key: https://keybase.io/georgebashi; my proof: https://keybase.io/georgebashi/sigs/mH4h3TOFUhR1_Qbc3IOn2A0_-CMfNEBF7btxb-DD41w ]