I can vouch for almost everything the person mentioned above. I have been asked questions like "What is git?" "Can pandas parse Excels?" from L3 and a Tech Lead respectively. Recently I read an email where they hired a guy for an SDE role who was a "chef" until 2 months ago. I don't know what's happening really. People put on busy masks by going into meetings and spending 1h talking vaguely about things, eventually coming out of the meeting having achieved nothing. At the end of the day, they advertise saying they're the best in the business when it comes to tech. Hahaha, sure sure.
Trust me there internal wheels in motion to start solving these issues. The problem is at our scale it's hard to turn the ship on a dime. The cloud is not the winner you seem to think it is. We have smart engineering who seem to forget the basics to scaling. We are working on changing the culture one piece at a time.
Honestly first time hearing someone using Read Uncommitted transaction isolation level.
3TB of RAM is REALLY a lot. We have done someone spiky (very high traffic) events in the world and still our primary database has only 64G RAM (in spite of one of the major application don’t have connection pooling).
This is exactly like my job! With (nolock) is necessary when you have hundreds of people reading the row. Normal reads take a shared read lock, which doesn't block other reads, but DOES block updates. Do you want people reading a company data row to block an admin updating a value there? You don't. With nolock shouldn't be used on data that might have _just_ been inserted. But on the 99.9% of the data that is more than a second old it's fine