VB Team is describing in parts
, how they write softwares at Microsoft. I liked the part about document templates:
It is funny that before I came here, I thought that Microsoft (being a huge company) is all about big piles of documentation and heavy processes, weird templates, etc. And you can’t blame me; many companies actually do have those processes, even companies way smaller than Microsoft. So I was really struck when I asked “So, what template should I follow?” and the answer was “Well, whatever works for you”. Of course, there are guidelines, but you aren’t forced to follow them.