[HN Gopher] Code with Engineering Playbook
       ___________________________________________________________________
        
       Code with Engineering Playbook
        
       Author : nrsapt
       Score  : 72 points
       Date   : 2021-11-27 15:46 UTC (7 hours ago)
        
 (HTM) web link (microsoft.github.io)
 (TXT) w3m dump (microsoft.github.io)
        
       | noen wrote:
       | This was written by the organization I used to work for in
       | Microsoft. It was developed over the last 6 years by the
       | Commercial Software Engineering organization through hundreds of
       | real, production ready, engineering engagements with Microsoft
       | customers and partners.
       | 
       | There's nothing groundbreaking for seasoned engineers but it
       | serves as a very robust set of reminders, especially the
       | secondary and tertiary elements that often fall off when projects
       | get stressed to move faster/cheaper/more featured.
       | 
       | Also important that this isn't Microsoft's home grown process -
       | rather an amalgamation of working with hundreds of companies -
       | some tech companies, many not - with wide ranges of software
       | engineering maturity. It's also written and maintained by the
       | engineers directly and with a singular purpose. No marketing, no
       | fluff, no technology or vendor implementations.
        
       | rationalfaith wrote:
       | Good stuff! Always good to see how the big players do it!
        
       | iou wrote:
       | As much as one could "nitpick" about ommisions or unnecessary
       | points, for large companies these things are obvious yet
       | necessary.
       | 
       | I also liked the writing style guides that Microsoft and Google
       | put out in recent years:
       | 
       | - https://docs.microsoft.com/en-us/teamblog/style-guide
       | 
       | - https://developers.google.com/style/highlights
        
         | TeeMassive wrote:
         | Too bad Google is going woke
         | https://developers.google.com/style/inclusive-documentation#...
        
         | rationalfaith wrote:
         | Thanks for that! Definitely giving it a read as I want to make
         | my writing quality more consistent.
        
       | davedx wrote:
       | Lots of good stuff in there. One that caught my eye is "able to
       | change logging level without code changes". I would take that one
       | step further to "without redeploying". Going to try and implement
       | that in my own projects.
       | 
       | I disagree strongly with "90%+ unit test coverage" though.
       | Diminishing returns are very real there.
        
         | spyremeown wrote:
         | >I disagree strongly with "90%+ unit test coverage" though.
         | Diminishing returns are very real there.
         | 
         | Hi, stupid junior here. Can you elaborate a bit or give me some
         | reading material? I'm currently struggling to get good
         | practices with tests and understanding associated metrics.
         | Thank you!
        
       ___________________________________________________________________
       (page generated 2021-11-27 23:00 UTC)