Development
Our Engineering team, apprentices, Front-End Developers, and Designers share insights on the development process
Why Behavior Driven Development (BDD) Makes User Stories 100% Better
At Revelry, we use BDD for all members of the team — and yes, that team includes our clients — so that everyone is clear about the intended user experience in the final product. Revelry’s flavor of BDD is a process for describing software features that is biased toward user’s actions and the results of those actions.
My Introduction to Property Testing
Lately I’ve been exploring various automated testing techniques, and it’s about time I got to property-based testing, also known simply as property testing. I…
Implementing Globalization (G11N) in Software Applications
While working on getting a product live in Canada, we have gone through various trials and tribulations getting localization to work. Globalization generally refers to the combination of localization (L10N), and internationalization (I18N).
Getting My Feet Wet with Deep Learning and Word2Vec
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…
6 WordPress Features You Should Know – Or May Have Forgotten About
There are so many features in WordPress, it’s impossible to know them all. The trick is to find the hidden gems that make your life easier.
Improve Your Workflow in the Terminal with These fzf Tips
Tips and code snippets that can be used to help improve your workflow in the terminal, and, how to create your own fzf-based workflow.
Improving UX Design with React Native Features
Front-end development for React Native is an entirely different ball game, especially when it comes to styling content, because styles are written in JavaScript. At one point or another, you’ll face challenges like a different markup, style properties, number conversions, boundaries, and lots of weird errors. So Brittany gathered up some resources for you.
Prioritizing Features and Bugs in Software Development
Whether it’s a feature, a bug, or a regression, it’s all work. It all has the same level of prioritization before we add in the business context. This is how we decide what gets worked first.
Here’s Why We Do Case Interviews for Software Engineers
Technical interviews are broken. We do case interviews in order to take candidates from hearing the scenario, to asking clarifying questions, to giving broad opinions and concepts, to specific architecture and programming tasks.
Managing Technical Debt: Etiquette, Tips, and Techniques
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.