How to survive the StackOverflowgeddon

Full disclosure - I built getmanfred.com/stackoverflowgeddon

As you probably already know, next March 31st, Stack Overflow will discontinue Developer Stories, their own flavour of online CV.

4.7 million developers will be affected, and the professional data they maintained during seven years will be lost forever if they don't find a backup. The only solution Stack Overflow has provided is to download your CV... as a PDF file

You can find some good options out there to retrieve your data and even get it back online:

• You can import your DevStory to File/New/Job but you won't have a copy of your data and you have to register first :/
• developerstory.dev exports your DevStory as a generic JSON file but you have to authenticate with your Stack Overflow account first.
• devstory.fyi allows you to:
  • Download your DevStory as a JSON file (with the JSON Resume open-source format), but the downloaded JSON is not valid as is.
  • Import your DevStory data to get an online version.
• Finally, Manfred has developed an open-source solution. You can:
  • Download your data as a valid JSON file (with the MAC open-source format)
  • Download the open-sourced code used to scrap your data.
  • Import your DevStory data to get your online version and much more features (eg. you can sync your data in Manfred with one of your repos on GitHub and LinkedIn will be the next platform to follow)

Some developers ask themselves about the benefits of maintaining an online CV when they have job offers every day on LinkedIn. The point is if we want to manage our career on our own or let LinkedIn work it by us. If we want to look for the best opportunities for us or let LinkedIn decide which options are worth it.