Re:Why I close pull requests
by dismantlethesun on Thursday December 29, 2016 @12:34AM
(#13275816)
I thought design documents and reporting were mandatory for 'engineering'. As is things like ethics, and organizational standards, and testability.
Move fast and break something is the domain of hacking.
If it produces results, does it matter whether you call it "engineering" or "hacking"?
It depends on the result. If the result is public embarrassment of the company and the loss of millions in market worth? If the result is someone dying?
Do you have any actual evidence that a culture of design documents and signoffs produces code with fewer vulnerabilities?
Re:Why I close pull requests
by user5994461 on Thursday December 29, 2016 @10:22PM
(#13282257)
How to make flawless software that goes into space => A truckload of process and design documents. https://www.fastcompany.com/28121/they-write-right-stuff
Whatever software is made, the [lack of] efforts put in design and reviews will have high impact on quality [or lack thereof].
Re:Why I close pull requests
by stinkytaco on Tuesday January 03, 2017 @05:13PM
(#13313644)
I didn't mean it to offend, just to emphasize that though the poster may feel it affronts his "engineering dignity" (his words) to write design documents, there are others in the chain who have to deal with the fallout from that.
Wow. I feel terribly offended as an engineer.
Could we not confuse "engineering" with "pushing random changes at any times that may not even pass the tests by any bro-ninja that just felt like it".
The poster has clearly never written or maintained any critical software.