This is the 38th — and final — edition of the Developer Newsletter. It's been a pleasure writing for you, and we wanted to close with a proper goodbye rather than simply going quiet.
In this edition: an update we hadn't covered yet, and how to stay up to date from now on.
If you've ever learned about important app development news from a four-times-forwarded Slack post, or an offsides comment in a meeting — the Dynatrace Developer Blog is for you. It's a single, searchable, filterable feed of news worth knowing, without all the channel-hopping: a steady mix of updates about new features and ideas, interesting events, and tools for your work. It launched back in June and is where we'll be publishing going forward — and, as you'll read at the end of this edition, it's also the replacement for this newsletter. The post below is a good example of what you'll find there.
A good error message can turn a dead end into a recoverable step. The new Error messages pattern brings together everything you need to design clear, consistent error messages across your app, whatever component you're working with.
After 38 editions, the Developer Newsletter is coming to an end.
When we launched the newsletter, it was the primary way we shared developer updates, new documentation, and community news with app builders. The Dynatrace Developer Blog is now that home — a single, searchable, filterable feed of news worth knowing, without the channel-hopping. It isn't a changelog — Release notes remain the definitive record of every Strato and toolkit change — but it's where you'll find the updates and announcements this newsletter has been carrying.
Going forward, the blog is the place to check.
Nothing is being deleted. All 38 editions will remain accessible here on the community, exactly as they are.
Where to stay informed going forward:
Thank you for reading and for the kudos along the way.