The name is burnt. They still are a company with business interests. While their interests might align today with the open source community this doesn't have to be so tomorrow and there is no resistance internally to burn these bridges they are building today.
I wonder how Microsoft can manage to commercialize all the projects on GitHub. Maybe by providing an universal installer that works through the Windows Store. Maybe by adding a few mandatory patches to each project that improve compatibility. Maybe by making a much improved version of Git with a proper GUI interface. The possibilities are endless!
It may not be in the job description but usually somebody has to clean the data by hand or build specialized tools before it can be used.
Something as simple as a text field for entering a date can produce interesting effects. Even if your data looks good on the surface, when you dig in, you might find interesting things. Like data entered when the system was definitely shut down for maintenance.
Your rules are basically "the winner takes it all in the long run". This is similar to reality but real actors can disappear. Individuals have a limited lifespan. Their offspring have slightly different abilities. Corporations/Nations/Organizations are run by individuals (chosen not randomly) and may face technological/political challenges but here it's not clear that these structures need to disappear.
The things that are on schedule are one part but there are other things not on the schedule when you have scheduled a few days to do programming.
I find it hard to balance between being unavailable to my colleagues/users and being interrupted all the time. Often the most efficient way to solve a software problem is to just come to the developer and resolve it together in a few minutes. These interruptions happen at random though and are hard to plan. Some days there are none and other days there are people almost lining up.
I also suspect that the mind is able to go into a deeper state when it does not expect to be interrupted all the time. So not only the interruptions but also the expectation thereof is taking energy away. Some days when there is nothing going on I even miss the interruptions and even get the feeling of needing to actively stray away with my concentration.
I wish my company would have a hidden room where I could go with a laptop, disconnect everything and emerge only after the work of the day is done.
There is the 80 bit "long double" type that contains excess precision over the 64 bit double type. But if you want to write code that's both, portable, and reliable you have to turn off a lot of optimizations and use 32 or 64 bit types with standardised behavior.
They should have kept RAID behind yellow tape for years to come. There's just too many problems that can bite you once a physical disk fails and you really need that RAID to recover.
You misunderstood on the meta level. My point was that you want to use one feature of C++, you enable C++ to use this feature. Developer B wants to use ten other features. Developers C..Z want to use different features. Every feature by itself makes some sense in its context but in the end you're using so many different C++ features that no single developer knows them all. If you use modern C++ there are some ugly edge cases you have no idea they exist and if you use older C++ styles there is hell waiting for you.
The hard part is to select which features of C++ to use and more importantly which NOT to use and to ENFORCE these rules.
That's probably the whole point of it. Ask yourself daily: WWMD? "What Would Musk Do?"