,
3 tweets,
1 min read
Read on Twitter
A tiny thing that makes my life so much easier:
We have an internal alias for product quality issues, designed to bring the effort required to report them to epsilon. Instead of having to write a ticket and figure out where to write it, you just send an email and a team triages.
We have an internal alias for product quality issues, designed to bring the effort required to report them to epsilon. Instead of having to write a ticket and figure out where to write it, you just send an email and a team triages.
My most recent issue was along the lines of "FYI, if you're using the ruby bindings and give the version number as a date object rather than a string representation of a date, you get an opaque error message. We should just do what the user meant to do."
(I could see an argument there for raising a type error instead but ideally it would be pretty explicit as to the cause and the action you expected the user to take subsequent to it.)
