Explore >> Select a destination
|
You are here 
|
arunrocks.com | ||
| | | | |
www.mattlayman.com
|
|
| | | | | A review of "Dreaming in Code" | |
| | | | |
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. | |
| | | | |
boxbase.org
|
|
| | | | | I came up with an idea when studying type theory. I am a vehement proponent of dynamic typing but there are several ideas that require me to explore into type theory so I am studying it. | |
| | | | |
dominickm.com
|
|
| | | Dependency management in software development is often akin to playing an elaborate game of Jenga where everyone involved is on their third IPA: every block you move introduces the risk of toppling the tower which is becoming more wobbly over time. Complexity Unchained Python prides itself on simplicity and readability, but as soon as you [...] | ||
