Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Teams
Q&A for work
Connect and share knowledge within a single location that is structured and easy to search.
Learn more about Teams###Yes! There will be product updates and they'll resume as early as 2019-06-21!
###Updates on the blog :: Q&A on Meta.
###So meta will be for .. blog comments?
###Yes! There will be product updates and they'll resume as early as 2019-06-21!
###Updates on the blog :: Q&A on Meta.
###So meta will be for .. blog comments?
Super-short, totally cheat-sheet ready answer:
###Yes! There will be product updates and they'll resume as early as 2019-06-21!
For a long time, our company blog has been ... well, kinda corporate-y. That's not bad for a corporate blog, but along the way we went from being probably way too informal on our blog to a little too formal. A lot of the old blog posts are great, but they talk about stuff that only folks that are active on our sites really understand. To an outsider, it was hard to see why so much of that stuff was novel, given that so much of it reads just like common sense years later. But we were the ones that made it common sense. We lost something when we stopped talking about that.
Tim, why are you getting all nostalgic about the blog?
Well, my calendar has been down most of the day but I have other reasons too. We have been working with folks across the organization, joining in on the push to bring that community and product updates back to the blog now that we have quite a few more contributors and some better flexibility in the platform.
###Updates on the blog :: Q&A on Meta.
Meta doesn't work very well for "grand announcement" type posts because feedback to them gets captured as answers and it's sometimes like being inside a loudly ringing bell. Smaller incremental updates don't work so well on meta because it's easy to miss stuff (producing and consuming) and there's no real concept of shared drafts where folks from many teams can converge.
The platform was never really all that great at open discussion type stuff, that's ... a big reason why we so strongly discourage it on our main sites.
As updates are posted to the blog, feel free to ask a question on this or any other meta site about something on the blog, and we'll do our best to respond.
###So meta will be for .. blog comments?
No. While we're looking at different comment systems for the blog, meta will be a place to have a sidebar chat about a specific thing related to something in the blog, which needs more than a blog comment system to be facilitated adequately. We'd rather have you just ask questions where things aren't clear rather than try to anticipate a bunch of questions and just end up realizing we now have a post with a bunch of questions we never anticipated as answers.
As for the specific content (e.g. presence on bugs, what's currently being worked on, what's getting approved but delayed, declined, etc) we're looking at more directly interfacing our back-end bug tracker with meta so you can see (essentially) what we do when it comes to bugs and features. I don't have 100% details on that now, but maintaining the lists of lists of lists of stuff isn't scaling well (obviously), so the ideal way is just let anyone who cares about a bug or feature see the status by where it is on our back end system, by somehow showing that on meta. That's all up in the air at this point.
So no, they're not stopping - they're just changing, and (ideally) becoming less dependent on humans updating stuff like meta posts manually to get them to you, while also letting our product teams collaborate better on shared drafts for announcements.
I'll update this answer as I have more specifics (the irony of that isn't lost on me).
Super-short, totally cheat-sheet ready answer:
###Yes! There will be product updates and they'll resume as early as 2019-06-21!
For a long time, our company blog has been ... well, kinda corporate-y. That's not bad for a corporate blog, but along the way we went from being probably way too informal on our blog to a little too formal. A lot of the old blog posts are great, but they talk about stuff that only folks that are active on our sites really understand. To an outsider, it was hard to see why so much of that stuff was novel, given that so much of it reads just like common sense years later. But we were the ones that made it common sense. We lost something when we stopped talking about that.
Tim, why are you getting all nostalgic about the blog?
Well, my calendar has been down most of the day but I have other reasons too. We have been working with folks across the organization, joining in on the push to bring that community and product updates back to the blog now that we have quite a few more contributors and some better flexibility in the platform.
###Updates on the blog :: Q&A on Meta.
Meta doesn't work very well for "grand announcement" type posts because feedback to them gets captured as answers and it's sometimes like being inside a loudly ringing bell. Smaller incremental updates don't work so well on meta because it's easy to miss stuff (producing and consuming) and there's no real concept of shared drafts where folks from many teams can converge.
The platform was never really all that great at open discussion type stuff, that's ... a big reason why we so strongly discourage it on our main sites.
As updates are posted to the blog, feel free to ask a question on this or any other meta site about something on the blog, and we'll respond.
###So meta will be for .. blog comments?
No. While we're looking at different comment systems for the blog, meta will be a place to have a sidebar chat about a specific thing related to something in the blog, which needs more than a blog comment system to be facilitated adequately. We'd rather have you just ask questions where things aren't clear rather than try to anticipate a bunch of questions and just end up realizing we now have a post with a bunch of questions we never anticipated as answers.
As for the specific content (e.g. presence on bugs, what's currently being worked on, what's getting approved but delayed, declined, etc) we're looking at more directly interfacing our back-end bug tracker with meta so you can see (essentially) what we do when it comes to bugs and features. I don't have 100% details on that now, but maintaining the lists of lists of lists of stuff isn't scaling well (obviously), so the ideal way is just let anyone who cares about a bug or feature see the status by where it is on our back end system, by somehow showing that on meta. That's all up in the air at this point.
So no, they're not stopping - they're just changing, and (ideally) becoming less dependent on humans updating stuff like meta posts manually to get them to you, while also letting our product teams collaborate better on shared drafts for announcements.
I'll update this answer as I have more specifics (the irony of that isn't lost on me).
Super-short, totally cheat-sheet ready answer:
###Yes! There will be product updates and they'll resume as early as 2019-06-21!
For a long time, our company blog has been ... well, kinda corporate-y. That's not bad for a corporate blog, but along the way we went from being probably way too informal on our blog to a little too formal. A lot of the old blog posts are great, but they talk about stuff that only folks that are active on our sites really understand. To an outsider, it was hard to see why so much of that stuff was novel, given that so much of it reads just like common sense years later. But we were the ones that made it common sense. We lost something when we stopped talking about that.
Tim, why are you getting all nostalgic about the blog?
Well, my calendar has been down most of the day but I have other reasons too. We have been working with folks across the organization, joining in on the push to bring that community and product updates back to the blog now that we have quite a few more contributors and some better flexibility in the platform.
###Updates on the blog :: Q&A on Meta.
Meta doesn't work very well for "grand announcement" type posts because feedback to them gets captured as answers and it's sometimes like being inside a loudly ringing bell. Smaller incremental updates don't work so well on meta because it's easy to miss stuff (producing and consuming) and there's no real concept of shared drafts where folks from many teams can converge.
The platform was never really all that great at open discussion type stuff, that's ... a big reason why we so strongly discourage it on our main sites.
As updates are posted to the blog, feel free to ask a question on this or any other meta site about something on the blog, and we'll do our best to respond.
###So meta will be for .. blog comments?
No. While we're looking at different comment systems for the blog, meta will be a place to have a sidebar chat about a specific thing related to something in the blog, which needs more than a blog comment system to be facilitated adequately. We'd rather have you just ask questions where things aren't clear rather than try to anticipate a bunch of questions and just end up realizing we now have a post with a bunch of questions we never anticipated as answers.
As for the specific content (e.g. presence on bugs, what's currently being worked on, what's getting approved but delayed, declined, etc) we're looking at more directly interfacing our back-end bug tracker with meta so you can see (essentially) what we do when it comes to bugs and features. I don't have 100% details on that now, but maintaining the lists of lists of lists of stuff isn't scaling well (obviously), so the ideal way is just let anyone who cares about a bug or feature see the status by where it is on our back end system, by somehow showing that on meta. That's all up in the air at this point.
So no, they're not stopping - they're just changing, and (ideally) becoming less dependent on humans updating stuff like meta posts manually to get them to you, while also letting our product teams collaborate better on shared drafts for announcements.
I'll update this answer as I have more specifics (the irony of that isn't lost on me).
Super-short, totally cheat-sheet ready answer:
###Yes! There will be product updates and they'll resume as early as 2019-06-21!
For a long time, our company blog has been ... well, kinda corporate-y. That's not bad for a corporate blog, but along the way we went from being probably way too informal on our blog to a little too formal. A lot of the old blog posts are great, but they talk about stuff that only folks that are active on our sites really understand. To an outsider, it was hard to see why so much of that stuff was novel, given that so much of it reads just like common sense years later. But we were the ones that made it common sense. We lost something when we stopped talking about that.
Tim, why are you getting all nostalgic about the blog?
Well, my calendar has been down most of the day but I have other reasons too. We have been working with folks across the organization, joining in on the push to bring that community and product updates back to the blog now that we have quite a few more contributors and some better flexibility in the platform.
###Updates on the blog :: Q&A on Meta.
Meta doesn't work very well for "grand announcement" type posts because feedback to them gets captured as answers and it's sometimes like being inside a loudly ringing bell. Smaller incremental updates don't work so well on meta because it's easy to miss stuff (producing and consuming) and there's no real concept of shared drafts where folks from many teams can converge.
The platform was never really all that great at open discussion type stuff, that's ... a big reason why we so strongly discourage it on our main sites.
As updates are posted to the blog, feel free to ask a question on this or any other meta site about something on the blog, and we'll respond.
###So meta will be for .. blog comments?
No. While we're looking at different comment systems for the blog, meta will be a place to have a sidebar chat about a specific thing related to something in the blog, which needs more than a blog comment system to be facilitated adequately. We'd rather have you just ask questions where things aren't clear rather than try to anticipate a bunch of questions and just end up realizing we now have a post with a bunch of questions we never anticipated as answers.
As for the specific content (e.g. presence on bugs, what's currently being worked on, what's getting approved but delayed, declined, etc) we're looking at more directly interfacing our back-end bug tracker with meta so you can see (essentially) what we do when it comes to bugs and features. I don't have 100% details on that now, but maintaining the lists of lists of lists of stuff isn't scaling well (obviously), so the ideal way is just let anyone who cares about a bug or feature see the status by where it is on our back end system, by somehow showing that on meta. That's all up in the air at this point.
So no, they're not stopping - they're just changing, and (ideally) becoming less dependent on humans updating stuff like meta posts manually to get them to you, while also letting our product teams collaborate better on shared drafts for announcements.
I'll update this answer as I have more specifics (the irony of that isn't lost on me).
