Explore >> Select a destination
|
You are here 
|
arunrocks.com | ||
| | | | |
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. | |
| | | | |
zerokspot.com
|
|
| | | | | ||
| | | | |
explaining.software
|
|
| | | | | Confronted with this dissonance, this ugliness, we inevitably gesture towards a better future. | |
| | | | |
lifeofaudrey.com
|
|
| | | [AI summary] The post discusses the evolution of the free/open source software movement, highlighting its historical development, challenges like sustainability and diversity, and potential solutions for the future. | ||
