sansguidon/bookmarks
1
0
Fork 0
Code Issues 16 Pull Requests 1 Packages Projects 1 Releases Activity

(2018) Just-In-Case vs. Just-In-Time Learning

Browse Source
This commit is contained in:
Morgan 2018-09-08 11:06:16 +02:00 committed by GitHub
parent 82e481879b
commit 832b553ca7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@ -4677,6 +4677,7 @@ Raw
> 2. programmers are most effective when they avoid writing code > 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.” > 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. > 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 ## Programmer humor
* [CommitStrip](http://www.commitstrip.com/en) - daily life of developers * [CommitStrip](http://www.commitstrip.com/en) - daily life of developers