From 832b553ca7e48cc34fdf24c27389a4df612bc8ab Mon Sep 17 00:00:00 2001 From: Morgan Date: Sat, 8 Sep 2018 11:06:16 +0200 Subject: [PATCH] (2018) Just-In-Case vs. Just-In-Time Learning --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 11348ab..9b60c75 100644 --- a/README.md +++ b/README.md @@ -4677,6 +4677,7 @@ Raw > 2. programmers are most effective when they avoid writing code > 3. when they are being their most productive, nobody says “Wow! You were just 100x more productive than if you’d done this the hard way. You deserve a raise.” > 4. it may take a long time to realize that others are programming with sound and fury but producing nothing. +* [Osman (Ozzie) Ahmed Osman](https://hackernoon.com/just-in-case-vs-just-in-time-learning-c87f61d24360) - (2018) Just-In-Case vs. Just-In-Time Learning | Should software engineers learn new things “just in case” we need them in the future? Or should we learn the things we need “just in time”, when we realize we actually need them? ## Programmer humor * [CommitStrip](http://www.commitstrip.com/en) - daily life of developers