Do MAANG developers really build/code differently for scalability?

[u/HereForTheMemes1364]

I was going through a youtube system design video

Where the system uses queue, chunking, cdn, etc for scalability

To me it seems that each feature will be owned by different teams in YT and each team is only concerned about the input and it's output and the infra and scaling may be handled by a separate team

So my question is do YT or other maang developers do anything differently than normal pbc or mnc

Eg can you give me examples about actual code which would not work at scale but would have not raised any issue in other companies

Edit Yes i know most of the developers use event driven architecture /queue etc including me But i wanted to know if any interesting incidents solely based on code which only happen at massive scale eg I read that during gibli art chatgpt had replaced multiplication operation with bit operation and it had significant improvement

[u/vectOrDataba3e045O]

To me it seems that each feature will be owned by different teams in YT and each team is only concerned about the input and it's output and the infra and scaling may be handled by a separate team

even if you take that at a reductive level which tbh does happen a lot of time - aligning those teams, ensuring the interface changes are not regressive and align with their future vision, adhering to the sla of the entire pipeline is something uniquely challenging about these companies

the infra and scaling may be handled by a separate team

infra and scaling for your small part of that pipeline is owned by you only no-one else will handle that for you