4 ms·
I used to program with 6 thick reference books around me. Has memorizing SDKs, APIs, libraries ever been a thing? Or is this just the daily "everything is bad n
by paxys 6y ago
I used to program with 6 thick reference books around me. Has memorizing SDKs, APIs, libraries ever been a thing? Or is this just the daily "everything is bad nowadays" post?
- azhenley 6y agoEvery interview I’ve done required me to have everything memorized, so it seems this is very much a thing.
- tutfbhuf 6y agoBut then it's rather a problem with the interview itself.
- bennyp101 6y agoI had an online interview last year, and it was basically me coding up as they supplied the criteria (in PHP). For the life of me, I couldn't remember how to use array_column, but I knew that was what I needed to use. They basically said "errr, you could just look it up?" - like, it was obvious that the interview was more about what you knew, and how to do things, rather than can you remember every little thing from ever about your job that you don't use day in day out.
- jermaustin1 6y agoGetting a simple application up and running shouldn't be that difficult without scouring reference guides if it is a thing you do. The number of times I google how to do the thing I'm supposed to do is relatively low, but the number of times I have to google how to fix something that has come up AFTER I did the thing I was doing is probably 90+% of my googling.
- mywittyname 6y agoBack in the days of PHP, I could develop web apps without references for the most part, using a simple text editor. It's a pretty similar story with Python too, unless I'm using Pandas, I generally don't use reference material much. Today with node/angular, I'm generally leaning on Google (well DDG) pretty heavily throughout the day. Web platforms seem substantially more complicated today than they used to be. Then again, maybe the mid-aughts was the golden age of programming.
- rzzzt 6y agoI read Python and PHP's offline .CHM files, and was quite happy with the level of information contained there.
- paxys 6y agoPHP in fact had one of the first large online dev & documentation communities. A huge chunk of the web was built with multiple tabs of php.net open looking up which string length function to use.
- strictnein 6y agoYeah, I was just thinking of how every developers cube used to have stacks of books and binders of CDs from MSDN.
- kube-system 6y agoThink about the days before the internet. Was there any technical profession where you'd find offices without lots of books?
- t8e56vd4ih 6y agoyou name it ... looking something up in a book takes much more effort than just googling. that's why there was a stronger incentive to memorize.
- Too 6y agoBack in the days i would open an editor and start with <?php...?><html><head>, and it would immediately show at least something in the browser. The rest was open to creativity. Adding libraries was only needed when adding features. Today on day one i would go: wtf is this Babel thing and how do i configure it so that Angular work together with SASS and is npm compatible with this version of Typescript? Which reactor pattern is flavor of the month and what stupid parameter was needed to make the router work? I hardly even know which files are shipped to the browser anymore after all Webpack preprocessing. But once you actually have the setup in place, i have to admit the modern experience is a lot more productive and powerful. It's just that every time you have to start a new project or touch anything related to the build-process your soul dies inside. There are too much gunk just built on top and on top of each other, instead of replacing the whole stack, and thanks to leaky abstractions you have to understand at least something throughout every layer of the rotten cake. There are a lot of scaffolding-scripts available, like Vue-cli, helping you to do all of this but imo they just add even more to the problem, now you got yet another layer of crap to crawl through and it prevents you from actually learning the real layer underneath.