At my company, each of our API responses sends a randomly selected compliment in an HTTP header. When we're onboarding new engineers, everybody's first commit to the codebase is adding a compliment to the list.
Nobody's noticed yet because the API is currently consumed only by us, but maybe they will someday. :)
We prefix all our custom headers with `X-Ark-` (for auth tokens, request IDs for logging and such), so in this case it's `X-Ark-Compliment`.
Also, another thing we do to propagate joy in engineering culture is make heavy use of Phabricator macros in the code review process. It adds a lot of humor to the situation to have somebody draw attention to a bug in your code by pointing it out with an epic skateboard accident: http://giphy.com/gifs/fail-SMwheKIMDwA00
Comments
At my company, each of our API responses sends a randomly selected compliment in an HTTP header. When we're onboarding new engineers, everybody's first commit to the codebase is adding a compliment to the list.
Nobody's noticed yet because the API is currently consumed only by us, but maybe they will someday. :)
I like that approach. Might I ask what the header is? HTTP-COMPLIMENT or somesuch?
It could be a fun 'standard'.
We prefix all our custom headers with `X-Ark-` (for auth tokens, request IDs for logging and such), so in this case it's `X-Ark-Compliment`.
Also, another thing we do to propagate joy in engineering culture is make heavy use of Phabricator macros in the code review process. It adds a lot of humor to the situation to have somebody draw attention to a bug in your code by pointing it out with an epic skateboard accident: http://giphy.com/gifs/fail-SMwheKIMDwA00