3 ms·
There are a bunch of comments in support of your viewpoint, so I'll put in a counter argument. People who have very good memories for lots of programming langua
by hn_throwaway_99 8y ago
There are a bunch of comments in support of your viewpoint, so I'll put in a counter argument. People who have very good memories for lots of programming language and API details are just faster, and faster does translate into higher productivity if you are indeed good at the other parts of your job.
For any programming language, I consider the following pretty essential APIs that you are going to use over and over:
1. Details of primitives and built-in "base" objects and related functions (e.g. strings, numbers, object literals, dates, etc.)
2. Collection libraries (arrays, dictionaries, sets, etc.)
3. Details of async libraries (e.g. in JS everything in Promise, how that applies to async/await).
4. Streaming libraries.
5. For OO languages, details around class creation/construction
6. Language specific details that are important (e.g. for Javascript I would put things like which values are falsy, Function prototype values like apply, bind, etc.)
7. Default common 'util' libraries, like lodash for JS and Apache commons for Java (not necessarily saying you know every single function, but you generally know which functionality groups are there).
Yes, you can look those up, but if you have a good memory for what the slice() function is and what you can do with it you will be faster than someone who has to look up the details every time you want to use it. In addition, knowing the general API surface means you know instantly what tools are available to you vs. what you'll need to create or get from an alternate library.
- zdragnar 8y agoAs a counter-counter argument, More time should be spent thinking than typing; specifically, reasoning through the problem domain and appropriate solutions. Having surface APIs memorized is going to save less time than having a well of experience to draw upon thinking through correct or best solutions. Beyond that, you identified a ton of areas of APIs that are useful to know, but if you understand the fundamentals behind the ideas (i.e. how to use arrays to solve problems, when to get a subset from them, how promises and futures differ from streams, etc) you're 90% of the way there. I think it's less about memorizing the API specific words and knowing the language of the paradigm. I might be splitting hairs a bit on that last point, since they're pretty closely related. But, I think a 10x developer is going to be better distinguished by knowing when to use a future vs. a stream, rather than simply knowing the API method names and signatures for a particular library / language.
- jogjayr 8y agoIn a corruption of a Steve Yegge saying, most programmers are CPU-bound rather than I/O-bound. Very rarely has my code typing speed inhibited my productivity. Understanding which problem I need to solve, and doing the research takes up the bulk of my programming time. Actually writing the code is a formality after that.
- dTal 8y agoI think you have to separate the I from the O. Output, i.e. typing, is not a bottleneck. Input, that is domain and API research, can be a huge one, especially if you're a "full-stack" or generalist engineer where task switches cause information to get swapped out all the time. If you only have to do a task once every few months, you're going to struggle with retention. 'CPU-bound' I would say is where you have all the pieces you need to solve a problem, but the precise solution is tricksy or math-heavy. Such problems are relatively rare in day-to-day programming. So I would say that on the contary, most programmers are I/O bound most of the time.
- seventhtiger 8y agoI don't think memorizing is to type faster. It's to think faster. CPUs speed up with more cache. Adding in a websearch/API lookup in-between thoughts will slow a programmer down.