What you need to know
- Nat Friedman announced he will no longer be CEO of GitHub.
- Thomas Dohmke, GitHub's current Chief Product Officer, will take his place.
- Friedman will gain the new title of Chairman Emeritus, which Friedman is happy about because it's a title in Latin.
Nat Friedman released a lengthy note on GitHub today announcing he'll no longer be the developer platform's CEO. On November 15, 2021, GitHub Chief Product Officer Thomas Dohmke will take his place.
But Friedman's not just disappearing in a puff of smoke. Instead, he'll adopt the title of Chairman Emeritus, which sits well with him as it checks off the box for his "lifelong ambition of having a title in Latin."
As to where Friedman will be going? Here's the teaser he gave for his upcoming plans. "With all that we've accomplished in mind, and more than five great years at Microsoft under my belt, I've decided it's time for me to go back to my startup roots," he said. "That's why I'm moving on to my next adventure: to support, advise, and invest in the founders and developers who are creating the future with technology and tackling some of the biggest opportunities of our day."
He follows that up with a bit of discussion about why his colleague, Dohmke, is qualified for the job of CEO, and then continues with a paragraph of thank yous. You can read the whole note at the hyperlink in the first sentence of this article.
If you're not familiar with GitHub or its activities, know that a lot of interesting code ends up there. For example, there was a mod that made Grand Theft Auto V look photorealistic, and you could look at its programming innards over on GitHub.
Robert Carnevale is the News Editor for Windows Central. He's a big fan of Kinect (it lives on in his heart), Sonic the Hedgehog, and the legendary intersection of those two titans, Sonic Free Riders. He is the author of Cold War 2395. Have a useful tip? Send it to email@example.com.
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.