Explore >> Select a destination
|
You are here 
|
ericniebler.com | ||
| | | | |
www.kuniga.me
|
|
| | | | | NP-Incompleteness: | |
| | | | |
www.reedbeta.com
|
|
| | | | | Pixels and polygons and shaders, oh my! | |
| | | | |
jguegant.github.io
|
|
| | | | | Trivia: As a C++ enthusiast, I usually follow the annual C++ conference cppconf or at least try to keep myself up-to-date with the major events that happen there. One way to catch up, if you can't afford a plane ticket or the ticket, is to follow the youtube channel dedicated ... | |
| | | | |
mbuffett.com
|
|
| | | The Commonplace blog has been writing a lot on tacit knowledge recently. As someone who's been programming for a long time (8ish years), these articles resonated deeply. I won't go into too much detail what tacit knowledge is about, since the above posts do such a good job with it. If you're not familiar, check them out. Explicit knowledge vs tacit knowledge Essentially, explicit knowledge is that which can be transferred verbally. For example, I could tell someone the method name for pushing to an array in JavaScript, what version of Python print went from a keyword to a function, and the range of HTTP status codes that represent success. Maybe they'd need to do some spaced repetition learning or something, but they can just memorize these bits. | ||
