by cipher0 on 9/20/14, 5:45 AM with 6 comments
by mathattack on 9/20/14, 11:56 PM
by klibertp on 9/20/14, 9:56 PM
by commentei29 on 9/20/14, 8:45 PM
8.)What a shame. the evidence of the Heartbleed Bug that broke the internet is on git. One way to find the BLAME is git blame. What are the other THREE WAYS???
9.)IMHO, it is NOT an EVIDENCE database. Provide evidence and a few toolsets.
10.)Even simple metrics like WHAT IS THE TREND LINE MOVING CHART like yahoo finance stocks for 'changes', BUGS, vulnerabilities and HEAT MAP - changes.
11.)Heat map changes? a.) Coder stated design b.)goals and constraints c.)code diff d.)code metrics - EVIDENCE e.)code analytics - EVIDENCE f.)redditc snarky comments - sometimes evidence g.)....
No, the evidence does NOT have to be extreme detail, however the test framework: S M A R T S for specific - related to ontology or BoK or ??? or ?? scrum? is needed. Haskell wording is VAGUE, context specific, scoping?, strange logic - Template Haskell and Liquid, etc., etc.
haskell is an example. Engineering is the middle layer between the hacker - anything goes technically to the Science and then to the Math.