quick review. my opinion can change. THUMBS DOWN. 1 out of 5 stars.
why? remember I am not as smart other disclaimers.
THIS IS THE METHOD I AM USING after 38 or so years and yes I have
dropped the box with Fortran punch cards. OOPS.
1.)it a human process - worthless.
2.)only human process worth while in REAL time is this site and reddit dot
com / haskell, etc.
3.)where is the ontology?
4.)i also provide real perspective by
a.)rosetta code - go ahead and laugh but code translation is helpful
especially between OOP python, C and FP Haskell
b.)encylopedia of int sequences. Help me find more mistakes in the
int sequences for I so far CANNOT FIND ANY.
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.
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.