Sometimes it's better not to communicate publicly at all than to write vague nonsense like this, especially on a controversial issue you've caused as a founder.<p>Imagine Basecamp employees reading this blog post, trying to make sense of the latest controversy at their workplace; does this add anything meaningful to the discussion other than, "shit will blow over, deal with it".
Basecamp leadership has always thrived on fanning the flames of public controversies.<p>They're a tiny company. Less than 100 people. Everyone knows about their software because they're loud and make a lot of noise, but I barely know anyone who continues to use it.<p>Yet here we are, following along with their internal company drama and plastering their name across social media. They seem to be doubling down on the controversy with this weirdly cryptic blog post. Probably because they've always been rewarded for fanning the flames in the past, so why stop now?