Architecture & Design

16 October 2019 by Phillip Johnston • Last updated 9 September 2024After a decade spent building and shipping hardware products, we became convinced that many of the problems and schedule delays we experienced could have been avoided with a little bit of planning and thought. Repeatedly, we painted ourselves into corners with code that seemed to work well initially but caused problems months later when we finally started end-to-end system testing. Serious problems resulted in major software rewrites, changes in the technology stack, and delayed the ship date. Even worse, as we migrated from one product team to another, we …

To access this content, you must purchase a Membership - check out the different options here. If you're a member, log in.