TRC post-mortem

#1

Post by pepijndevos » Sun, Feb 16, 2014, 1:31 PM UTC

TRC post-mortem
pepijndevos.nl

Re: TRC post-mortem

#2

Post by pepijndevos » Sun, Feb 16, 2014, 1:35 PM UTC

I think "post-mortem" is over used, but it's HN-speak.

Re: TRC post-mortem

#3

Post by davidvanleeuwen » Sun, Feb 16, 2014, 3:01 PM UTC

Sorry to hear. I think it's admiring to see how you tried to build a product, but lack of selling/marketing always creates a bump in the road to a successful product.

We're currently using Slack. It supports both IRC and XMPP, has a webinterface and bouncers. It also gives you more detailed stats about the users, has integrations with other services and so on: https://slack.com/r/024fus8f-02566qu1 (shameless referral link.. k, thx, bye).

Re: TRC post-mortem

#4

Post by sp332 » Sun, Feb 16, 2014, 3:27 PM UTC

pepijndevos wrote: post #2

I think "post-mortem" is over used, but it's HN-speak.

It's not HN-speak. A "post-mortem" can be a scheduled part of development, even if a project succeeds. It's just a review after the project (or milestone) is declared complete. It's for finding lessons to apply to future projects, since it's too late for the current project :)

Re: TRC post-mortem

#5

Post by bronson » Sun, Feb 16, 2014, 3:52 PM UTC

pepijndevos wrote: post #2

I think "post-mortem" is over used, but it's HN-speak.

http://www.merriam-webster.com/dictionary/post%20mortem

First known use: 1846

(next to "Party leaders are conducting a postmortem of the election to try to find out what went wrong.")