5 ms·
The books recommended by Kay here are very much about DEPTH, not BREADTH. The majority of programming books are just ephemera and arcana and details that will
by jimbokun 7y ago
The books recommended by Kay here are very much about DEPTH, not BREADTH.
The majority of programming books are just ephemera and arcana and details that will be irrelevant in a year, or next month when the new version of the framework comes out.
Kay points to books, like the original Lisp Programming Manual, that will help you understand deep core concepts about computing itself, that will remain applicable no matter what framework or library you need to use tomorrow.
Take an Alan Kay, a McCarthy, Norvig, Abelson, Sussman, Armstrong, Steele, etc. from their prime and drop them into a software company where they have zero familiarity with the programming languages or tools currently being used, and within days or weeks they will be the most productive developer at that company by far. They will come up with simple, elegant, high performance and correct solutions to problems none of the other developers would have even considered.
Those are the kinds of thinkers you want to emulate, if you really want to write excellent software solving real problems in the shortest amount of time.
- neilv 7y agoIt doesn't even have to be "from their prime" (and I don't like to encourage that ageism concept, now that we have hiring managers fresh out of school). I'm comfortable asserting that, at any age, they will probably be high-value, having enough background to have insights and see connections that others cannot yet, now with a lot of general wisdom besides. See Danny Hillis's writeup on Feynman at Thinking Machines. You'd just need to offer them a compelling work situation, with problems that interest them.
- jimbokun 7y agoHeh, true, I just added "from their prime" because I know not all of them are still alive so would not add much to a development team in their current state.
- deleted 7y ago[deleted]
- yitianjian 7y agoYou never know, something like "The Hand of Alan Turing" might be a fairly decent draw for hiring
- davidw 7y agoI'm totally picturing The Hand treated like a relic in some Italian church, along these lines: https://www.atlasobscura.com/places/st-anthonys-tongue https://www.atlasobscura.com/places/st-anthonys-tongue
- GuiA 7y ago> You'd just need to offer them a compelling work situation, with problems that interest them. If you want to attract those kind of people and have them do their best work, then part of the “compelling work situation is to let them pursue their own problems. Alan Kay: ” I don’t run CDG, I visit it. [Xerox PARC founder Robert] Taylor didn’t want to hire anyone who needed to be managed. That’s not the way it works. I have people on my list who are already moving in great directions, according to their own inner visions. I didn’t have to explain to these people what they would be working on, because they already are. Bret Victor has already hired four people that I didn’t know about. I wanted people to fund, not manage.” https://www.fastcompany.com/3046437/5-steps-to-recreate-xerox-parcs-design-magic-from-the-guy-who-helped-make-it https://www.fastcompany.com/3046437/5-steps-to-recreate-xero...
- gabrielizaias 7y ago> to write excellent software solving real problems in the shortest amount of time. This should be on the wall of every developer's workplace.
- david927 7y ago> ephemera and arcana and details that will be irrelevant in a year Personally, I like this one.
- rubber_duck 7y agoThat sounds like JS developer mentality where you rewrite everything in a different framework every year so figuring stuff out in-depth is a waste of time and you just duct tape everything to get it working. Ephemera and arcana I've learned decade ago still serve me well today, even when it's outdated people mostly either reinvent stuff so I can recognise new stuff as a variation on an existing thing or build on previous solutions so I know the details and circumstances that lead to some developments and this lets me understand new things better as well (puts it in context).
- technofiend 7y ago>Ephemera and arcana I've learned decade ago still serve me well today, I think the usual back and forth about developer interviews may have this thought as an underlying assumption; specifically people who can solve a red/black tree on the whiteboard at the drop of a hat must be filled to the brim with useful but potentially obscure knowledge. (Obscure to those who haven't majored in CS or a related field.) It would be interesting to submit an ask hn "What is your so there I was doing x, y, z when being able to answer obscure interview question seventeen saved the day" story. (That's not well worded but you get the idea).
- reroute1 7y agoNo it sounds like bad development mentality in any language.
- 0x445442 7y agoAnd they all would have failed to get past the phone screen from the recruiter wanting to know how many years of experience they have had with "the XML" or "the Spring".
- Exuma 7y agoCan you give a concrete example of some topics it covers in breadth and how it would help me to read that book? FWIW I mostly program in ruby, go, elixir, and I program web apps.