From cded271787c9ac042e5e0c5feaa7d633e8a90b79 Mon Sep 17 00:00:00 2001 From: Charles-Axel Dein Date: Fri, 1 Jun 2018 11:33:27 +0200 Subject: [PATCH] Fix link to clean cheatsheet --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c8b491e..3cfb484 100644 --- a/README.md +++ b/README.md @@ -141,7 +141,7 @@ Biases don't only apply to hiring. For instance, the fundamental attribution bia * [Write code that is easy to delete, not easy to extend](http://programmingisterrible.com/post/139222674273/write-code-that-is-easy-to-delete-not-easy-to) * [Lessons learned writing highly available code](https://medium.com/imgur-engineering/lessons-learned-writing-highly-available-code-7eaf3d7aae00#.u7c4j6hac) * [The Ten Commandments of Egoless Programming](http://blog.codinghorror.com/the-ten-commandments-of-egoless-programming/) -* [Clean Code: A Handbook of Agile Software Craftsmanship](https://www.goodreads.com/book/show/3735293-clean-code) 📖, Robert C. Martin. Describes numerous useful best practices. A bit long. There's also a [clean code cheatsheet](./cheatsheets/Clean-Code-V2.4.pdf). +* [Clean Code: A Handbook of Agile Software Craftsmanship](https://www.goodreads.com/book/show/3735293-clean-code) 📖, Robert C. Martin. Describes numerous useful best practices. A bit long. There's also a [clean code cheatsheet](cheatsheets/Clean-Code-V2.4.pdf). ### Computer science @@ -259,7 +259,7 @@ resources](https://github.com/charlax/engineering-management). The best way to learn is to learn by doing. -* [danistefanovic/build-your-own-x: build your own (insert technology here)](https://github.com/danistefanovic/build-your-own-x) +* [danistefanovic/build-your-own-x: build your own (insert technology here)](https://github.com/danistefanovic/build-your-own-x) ### Incident response (alerting, outages, firefighting)