Quick tip for anyone posting feedback answers to announcement posts: include a ## Heading at the top of it that summarizes its basic gist, similar to what you'd write as a title had you been posting it as a new question. This makes it easier for others (especially the team) to have an idea about it when reading your feedback.
@JourneymanGeek sorry, my trust in the company was never restored and most likely will never be. Maybe they're doing some good things recently, that's good, but I don't trust them to keep it up. Not the dev layer of course, the highest levels.
So I'm standing by, watching, and that's about it.
Maybe the delay with the new CM is a sign to something bad behind the scenes, e.g. manager(s) getting cold feet about the whole thing and freezing the changes. Won't be surprised if that's the case.
Well the recent CEO blog post proves (to me at least) the main, if not only, focus of SE is the Teams product. CM's aren't really required for that. So....
Still, I'm getting a bit tired of all the conspiracy theories and whatever. Either just ask someone that may be able to answer you, or accept that it's not there yet and will happen eventually.
@JourneymanGeek nah I'll leave it. I'm trying to read through the [badges] tag, and I'm somewhere in 2014...(At one point I started thinking if something should be closed...)
Tim Post, Shog, and Jon Ericson wrote a lot of good post through the years...There's some amazing wisdom behind their ideas. (Retrospectively it explains SE as new users come to know it.)
With almost 5 years on SO, 16 Q&As (one with 13K views) and 22K reach, I'd suspect that we don't constitute most of the views; if anything he's view deficient.
