esigler
Joined 18 years ago
Karma
205
Submissions
19
Member since
Mar 30
email: [email protected]
View on Hacker NewsRecent submissions
Comment · 7 years ago
We've been using golinks.io for a few months now at my current employer, and it's been very well received by folks, with both technical and non-technical users adopting it quickly.
Variable links are very useful - links like "go/monitoring/alpha", "go/monitoring/beta" (with a template "go/monitoring/$1 -> $1.example.com"), make it super easy to keep things up to date.
Comment · 8 years ago
Note also there are many other repositories available in https://github.com/openai from various papers & projects, such as https://github.com/openai/baselines.
Comment · 8 years ago
The roles definitely aren't sacrosanct. Teams (& individuals) change and evolve over time, and there's plenty of work to be done. :) Having said that, I might suggest the Fellows program if someone is serious about becoming a researcher - it's a good way to leverage your existing skills while learning how to do AI research.
Comment · 8 years ago
OpenAI | Infrastructure Engineer | San Francisco, CA | ONSITE, FULL-TIME
OpenAI is building safe Artificial General Intelligence (AGI), and ensuring it leads to a good outcome for humans.
The team I'm on is hiring for Infrastructure Engineers to help with things like scaling Kubernetes to 2,500 nodes and beyond: https://blog.openai.com/scaling-kubernetes-to-2500-nodes/
We work in Terraform, Chef, Golang, Ruby, Python, and across the stack as needed. We use existing tools instead of reinventing the wheel when it makes sense, and when we build new tools we often open-source them: https://github.com/openai/kubernetes-ec2-autoscaler
You can find out more at https://openai.com/jobs/, & I'm happy to answer questions via email, ping me at [email protected].
Comment · 10 years ago
We use Serf for infrastructure command propagation ("Chef, go converge on host X", "Docker, start running container Y on host Z") across our entire staging and production sets of hosts, and Consul for holding most of our network topology information across three different geographic regions. Works pretty well. We're bringing in Nomad (edit: and Vault) now, though they still have a few rough spots.
Comment · 10 years ago
We've been using this internally as the integration was developed. Having a message continue to change to show updates is super useful, and is a nice way to avoid spamming a channel with changes / cuts down on the "noise".
Comment · 12 years ago
The testability of Lita plugins via RSpec is super helpful, and it's great to see things like route matching get addressed & improved with this release.