I often take notes in the form of “TODO” comments, as I work through a problem. Then I have my editor set up to highlight them, and my git asks me if I’m sure I want to commit them. Works pretty well with keeping my thought process straight
It’s also an amazing way of duck-debugging. By the time you write down what the problem is, you’ll figure out where’s the issue or at least what you should try next.
“X is giving me an error, I checked X’s logs. X communicates with Y… Oh, I need to check Y next!”
And if you can’t figure it out, you have the problem and everything you tried documented so you can ask for help and get answers effectively.
What don’t you like about graphql error handling? Whenever I’ve made a graphql api, I use the default errors as unhandled/system errors and payloads return handled error types.
It’s a bit more boilerplate to wire up, but I find it smooth to build and use
I have worked with most of these people at one point or another. I used to sit next to an old architect like walters. He had so many patents the company only recognize him on every 10th one.
programmerhumor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.