I urge developers to stop being annoyed by their flaky end-to-end tests and test frameworks, and appreciate flakiness as feedback about application design that leads to flaky behavior.
All in Frontend
Think about the number of times you pass props around a React application and expect them to look a certain way or be of a certain type, or the times when you’ve passed the wrong type of argument into a function and rendered a page useless. Fortunately, there are many solutions for these preventable problems, and one of the tools we’ve found helpful here at Rent The Runway is Flow.
Without a one-to-one mapping of API service calls to application views, it was critical that we come up with a robust and coordinated approach for data binding and content updates.
Our stylesheets were getting unruly, unreadable, and impossible to maintain, which seemed like a great opportunity to refactor using two cool Sass features: lists and maps.
Our style guide greatly aided in developer-designer relations by ensuring designer mockups were consistent with the colors and Sass stylings powering the site. However, because it was separate from our site and we were rapidly evolving our brand identity, the GitHub Pages style guide quickly fell behind our storefront stylings. There was nothing forcing the guide to be kept up-to-date.