In part one of this two-part blog series, we looked at two approaches to codebase decisions: working with existing code patterns and refactoring for…
Code content on the Revelry Blog: Navigate our lab notes by using the tag system.
Codebase decisions aren’t just about writing code. They’re about making choices that shape the reliability, maintainability, and overall quality of software. Since requirements, technologies,…
Software engineer, Jonathan Walters, breaks down three approaches he took to solve the New Year Chaos logic problem from HackerRank.
After listening to this episode of Practical AI, I got interested in experimenting with Word2Vec. According to wikipedia, Word2vec is a group of related models that…
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.
The hard part of this was recognizing the algebra beneath layers of domain-specific business rules.
Coding without if-statements is one method for learning other ways to structure your code. That doesn’t mean never use if-statements. Being careful with conditional logic makes better code. Here’s why.
You might want to avoid Jest if you don’t need its features, don’t like its conventions, or if Jest is incompatible with your other tools. If you choose not to use Jest, you can use Jasmine directly instead.