5 ms·
I’m interested to know what are common epiphanies for developers. For me, I can remember: - objects are closures and closures are objects - properly getting t
by bambataa 5y ago
I’m interested to know what are common epiphanies for developers.
For me, I can remember:
- objects are closures and closures are objects
- properly getting the JS asynchrony model
- pointers and the whole memory addressing model
- HTTP being stateless
I must have had an early epiphany with function return values, since I remember not writing functions correctly at first, but I don’t remember the actual epiphany.
- junon 5y agoI don't remember specifically what it was as I started quite young, but especially starting out there were a couple of major "lightswitch flipped on" a-ha moments like that. I think realizing that execution in imperative languages was one after the other and that there's a sort of "cursor" that goes through the code (execution flow/instruction pointer/whatever) was one of the first things that made things click. I miss them, as they were incredibly endorphin-releasing moments.
- whartung 5y agoFor me the big 3 were arrays, dynamic memory, and lambda/closures. But I must admit, the day I saw a guy run, essentially, "cpio ... | rsh otherhost cat > /dev/tape", that was a very "aha" moment in terms of overall system design and what networking brought to the table.