flimzy

4 ms·

1. 1.▲
   by flimzy 3y ago

   Post author here. For any non-trivial app, there would ideally be a set of domain error types/codes that the various application layers know about, rather than concerning themselves with HTTP statuses. I didn't discuss that in the
2. 2.▲
   by flimzy 3y ago

   Post author here. I probably could have made this a bit more clear, but I feel it was a slight tangent to the main point of the post: In any serious app, I wouldn't actually set an HTTP status directly in the db layer. Rather, I would
3. 3.▲
   by flimzy 3y ago

   "having been on one" -- So n of 1. Classic "my experience trumps yours".
4. 4.▲
   Things a Go Lover Hates About Go(youtube.com)

   3 points by flimzy 4y ago|0 comments
5. 5.▲
   My Funny Habit: Code Review for Solo Projects(jhall.io)

   1 points by flimzy 6y ago|0 comments
6. 6.▲
   Solo DevOps(jhall.io)

   8 points by flimzy 7y ago|0 comments