3 ms·
The code itself wasn't the hardest part, it was understanding all of the things that your code is ultimately talking to: databases, web browsers, HTTP, etc. Eac
by zachrose 8y ago
The code itself wasn't the hardest part, it was understanding all of the things that your code is ultimately talking to: databases, web browsers, HTTP, etc. Each of these has both a vast encyclopedic bundle of stuff to get fluent with and also an abstraction that you need to "grok."
These auxiliary abstractions were the hardest for me. Where "is" my the data in my database? Isn't it all files at the end of the day? Why can't I just use files? What does "stateless" mean in the context of HTTP, when clearly something is remembered when I log in? Circa 2009, why not do everything in JavaScript? (Ha!)