SO blog editor here (and author of the piece). Sorry for the confusion, we're republishing our top ten posts of the year over the holidays, and I guess y'all picked this one up again.
Not a great thing to do IMO... by all means resurface the good stuff to the top of the blog, but why change the date? SEO? I don't think there's a good answer?
Since the date is in the URL, you broke old links, and without a redirect at that. You should look into how you "republish" because it doesn't look like you're doing it ideally.
Just some helpful advice. Without a redirect, SEO on the old post will go poof.
I understand if they need to update the date to get it to show up at the top of the blog. But, in that case they can just add a few words to the front of the article saying that they are republishing an item from September.
Author here. We did use Confluence, but as other folks had said, it went very stale. Not everyone could edit everything and there was no structure. Confluence is a mess in my experience.
Have to agree. Without a clear set of standards on how to structure things, it ends up being chaos very quickly. We had a PM for a while, who gravitated more towards QA, and when they got ahold of Confluence they went crazy (in a mostly good way). We had so many great "How To" articles on how to perform various tasks in our system form an internal user perspective, all authored by the same SME.
Unfortunately, given their affinity for testing things, the How To docs starting taking on that QA perspective and everything ended up in a QA "space". Sure, it's easy to move them around, but there wasn't a clear cut way on how to separate the "How To" from the "QA" - and then they left.
Since then, people add things when managers say "make sure that's in Confluence" and it ends up getting placed in the areas they're most familiar with, not necessarily where it should be. Add in the aforementioned lack of standards and no two documents look the same. Then we started using Confluence for devs to write Test Plans and QA to execute them - and now it just makes my brain hurt whenever I have to go in there.
Some of it is a cultural problem: we're email and Teams heavy and so much of our "documentation" is buried in those tools. So then we adopt something like Confluence to move our knowledge base to that, but finding stuff in Teams is a nightmare (posted in another thread on that). So now rather than having one tool to rule them all, we just have another half-baked attempt.
We're monolithic for the most part, so I'm not sure Backstage would help us, but the article mentioned Stack Overflow for Teams, so maybe that would? (insert relevant XKCD here on competing standards)
Also Confluence and JIRA end up weirdly competing, with information spread between the two, sliced up chronologically in JIRA, and based on some a-priori and/or competing sets of structurations...
Businesses aren't demanding these things because they would take away their leverage over their employees. You need the employer for your income and your health insurance right now. Why would they want to make it easier for you to leave them?
