Explore >> Select a destination
|
You are here 
|
arunrocks.com | ||
| | | | |
explaining.software
|
|
| | | | | Confronted with this dissonance, this ugliness, we inevitably gesture towards a better future. | |
| | | | |
blog.codingconfessions.com
|
|
| | | | | Exploring the concurrency, debugging, and performance upgrades that make Python 3.14 special. | |
| | | | |
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. | |
| | | | |
tutorial.ponylang.io
|
|
| | | A tutorial for the Pony programming language. | ||
