4 ms·
If you didn't develop in that timeframe you might not get the difference between then and today. It takes forever to look things up so you end up memorizing ins
by thoughtsimple 8y ago
If you didn't develop in that timeframe you might not get the difference between then and today. It takes forever to look things up so you end up memorizing instead. And it isn't a big deal because the number of things needed to be a successful software developer wasn't that great. To be successful and finish projects more or less on time, memorization was needed.
Edit: For example, for a different project I knew the hex codes for every 8051 instruction. This was necessary to be successful debugging using a logic analyzer. Looking up each op-code would be prohibitively slow.
- AnIdiotOnTheNet 8y agoIt's a caching problem. If memory access is slow you want to cache more, if not then you don't bother. Things you use a lot will spend more time in the cache, things you don't you'll have to keep retrieving from memory. We really aren't as different from computers as we sometimes like to believe.