Reply to thread

Message

<blockquote data-quote="ForgottenSeer 58943" data-source="post: 825340">Windows is a mess. It&#039;s touched by 10,000 people in compartmentalized environments that often have no idea what someone else is doing. Often some of the programs are written to fix some integration between departments that didn&#039;t work right. So a program to fix another program.The left hand has no idea what the right is doing the majority of the time with Microsoft. Each branch comes together in a &#039;ceremony&#039; (code merge, etc), then the discovery is made about what doesn&#039;t work, and what has to be done to make it work. Yes, sometimes that means someone has to write something new to run in between to make the code merge work.A guy I knew that was a lead there said it&#039;s the messiest code and most convoluted, top heavy organization he&#039;s ever seen, and he worked all around the world.So if you poke around,&nbsp; you&#039;ll find so many things you&#039;ll waste days looking up each one.</blockquote>

[QUOTE="ForgottenSeer 58943, post: 825340"] Windows is a mess. It's touched by 10,000 people in compartmentalized environments that often have no idea what someone else is doing. Often some of the programs are written to fix some integration between departments that didn't work right. So a program to fix another program. The left hand has no idea what the right is doing the majority of the time with Microsoft. Each branch comes together in a 'ceremony' (code merge, etc), then the discovery is made about what doesn't work, and what has to be done to make it work. Yes, sometimes that means someone has to write something new to run in between to make the code merge work. A guy I knew that was a lead there said it's the messiest code and most convoluted, top heavy organization he's ever seen, and he worked all around the world. So if you poke around, you'll find so many things you'll waste days looking up each one. [/QUOTE]

Verification