Common Code Review Pitfalls and How to Manage Them
Learn how to avoid common code review pitfalls that engineering managers face.
Hone your team’s code reviews at the Git Pull Request level.
Learn how to avoid common code review pitfalls that engineering managers face.
Hone your team’s code reviews at the Git Pull Request level.
At Revelry, we believe in sharing and learning from one another (beliefs that are rooted in our Core Values). Among the many things we…
Note: This post reflects my experience working in LiveView Native before the recent (official) 0.3.0 release. I recently tried my hand at creating a…
In a recent article, I shared Revelry’s journey into building with generative AI. As a brief recap: since 2013, Revelry has been at the…
Every software development team has its unique set of challenges when it comes to project management and communication flow. Enter **Slax**, our bespoke Slack…
At Revelry, we believe in sharing and learning from one another (beliefs that are rooted in our Core Values). Among the many things we do…
Most software teams have left behind the Waterfall(1) methodology in favor of approaches that move faster and flex more to accommodate changes and maximize the…
Also known as CI, this refers to the continuous work of pushing new features into the main codebase. We use Travis CI to manage…
We use GitHub labels to quickly identify tickets on the kanban board. (See GitHub repository, below.) This allows us to quickly scan the board…
We understand how involved it can be as you acclimate to remote work culture, especially during times like these. With years of remote work under our belt, we’d like to help by sharing our own work from home setups and some of the tools and products that we love.
Since the implementation team is already using GitHub on a daily basis to track work and deploy code to our project repositories, our Cluster Ops team has adopted the GitOps philosophy. Having a centralized place for all of our configuration and the ability to view all deployments in a friendly, comfortable environment makes Kubernetes more accessible to the rest of the team.
There are many moving parts involved in product delivery. Ideally, we never utilize developer shortcuts or compromises. And even when we knowingly take shortcuts, the intention is always to come back and clean this up eventually.
Mutation testing involves running your test suite many times, modifying the application code in different ways to see if the tests catch the change.