Explore >> Select a destination
|
You are here 
|
fsharpforfunandprofit.com | ||
| | | | |
codewithstyle.info
|
|
| | | | | With this post, I would like to start a short series about monads. If you are familiar with some functional programming techniques in JavaScript (such | |
| | | | |
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. | |
| | | | |
www.cppstories.com
|
|
| | | | | In this post we?ll have a look at new operations added to std::optional in C++23. These operations, inspired by functional programming concepts, offer a more concise and expressive way to work with optional values, reducing boilerplate and improving code readability. Let?s meet and_then(), transform() and or_else(), new member functions. Traditional Approach with if/else and optional C++20 In C++20 when you work with std::optional you have to rely heavily on conditional checks to ensure safe access to ... | |
| | | | |
nmn.gl
|
|
| | | Last Tuesday at 1 AM, I was debugging a critical production issue in my AI dev tool. As I dug through layers of functions, I suddenly realized - unlike the new generation of developers, I was grateful that I could actually understand my codebase. That's when I started thinking more about Karpathy's recent statements on vibe coding. For those who missed it, Andrej Karpathy recently shared his thoughts on what he calls "vibe coding" - essentially surrendering code comprehension to AI tools and hoping for the best. His exact words? "I 'Accept All' always, I don't read the diffs anymore." I have learnt a lot from Karpathy and use AI tools daily, but there's a world of difference between augmenting your capabilities and completely surrendering your understanding. | ||
