Merge pull request #4 from shaisachs/feature/amazon-links

add amazon links

_laws/brooks.md

@@ -3,10 +3,10 @@ layout: post
 title: Brooks's Law
 law: Adding [human resources] to a late software project makes it later.
 law-author: Fred Brooks
-law-url: https://www.indiebound.org/book/9780201835953
+law-url: https://www.amazon.com/Mythical-Man-Month-Software-Engineering-Anniversary/dp/0201835959?&_encoding=UTF8&tag=lawsofsoftwar-20&linkCode=ur2&linkId=175e9c6c1c8766c1ff56f05c2f7469e8&camp=1789&creative=9325
 law-year: 1975
 ---
 
-This law first appeared in a classic book, [The Mythical Man-Month](https://www.indiebound.org/book/9780201835953). The central insight is that new developers require onboarding, which in turn requires time of existing developers, which in turn subtracts time from ongoing projects. Hence, a word of caution for hapless managers who attempt to speed up a project which is running off the rails: adding new resources will only exacerbate the problem.
+This law first appeared in a classic book, [The Mythical Man-Month](https://www.amazon.com/Mythical-Man-Month-Software-Engineering-Anniversary/dp/0201835959?&_encoding=UTF8&tag=lawsofsoftwar-20&linkCode=ur2&linkId=175e9c6c1c8766c1ff56f05c2f7469e8&camp=1789&creative=9325). The central insight is that new developers require onboarding, which in turn requires time of existing developers, which in turn subtracts time from ongoing projects. Hence, a word of caution for hapless managers who attempt to speed up a project which is running off the rails: adding new resources will only exacerbate the problem.
 
 The qualifier "late" in the statement of the law is an important one. It suggests that human resources *can* be added to projects which are not late. Hence, for example, the success of some open source software projects, which successfully incorporate thousands of developers over the course of their lifetimes.

_laws/gall.md

@@ -3,7 +3,8 @@ layout: post
 title: Gall's Law
 law: A complex system that works has evolved from a simple system that worked. A complex system built from scratch won’t work.
 law-author: John Gall
-law-url: https://www.goodreads.com/book/show/583785.The_Systems_Bible
+law-url: https://www.amazon.com/SYSTEMANTICS-SYSTEMS-BIBLE-John-Gall-ebook/dp/B00AK1BIDM?&_encoding=UTF8&tag=lawsofsoftwar-20&linkCode=ur2&linkId=55d61fcdfabf182924a164860124a790&camp=1789&creative=9325
+ https://www.goodreads.com/book/show/583785.The_Systems_Bible
 law-year: 1975
 ---
 

_laws/hofstadter.md

@@ -3,8 +3,8 @@ layout: post
 title: Hofstadter's Law
 law: It always takes longer than you expect, even when you take into account Hofstadter's Law.
 law-author: Douglas Hofstadter
-law-url: https://www.indiebound.org/book/9780465026562
+law-url: https://www.amazon.com/G%C3%B6del-Escher-Bach-Eternal-Golden/dp/0465026567?&_encoding=UTF8&tag=lawsofsoftwar-20&linkCode=ur2&linkId=e1e23b12680c726714d88bff8af5af60&camp=1789&creative=9325
 law-year: 1979
 ---
 
-First coined in Hofstadter's book [Gödel, Escher, Bach](https://www.indiebound.org/book/9780465026562), this law nods at the difficulty of accurately estimating the length of software projects. It's self-referential in a way that Gödel especially would have appreciated. Indeed, advice to rising software managers commonly suggests adding a "buffer" to their estimates. This law suggests that the buffer will never be enough. Zawinski's Law may provide an explanation for this phenomenon: even when developers complete their tasks within the estimated time, software bloat will cause the project to expand and then overflow the buffer.
+First coined in Hofstadter's book [Gödel, Escher, Bach](https://www.amazon.com/G%C3%B6del-Escher-Bach-Eternal-Golden/dp/0465026567?&_encoding=UTF8&tag=lawsofsoftwar-20&linkCode=ur2&linkId=e1e23b12680c726714d88bff8af5af60&camp=1789&creative=9325), this law nods at the difficulty of accurately estimating the length of software projects. It's self-referential in a way that Gödel especially would have appreciated. Indeed, advice to rising software managers commonly suggests adding a "buffer" to their estimates. This law suggests that the buffer will never be enough. Zawinski's Law may provide an explanation for this phenomenon: even when developers complete their tasks within the estimated time, software bloat will cause the project to expand and then overflow the buffer.

_laws/kernighan.md

@@ -3,7 +3,7 @@ layout: post
 title: Kernighan's Law
 law: Everyone knows that debugging is twice as hard as writing a program in the first place. So if you’re as clever as you can be when you write it, how will you ever debug it?
 law-author: Brian Kernighan
-law-url: https://www.goodreads.com/book/show/454039.The_Elements_of_Programming_Style
+law-url: https://www.amazon.com/Elements-Programming-Style-2nd/dp/0070342075/?&_encoding=UTF8&tag=lawsofsoftwar-20&linkCode=ur2&linkId=39fc55b6042cc45ae5a739e6861b1a86&camp=1789&creative=9325
 law-year: 1974
 ---
 

_laws/linus.md

@@ -3,7 +3,7 @@ layout: post
 title: Linus's Law
 law: Given enough eyeballs, all bugs are shallow.
 law-author: Linus Trovalds
-law-url: http://www.catb.org/~esr/writings/cathedral-bazaar/
+law-url: https://www.amazon.com/Cathedral-Bazaar-Musings-Accidental-Revolutionary/dp/0596001088?&_encoding=UTF8&tag=lawsofsoftwar-20&linkCode=ur2&linkId=f6fd5393e16732fd608e42e74fa05f4d&camp=1789&creative=9325
 law-year: 1999
 ---
 

_laws/peter-principle.md

@@ -3,7 +3,7 @@ layout: post
 title: Peter Principle
 law: People in a hierarchy tend to rise to "a level of respective incompetence."
 law-author: Laurence J. Peter
-law-url: https://www.indiebound.org/book/9780062092069
+law-url: https://www.amazon.com/Peter-Principle-Things-Always-Wrong-ebook/dp/B00IRCZHXI/?&_encoding=UTF8&tag=lawsofsoftwar-20&linkCode=ur2&linkId=5fdaa1952a35093fddd09bc1d693482a&camp=1789&creative=9325
 law-year: 1969
 ---