Error messages aren't just annoying - they should be helpful.
5 tips to write better error messages.
Error handling is often forgotten and treated as a non-functional requirement. But it is a critical part of an API response.
A good error message will:
- Use the right error code.
- Expose only the necessary information, hiding the internal details.
- Help the consumer to understand the problem.
- Include tracing information.
- Include a link to the documentation. (If possible)
Every good error message should give your users a little nudge in the right direction.
Invest in your messages; Your customers will thank you.
What else?
TIL — GitHub's custom markdown syntax for notes and highlights supports Note, Tip, Important, Warning, and Caution.
When did this happen?
Side note: still not a fan of their non-standard blockquote syntax. 😅
Excited to be sharing some lessons learned from migrating our frontend codebase away from Create React App. Come join us on June 27th at the Madison in downtown Detroit! https://t.co/w6JIIvCH0R
Speed up sequential async/await code with promise concurrency
But be aware of a couple critical gotchas!
Read more in my latest article: https://t.co/pMLBx858dw
As a manager, what are ways you can encourage and support software engineers on your team to introduce practices that can help the team execute better?
Here are some.
What other approaches that you've seen work well, in encouraging engineers to make the team more efficient?
One of the most underrated languages to learn - that is surprisingly fast to do: SQL.
The language has a handful of operators. They take some - but not too much - time to understand and master.
Once you know how to join, group, union, create a view: that’s all you need really.
Start-up life = hard won insights. Here are my top 10 for this year.
1. Doing well at a start-up is not simply about skill, it is about mentality.
A start-up mentality values action over correctness, results over process. It suits those that value autonomy over clarity.
Problem: You want to re-throw a JavaScript error to provide a friendlier error. But, you want to keep the original error details too.
Solution: Include the original error via `cause`.
More: https://t.co/TyF4IyYxju
#javascript
If you use lastpass, immediately change all related passwords & find an alternative.
I think it is important people are made aware of this breach. @SwiftOnSecurity
If anyone has any more insight into this or feel they could help investigate it, please reach out.
The best suggestion I have for software engineers with some experience is to learn a "different stack": dip your toes at least. If you're doing backend: do some frontend or mobile. Or the other way around.
You'll learn a ton and appreciate how challenges are different there.