November 2020 Summaries

Cryptic error messages can be frustrating and time-consuming for developers. As framework and library designers, it is crucial to follow design principles that create helpful and actionable error messages. These principles include writing errors for users rather than maintainers, suggesting why an error occurred or how to fix it, making errors searchable, logging frequent errors, and avoiding verbosity in error messages. By following these guidelines, developers can improve the user experience and save time during debugging processes.

Temporal, an application development tool, faced challenges in its documentation process due to its unique approach and inherited information from its predecessor. The team decided to focus on creating a great new user experience by developing effective SDK tutorials. They used Snipsync, a tool that synchronizes code with documentation, and created template repositories for sample applications. The money transfer scenario was chosen as the main tutorial to demonstrate Temporal's benefits. The team plans to continue improving their documentation and engaging with the community for feedback.

The Temporal team has been busy working on various updates and features, including the announcement of Temporal v1.0 as their first production-ready release, raising Seed and Series A rounds led by Amplify and Sequoia, shipping a new Landing Page with an explainer video and case studies, and adding PostgreSQL 9.6 support. The team has grown, and they are currently hiring. They are now working on implementing authentication for Temporal Web, which is expected to be OAuth/OpenID Connect (OIDC) Single Sign-On based. The process will involve providing identity provider information in a config file. Beta testers are being sought for feedback on the new feature.