From 1b7ecd884894d1ecd7af0d15ccc69947c07add0e Mon Sep 17 00:00:00 2001 From: Charles-Axel Dein Date: Wed, 22 Jun 2016 16:54:47 +0200 Subject: [PATCH] Add configration bias --- README.md | 6 ++++-- glossary.md | 12 ++++++++++++ 2 files changed, 16 insertions(+), 2 deletions(-) create mode 100644 glossary.md diff --git a/README.md b/README.md index 0ce05b2..d07fd09 100644 --- a/README.md +++ b/README.md @@ -85,6 +85,7 @@ I've found these books incredibly inspiring: * [System design interview for IT company](https://github.com/checkcheckzz/system-design-interview) * [Technical Interview Megarepo](https://github.com/jdsutton/Technical-Interview-Megarepo): study materials for SE/CS technical interviews * [How to Win the Coding Interview](https://blog.devmastery.com/how-to-win-the-coding-interview-71ae7102d685#.16ph6bp5y) +* [The elevator programming game](http://play.elevatorsaga.com/) ### Managing the database @@ -105,8 +106,9 @@ I've found these books incredibly inspiring: ### Testing -* [Testing Strategies in a Microservices -Architecture](http://martinfowler.com/articles/microservice-testing/) (Martin Fowler) is an awesome resources explaining how to test a service properly. +* [Testing Strategies in a Microservices Architecture](http://martinfowler.com/articles/microservice-testing/) (Martin Fowler) is an awesome resources explaining how to test a service properly. +* [A Quick Puzzle to Test Your Problem Solving](http://www.nytimes.com/interactive/2015/07/03/upshot/a-quick-puzzle-to-test-your-problem-solving.html?_r=0)... and a great way to learn about confirmation bias and why you're mostly writing positive test cases. + ### Writing for performance diff --git a/glossary.md b/glossary.md new file mode 100644 index 0000000..9ba89c4 --- /dev/null +++ b/glossary.md @@ -0,0 +1,12 @@ + + +# Table of Contents + +- [Glossary](#glossary) + + + +# Glossary + +* **Stability** is the sensitivity to change of a given system that is the negative impact that may be caused by system changes ([ISO/IEC 9126 standard on evaluating software quality](https://en.wikipedia.org/wiki/ISO/IEC_9126)). +* **Reliability** is made of maturity (frequency of failure in software), fault tolerance (ability to withstand failure) and recoverability (ability to bring back a failed system to full operation) ([ISO/IEC 9126 standard on evaluating software quality](https://en.wikipedia.org/wiki/ISO/IEC_9126)). \ No newline at end of file