This is a remarkably well-written article. Made me really feel for the company, both in terms of sympathy and wanting to see them succeed.
One thing it did left me wondering, was covered in the final paragraph:
"...Engineers can spot his name and edits throughout the code repository. And occasionally, back-end commands will pop up messages, little surprises that Tang built into the system years ago. One reads, “You’re doing a good job today.”
How would your company react to messages like that? Do any of you take a strategy for injecting joy into your code?
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
Money can help get through the time you need to get back on your knees. I've had the misfortune of having my cofounder die after 18 month and two investments rounds and some money would have really help.
Also you have to prepare for this kind of problems in advance because all of a sudden a substantial part of the shares of the company will be in limbo until the legalities are handled (and it can really stink if the family of the deceased is not helping...) which means: you can't raise money anymore, you can't really hire someone good as most people are very afraid of this kind of situation.
I couldn't imagine any small company who didn't have life insurance on its owners - I thought that was like one of the first things you did. Guess it gets overlooked.
It's not the phosphoric acid, its the carbonation. Plain old carbonated water is acidic as well which can erode the teeth. That being said your saliva can repair the teeth. The current wisdom is don't drink solely acidic drinks and wait between acidic food/drink and teeth brushing.
One thing it did left me wondering, was covered in the final paragraph:
"...Engineers can spot his name and edits throughout the code repository. And occasionally, back-end commands will pop up messages, little surprises that Tang built into the system years ago. One reads, “You’re doing a good job today.”
How would your company react to messages like that? Do any of you take a strategy for injecting joy into your code?