3 ms·

> There will be an increasingly important history component in comp sci., software engineering, infosec, and associated fields. Much as I'd like that, I disagr

> There will be an increasingly important history component in comp sci., software engineering, infosec, and associated fields. Much as I'd like that, I disagree. The momentum has always been against that. We're members of a cult of the new, which does not value or even acknowledge the old. Which is why we keep reinventing the same solutions but with different tech stacks. This drives developer value down which drives developer salaries down, so I don't see it changing. FWIW, my history of math class as an undergrad was a math elective that almost nobody else took. Other math students didn't want to learn history and other history students didn't want math. And the curriculum stopped at the 18th century, before things got really interesting.

robertlagrant 3y ago
> We're members of a cult of the new, which does not value or even acknowledge the old This just isn't true. We have Heartbleed because we refuse to move off how we wrote software 30 years ago[0]. HTTP was invented in the 1980s[1]. REST in 2000[2]. TCP/IP in the 1980s[3]. Ethernet the same[4]. I'm pretty sure we acknowledge and value all of those things. Our field, depending on how you define it, is only about 70 years old. Those things are pretty old in those terms. [0] https://queue.acm.org/detail.cfm?id=3212479 https://queue.acm.org/detail.cfm?id=3212479 [1] https://en.wikipedia.org/wiki/HTTP https://en.wikipedia.org/wiki/HTTP [2] https://ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm https://ics.uci.edu/~fielding/pubs/dissertation/rest_arch_st... [3] https://en.wikipedia.org/wiki/Internet_protocol_suite#Adoption https://en.wikipedia.org/wiki/Internet_protocol_suite#Adopti... [4] https://en.wikipedia.org/wiki/Ethernet https://en.wikipedia.org/wiki/Ethernet