Live data from Hacker News

Microsoft Office migration from Source Depot to Git

danielsada.tech

71–80 of 290 posts

Re: Microsoft Office migration from Source Depot to Git

#72
post #7

I spent nearly a week of my Microsoft internship in 2016 adding support for Source Depot to the automated code reviewer that I was building ( https://austinhenley.com/blog/featurestheywanted.html ) despite having no idea what Source Depot was! Quite a few devs were still using it even then. I wonder if everything has been migrated to git yet.

Most of the day to day is in git, now.

Re: Microsoft Office migration from Source Depot to Git

#73
post #24

> Authenticity mattered more than production value. Thanks for sharing this authentic story! As an ex-MSFT in a relatively small product line that only started switching to Git from SourceDepot in 2015, right before I left, I can truly empathize with how incredible a job you guys have done!

Yeah, it was a whole journey. I can't believe it happened. Thanks for your comment.

I spent a lot of time coaching people out of source depot, it was touch and go there for a while. It was worth it though thank you for Your effort.

Re: Microsoft Office migration from Source Depot to Git

#75
This article makes out thousands of engineers that are good enough to qualify at Microsoft and work on Office but haven't used git yet? That sounds a bit overplayed tbh, if you haven't used git you must live under a rock. You can't use Source Depot at home.

Overall good story though

Re: Microsoft Office migration from Source Depot to Git

#76

Earlier quoted context omitted.

I didn't even know Microsoft SourceSafe existed.

Lucky you. Definitely one of the worst tools I’ve had the displeasure of working with. Made worse by people building on top of it for some insane reason.

It was at least a little better than CVS, but with SVN available at the same time, never understood the mentality of the offices that I worked at using Source Safe instead of SVN.

Re: Microsoft Office migration from Source Depot to Git

#78

We communicated the same information through multiple channels: weekly emails, Teams, wiki docs, team presentations, and office hours. The rule: if something was important, people heard it at least 3 times through different mediums. If only this were standard. Last week I received the only notification that a bunch of internal systems were being deleted in two weeks . No scream test, no archiving, just straight delet…

Even with this, there were many surprised people. I'm still amazed at all of the people that can ignore everything and just open their IDE and code (and maybe never see teams or email)

In my previous company it came to me as a surprise to learn from a third party that our office had moved lol.

Re: Microsoft Office migration from Source Depot to Git

#79

This article makes out thousands of engineers that are good enough to qualify at Microsoft and work on Office but haven't used git yet? That sounds a bit overplayed tbh, if you haven't used git you must live under a rock. You can't use Source Depot at home. Overall good story though

You’d be surprised at the amount of people at Microsoft that their entire career have been at Microsoft (pre-git-creation) that never used Git. Git is relatively new (2005) but source control systems are not.
Post reply on HN