3 ms·
I'm going to quote the majority of an entire section of Guo's post because it (a) demonstrates what I believe to be the core of his problem, and (b) is incredib
by mcguire 12y ago
I'm going to quote the majority of an entire section of Guo's post because it (a) demonstrates what I believe to be the core of his problem, and (b) is incredibly offensive to me as a computing professional:
"Here is a common productivity bottleneck faced by students working on applied computer science research:
"1. Advisor and student discuss high-level research ideas by doodling on the whiteboard. Awesomeness ensues.
"2. Student leaves advisor's office feeling pumped and knowing exactly what they need to do to implement those ideas in code.
"3. Student tries to get started on programming but immediately gets stuck since they don't know how to handle all of the command-line bullshittery required to set up their coding environment with the proper libraries, tools, and frameworks.
"Many students get discouraged and turned off from research when they hit the wall in step 3.
"There is a huge disconnect between the elegant high-level ideas discussed on the whiteboard (while presumably sipping cappuccinos) and the grimy, grungy, terrible command-line bullshittery required to set up a computing environment suitable for implementing those ideas in code. This gulf of execution is tremendously frustrating for highly-capable and motivated students who just didn't happen to spend 10,000 hours of their youth wrestling with nasty command-line interfaces."
If I were to try to write a summary of this complaint, I believe I would have to boil it down to, "Useful work is indeed often difficult."
I'm certain the HN community is familiar with the concept that ideas are a dime a dozen, that execution is indeed the important part. I'm also certain a significant chunk of the readership has also spent "10,000 hours of their youth wrestling with nasty command-line interfaces", by which I mean "has learned the fundamentals of how computers work" and "has spent some time understanding how to use their tools."
So along comes Philip Guo, who has, in his career, developed the ability to convert whiteboard doodles to working prototypes (I'll withhold my rant about academic quality code for today). Now, however, he's in the position of every developer promoted to management: he has whiteboard doodles that he would like his loyal minions to convert to functioning code and his minions are having difficulties. And, like almost every other recent promotee, he blames the tools involved. Because, after all, "this bullshit is not intellectually interesting in any way", at least to him; he's only interested in the whiteboard awesomeness, after all.
Programming is difficult. Guo knows this. The tools could be better. (Are there significantly better tools out there than "command-line bullshit"? Not that I'm aware of. Maybe the Plan 9 stuff, Acme, etc., but that comes with its own stack of bullshit and a reduced environment to boot.) But is actually learning to program really incidental complexity? Is it really "bullshit"?
- pessimizer 12y agoIt isn't offensive to me in any way as a computing professional. It's exactly what happened to me in college. "Programming is difficult. Guo knows this. The tools could be better. (Are there significantly better tools out there than 'command-line bullshit'? Not that I'm aware of. Maybe the Plan 9 stuff, Acme, etc., but that comes with its own stack of bullshit and a reduced environment to boot.) But is actually learning to program really incidental complexity? Is it really 'bullshit'?" Command-line bullshit has little to nothing to do with programming.
- Rusky 12y agoThe problem is not that programming or "useful work" is difficult. The problem is that getting your environment to the point of being able to do "useful work" is more complex than it needs to be. The problem is exactly that, as you say, "the tools could be better." The various parts of the system don't work together well enough. The installation process requires understanding systems that shouldn't even need to exist.