Interesting approach for a project to collect such traps in there dependencies like this.

Interesting idea. Didn't make one but maybe I should sit and take some time to do that.

Interesting trick for remote teams. There are many ways to try to get back the "water cooler talk" in your organization, it's the first I encounter structured like this.

Very interesting stuff. This doesn't give a very cheerful picture of the current state though. Can a XMPP revival be in the cards? That would be an interesting outcome.

You've see a co-worker doing this, right? They're unlikely to be spies, but still they're inadvertently using sabotage tactics.

Quite some good advice in here. I like being around people who proactively communicate, mind the quality of the communication and look for new things to work on. Who wouldn't?

Indeed, arguments have a function. If they're used they need to be regulated, otherwise you won't get the best ideas possible in your organization due to competition.

Interesting ideas about leadership lacking in impact. Indeed it should be seen as a communal function, it's not about individuals leading each in their own directions. Think about it in a systemic way.

Very good article. I wish I'd see more organisations writing such design documents. They help a lot, and that allows to have a way to track changes in the design. To me it's part of the minimal set of documentation you'd want on any non trivial project.

Nice trick, definitely should use it more often.

Nice reminder that even though we try to make things simpler to understand to people, there is a point where we can go too far.

The words we use indeed matter. This is definitely a domain where we should avoid ambiguities...

Very extensive guide on writing better commit messages. This is important, it's a very central communication mechanism with other developers.

When you're distributed, this is all about asynchronous communication. You can't walk to a person desk (and you should probably avoid it anyway if colocated).

Very interesting piece. The chances that it is another bubble are high. It's currently surviving on a lot of wishful thinking and hypothetical. This really feels like borrowed time... I wonder what useful will remain once it all collapses. Coding assistants are very likely to survive. Clearly there could be interesting uses in a more sober approach.

Definitely this. Managing expectations is a big part of management. It's also important for customer relationship. In both cases, clear communication and finding misunderstandings early are key.

This is a bit cartoonish I'd say but there's some truth to it. I indeed regularly get onto consulting gig where you find out that the people already had the solution to their problem. In those cases it's very often because communication channels are broken somewhere (team don't feel at liberty to share what they noticed, managers having a hard time to listen, etc.).

Nice suggestion for talking about your work in various type of situations. Definitely worth trying to frame it like this.

Looks like a good resource for someone who needs to get into IPC mechanisms on UNIX flavors.

Interesting set of advices for better communication and more sustainable production of software.