科技回声

We send weekly digests of what we did/achieved/tried of thr past week.

A lot of functional and technical specs on Confluence, involving as many shareholders as possible. Prevents boring meetings, improves shared understanding, prevents surprises down the road, serves as documentation for new team members.<p>Inspiration came from this fantastic serie by Joel Spolsky: <a href="https://www.joelonsoftware.com/2000/10/02/painless-functional-specifications-part-1-why-bother/" rel="nofollow">https://www.joelonsoftware.com/2000/10/02/painless-functiona...</a>

Usually by flaming someone publicly in the main Slack channel for making a mistake. After enough flame hits, you can find the answer with a nice search.

Documentation is crap. Confluence Jira are all useless time wasters, no fullfilment. No kick.<p>Do a POC and give a demo.

All on Confluence and we have people that mostly work on keeping it up to date.

We send weekly digests of what we did/achieved/tried of thr past week.

Usually by flaming someone publicly in the main Slack channel for making a mistake. After enough flame hits, you can find the answer with a nice search.

Documentation is crap. Confluence Jira are all useless time wasters, no fullfilment. No kick.<p>Do a POC and give a demo.

All on Confluence and we have people that mostly work on keeping it up to date.

Ask HN: How do you share knowledge in your company?

4 条评论

Ask HN: How do you share knowledge in your company?

4 条评论