Trading off Value, Quality and Time
The traditional Iron Triangle tries to explain in graphical form how software projects need to make hard tradeoffs between scope, schedule and resources.
Recent Posts
React Native Six Months In
NerdWallet released our first cross platform mobile app at the start of 2017, about six months ago. We choose to use React Native, and we are still using 99%...
Minimizing Impact of Interruptions on Engineers
Any software engineer knows the feeling of being “in the flow”, or “in the zone”. It’s when you get a large block of uninterrupted time to just code. These p...
Best Practices for Meetings
Every team meeting needs a primary owner. If you are the owner of the meeting, it’s your responsibility to make sure that this is a great use of team time.
Getting Started with AWS Device Farm and Python Appium
AWS Device Farm is a service for running mobile app integration tests against a suite of physical devices. The Amazon documentation is exhaustive, and they s...
Long Term Software Estimates
False scheduling to match a patron’s desired date is more common in our discipline than elsewhere in engineering because it is VERY DIFFICULT to make a vi...
Appium + React Native Quickstart
Appium is a great framework for automated functional testing of mobile apps. But it’s very general purpose, meaning that there is relatively little documenta...
React Native Multiple Release Variants
By default, React Native gives you a debug variant and a release variant. In debug mode, the app connects to a running packager service, and enables various ...
Deploying React Native apps with Buddy Build
Buddy Build is a great tool for getting your app out to physical devices, whether that is during development, or in production. Their tool is fairly agnostic...
Tiger Team Survival Guide
A tiger team is a diversified group of experts brought together for a single project, need, or event. They are usually assigned to investigate, solve, bui...