Watch this webinar with Kent C. Dodds about frontend testing, and prepare to re-think everything you think you know about shipping apps with confidence. We want to make sure that when we ship new code, our users can use the application. The best way we’ve found to do that is to write automated tests that run before we deploy a new version of the app.
But there’s a catch with frontend testing: if our tests aren’t doing exactly what the user will do, then how do we really know that things will work when users interact with our apps?
Expert Kent C. Dodds makes us rethink everything we know about frontend testing: what it means to ship applications with confidence, and what it takes to get there. With improved tools and practices, we can be more certain that what we’re shipping to our users will work the way it’s intended. Watch his full session right here: Read more…
On September 9, 1947, Grace Hopper recorded the first computer bug ever in the Harvard Mark II computer’s logbook. The bug in question? Believe it or not, an actual bug – a moth – flew into the relay contacts in the computer and got stuck. Hopper duly taped the moth into the logbook. Then she added the explanation: “First actual case of bug being found.” (This might be the most famous moth in history.)
If only things were this simple today. As software continuously grows in complexity, so does the process of testing and debugging. Nowadays, the lifecycle of a bug in software can be lengthy, costly, and frustrating.Read more…
React is, first and foremost, a library for creating reusable components. But until React Storybook came along, reusability of components between applications was very limited. While a library of common components could be created, it was very difficult to use, as there was no useful way of documenting it.
Yes, documenting the common components via a Readme file is possible, even useful. But a component is, in its essence, something visual. A Readme file just doesn’t cut it, neither for a developer and definitely not for a designer that wants to browse a library of shared components and choose the one that fits their purpose.
This limited the usefulness of React’s component reusability.
And then React Storybook came along. React Storybook has changed the way many companies approach React by allowing them to create a library of components that can be visually browsed so as to be able to pick and choose the component they want:
There is an art to managing websites that many do not appreciate.
The browser wars of the late 90s carried over into the early 2000s, and while web standards have helped align how these browsers render front-end code, there are still dozens of versions of the five major browsers (Edge has joined the crew!), all with their own understanding of how the web should look and act. Add to that the fact most digital properties ship with many templates, each with their own way of displaying content, and those templates in turn may run on dozens or hundreds of websites, and you’re left wondering if this internet thing is really worth it.