
#RevTWIL: A Week’s Worth of Slack Sharing
At Revelry, we believe in sharing and learning from one another (beliefs that are rooted in our Core Values). Among the many things we…
GitHub content on the Revelry Blog: Navigate our lab notes by using the tag system.
At Revelry, we believe in sharing and learning from one another (beliefs that are rooted in our Core Values). Among the many things we…
A Guide to Getting Off the Island When you’re stuck at a computer, in a room by yourself, on a problem you can’t solve,…
Setting up an exposed service or ingress on a Kubernetes cluster needs authentication with OAuth 2 Proxy: here’s how to get it done in 6 easy steps.
I’ve chosen this specific list as part of an effort to foster a shared understanding of commonly used terms. This “glossary” doesn’t exist in a vacuum – it can (and should) continue to be challenged and evolve over time as our understanding changes.
I was lying in bed this morning planning the best way to handle a merge conflict I know is coming with a colleague’s PR today, and I realized I’d like to know a couple of tricks for certain situations. Here they are:
Make sure you’re doing this consistently, because down the line it makes a big difference to somebody digging through git history.
If you write tests after you wrote the code, it’s hard to be 100% the tests are legit… If they wouldn’t have failed without the code you just wrote, they’re basically useless.
Subscribe to Revelry's monthly e-newsletter "Revelations" for technology industry insights, opinions, career opportunities, and more.
"*" indicates required fields