Programming

17419 readers

27 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

104

Why Facebook does not use Git – and why most other devs do • DEVCLASS (devclass.com)

submitted 4 months ago by [email protected] to c/[email protected]

44 comments fedilink hide all child comments

Facebook does not use Git due to scale issues with their large monorepo, instead opting for Mercurial.
Mercurial may be a better option for large monorepos, but Git has made improvements to support them better.
Despite some drawbacks, Git usage remains dominant with 93.87% share, due to familiarity, additional tools, and industry trends.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 13 points 4 months ago (3 children)

The inhouse tooling from the massive tech companies is very cool but I always wonder how that impacts transferrable skills. I work in a much smaller shop but intentionally make tech decisions that will give our engineers a highly transferrable skill set. If someone wants to leave it should be easy to bring their knowledge to bear elsewhere.

[–] [email protected] 8 points 4 months ago (1 children)

Speaking from my own experience and a few other seniors I work with, you try to recreate solutions you like at those smaller shops. It may not be identical, but you know what's possible.

I came into a company that didn't have a system to manage errors. At my old job, errors would get grouped automatically and work can be prioritized through the groupings. The new company only handled errors when they saw it, by word of mouth.

Immediately went to work setting up a similar system.

[–] [email protected] 5 points 4 months ago

There’s also a whole industry of ex-Googlers reimplementing Google tooling as SaaS services to sell to other ex-Googlers at other companies.

There’s even a lookup table: https://github.com/jhuangtw/xg2xg

(some of those are open source projects, some are SaaS services)

[–] [email protected] 1 points 4 months ago

The inhouse tooling from the massive tech companies is very cool

I agree. I personally know nothing about tooling like this but I went through the tooling used at rockstar for example GTA V and it was very cool to how much they have automated and made tools easier to use.

[–] [email protected] 1 points 4 months ago

Oh, it impacts indeed. And I would expect that to be partially to keep the devs from hopping away, as they will have a hard time transferring

On the other hand, onboarding is longer and wastes more time and money of the company ¯\_(ツ)_/¯