From 4ddb434d8bcfb6738460c5a176ecaa999252f396 Mon Sep 17 00:00:00 2001 From: Morgan Date: Tue, 18 Jan 2022 11:00:04 +0100 Subject: [PATCH] How to write software that works for decades --- sections/programming.md | 1 + 1 file changed, 1 insertion(+) diff --git a/sections/programming.md b/sections/programming.md index 7f1cec3..d72c0c8 100644 --- a/sections/programming.md +++ b/sections/programming.md @@ -1756,6 +1756,7 @@ See also [Dotfiles / Aliases](#dotfiles--aliases) and [Shell aliases](../README. * [kettanaito/naming-cheatsheet](https://github.com/kettanaito/naming-cheatsheet) - Comprehensive language-agnostic guidelines on variables naming. Home of the A/HC/LC pattern. * [Yossi Kreinin aka wetware](https://yosefk.com/blog/10x-more-selective.html) - (2013) 10x more selective > So I believe, having authored a lot of code that went down the toilet, that you don't get productive by working as much as by not working – not on stuff that is likely to get thrown away. +* [Unix Sheikh](https://www.unixsheikh.com/articles/how-to-write-software-than-will-keep-working-for-decades.html) - (2021) How to write software than will keep working for decades without problems > Tools * [Devhints](https://devhints.io/) - Rico's cheatsheets | TL;DR for developer documentation