Tangential: Peter Naur has something to say about this in his "Programming as Theory Building" paper. TL;DR: You have to reimplement the application or features to understand the "why" regarding technical decisions.
I don't know any books or course about the subject. I can only share my personal approach. This is something I've learned in the context of breaking down potential client projects into early plans and estimatable…
Such an excellent paper.
The concept is called 'tacit knowledge'.
As someone who teaches Human-Computer Interaction in a CS program, I find it odd that there are no HCI topics on that list. Especially, when they say it's a "complete education in computer science". Perhaps it's a…
When HN goes ad hominem I usually bookmark whatever HN got riled up about to read later. It's a sign that there's something interesting to think about ;)
Can you point me to any sources on the history of Office 97 (or other earlier applications) development?
Tangential: Peter Naur has something to say about this in his "Programming as Theory Building" paper. TL;DR: You have to reimplement the application or features to understand the "why" regarding technical decisions.
I don't know any books or course about the subject. I can only share my personal approach. This is something I've learned in the context of breaking down potential client projects into early plans and estimatable…
Such an excellent paper.
The concept is called 'tacit knowledge'.
As someone who teaches Human-Computer Interaction in a CS program, I find it odd that there are no HCI topics on that list. Especially, when they say it's a "complete education in computer science". Perhaps it's a…
When HN goes ad hominem I usually bookmark whatever HN got riled up about to read later. It's a sign that there's something interesting to think about ;)
Can you point me to any sources on the history of Office 97 (or other earlier applications) development?