A
Amy Ko
blogs.uw.edu · Personal blog · on HN since 2012
Amy Ko, a University of Washington researcher, writes on programming languages, software engineering research and how people use programming tools.
What HN saysHN links it for her write-up of John Carmack's software engineering talk, and commenters use it to debate Carmack's views and the case for math.
18HN people shared it
3linked it in comments
16stories submitted
822story points
5 years agolast shared
2012people per year2026
Most-shared posts
- 1John Carmack discusses the art and science of software engineering11 people · 564 points · first shared 2012 · 71 comments on HN
- 2Programming Languages are the Least Usable, but Most Powerful User Interfaces3 people · 138 points · first shared 2014 · 100 comments on HN
- 3The black hole of software engineering research (2015)2 people · 114 points · first shared 2015 · 69 comments on HN
- 4Making money versus making knowledge1 people · 3 points · first shared 2016 · discussion on HN
- 5My sabbatical research pivot1 people · 2 points · first shared 2016 · 1 comments on HN
- 6My Splash 2016 Keynote: A human view of programming languages1 people · 1 points · first shared 2021 · discussion on HN
What HN people wrote when they linked it
Joeri · 2014-09-05
He is also by his own admission still learning about programming:
On the software development side, you know there was an interesting thing at E3, one of the interviews I gave, I had mentioned something about how I’ve been learning a whole lot, and I’m a better programmer now than I was a year ago and the interviewer expressed a lot of surprise at that, you know after 20 years and going through all of this that you’d have it all figured out by now, but I actually have been learning quite a bit about software development, both on the personal craftsman level but also paying more attention by what it means on the team dynamics side of things.
https://blogs.uw.edu/ajko/2012/08/22/john-carmack-discusses-the-art-an…
gtani · 2013-01-15
He sort of alluded to it, but there's the usual perceived tooling/ retraining/hiring / performance ceiling issues for shops with > N devs, N somewhere between 5 and 25 (I don't agree with his arguments, just repeating them)
http://gamasutra.com/view/news/169296/Indepth_Functional_programming_i…
http://www.reddit.com/r/haskell/comments/jap3x/im_very_tempted_to_want…
http://blogs.uw.edu/ajko/2012/08/22/john-carmack-discusses-the-art-and…
ThatMightBePaul · 2015-06-12
I agree the next gen needs Math. Not for the reasons in this article, though.
John Carmack's 2012 QuakeCon speech is almost a direct rebuke:
https://blogs.uw.edu/ajko/2012/08/22/john-carmack-discusses-the-art-an…
In reality in computer science, just about the only thing that’s really science is when you’re talking about algorithms. And optimization is an engineering. But those don’t actually occupy that much of the total time spent programming. You know, we have a few programmers that spend a lot of time on optimizing and some of the selecting of algorithms on there, but 90% of the programmers are doing programming work to make things happen. And when I start to look at what’s really happening in all of these, there really is no science and engineering and objectivity to most of these tasks. You know, one of the programmers actually says that he does a lot of monkey programming—you know beating on things and making stuff happen. And I, you know we like to think that we can be smart engineers about this, that there are objective ways to make good software, but as I’ve been looking at this more and more, it’s been striking to me how much that really isn’t the case.
Aside from these that we can measure, that we can measure and reproduce, which is the essence of science to be able to measure something, reproduce it, make an estimation and test that, and we get that on optimization and…