Feynman doesn't say what, if anything, he told Webb, but it's an interesting backstory -- it's possible Webb knew more than this article suggests.
[1] https://books.google.com/books?id=_gA_DwAAQBAJ&pg=PT125&lpg=...
Feynman doesn't say what, if anything, he told Webb, but it's an interesting backstory -- it's possible Webb knew more than this article suggests.
[1] https://books.google.com/books?id=_gA_DwAAQBAJ&pg=PT125&lpg=...
(about setting up the IBM machines to perform calculations for the Manhattan Project)
"Well, Mr Frankel, who started this program, began to suffer from the computer disease that anybody who works with computers now knows about. It's a very serious disease and it interferes completely with the work. The trouble with computers is you play with them. They are so wonderful. [...] After a while the whole system broke down. Frankel wasn't paying any attention; he wasn't supervising anybody. The system was going very, very slowly-- while he was sitting in a room figuring out how to make one tabulator automatically print arctangent X [...] Absolutely useless! We had tables of arc-tangents. But you've ever worked with computers, you understand the disease-- the delight in being able to see how much you can do. But he got the disease for the first time, the poor fellow who invented the thing. I was asked to stop working on the stuff I was doing in my group and go down and take over the IBM group, and I tried to avoid the disease."
I try to keep this in mind when I'm working. I must admit I'm not very good at avoiding that disease.
However, when Texas Instruments released TI-Nspire CX, it was boycotted by the vast majority members from the hacking community because the system is locked down.
Some teachers and parents commented,
> "one thing that [...] is NOT wrong is TI's refusal to make the NSpire a platform for Doom or Quake or any other distraction that kids enjoy. These things may be fun, but they aren't about learning math"
I think it describes the same phenomenon.
Tinkering, fun, and being free to follow a stupid idea down a rabbit hole is how people learn and internalize stuff.
In middle school, a teacher showed us how to make a pythagorean theorem program, and I immediately saw the potential. When asked if it were possible to make a quadratic equation program, the teacher told me it couldn't be done. I had one written by the following day's math class, and I was hooked.
By high school, I was writing actual graphical games for the TI. I even taught friends so they could help contribute.
If it weren't for that freedom to explore, I would never have even gotten into software. And while pursuing my degree, I came to realize that my friends and I had "invented" some core programming concepts, things like hashing and basic cryptography (so no one would steal our game assets).
There was a really vibrant community on IRC and ticalc.org, which I was fortunate to find, because it was one of the only programming communities I know of at the time filled with people around my same age; it honestly changed my life. I wouldn't be where I am today without having found it.
Hmmmmmmmmmm
By 15yo, I was knee-deep in trying to make my own games. Final exams came, after which everyone's chatting about how they solved the math questions. "It was simple, I've used Pythagorean theorem", they'd say, and I rolled my eyes wondering how that applies. I said, "it was simple, I've used the formula for the length of a 2D vector, which is also the same for the distance between two points". They rolled their eyes wondering what I was talking about.
(It did click for me a couple moments later that the cool thing I've learned for my game programming goals was, in fact, derived from the Pythagorean theorem.)
Definitely not. On large scale, I own most of my career to that disease. On small scale, pretty much every job I got could be attributed to something that I learned through procrastination a year or two earlier.
Switched courses to design because my chemistry tutor kept telling me off for doodling on my notes. Got into web development was because I was bored at work and started learning HTML.
Trouble is, it means that whatever I’m doing is what I should be doing some point in the future, not what I actually need to do right now...
It is a disease in the same way that a painter or writer has a disease where he cannot stop painting or writing.
Frankly, I think those that have it should count themselves among the lucky ones.
Printing arctan tables sounds like a seminal example of a Advent of Code kind of problem, which have been known to nerd snipe countless programmers.
I've more than once caught myself lovingly perfecting some utility script when, really, I had some more important stuff I should've been focusing on.
The reason, of course, is that I'm getting that rewarding feeling of accomplishment on the script, when I know the feeling will be further out (or unattainable) on the Main Task.
Edit: But the 10% real work, I work real real hard :)