133 karma · joined February 3, 2009
// This code is pretty dense so I recommend you read the documentation first
Some months later I found a follow-up comment left by a fellow dev:
// Or you could just give up now
From the article:
"... economic and professional success exists on the surface of life, and that they emerge out of interpersonal relationships, which are much deeper and more important."
The situation seems ripe for a disruptive technology to emerge.
Furthermore, it will disrupt numerous markets: portable DVD players, GPS units, PDAs, laptops, industry-specific bespoke mobile platforms (what is that thingy the UPS guy uses?), control systems, newspapers, magazines, you get the idea. Anything less would not be worth Apple's time.
The code is the design. What other deliverable of the software development process contains the precision and specificity of a blueprint, which can then be followed to actually build (the double entendre is no coincidence) the thing?
A contractor equates to a compiler, albeit an expensive, time-consuming, and buggy one.
I don't think clients are so much to blame... it's just that software is so abstract and a house so, shall we say, concrete. We need to do a better job of helping clients understand and visualize what we are doing.
By the way, I'm proud to have originated the wikiHow guide cited in the article, nearly 3 years ago ;)
I once had a boss who was brilliant at learning other people's idiolect and then speaking it back to them. He never failed to get his point across.
I'm not an entrepreneurial hacker like so many on this site (wish I was). My job offers great opportunities to craft creative solutions to interesting technical problems, but I am far too disconnected from those who will ultimately benefit from my efforts. This disconnectedness really takes the interestingness out of solving interesting problems.
By the way, if anyone knows of a list of manual trades well suited to hackers, please post it here.
Recommended reading: Wendell Berry: _What Are People For?_
'Science' is just a fancy word for knowledge. We don't come to know our best friends, our mothers, our bosses, through the so-called scientific method. Nor do criminal investigators solve tough cases through exclusively empirical means. Would you ask a hung jury to just be scientific about things, and the answer will become clear?
Perhaps a small New England state could pull it off (and they do try) but to engineer a Dutch system from Washington is asking a bit much. The author perceptively observed that Dutch don't trust government any more than we do, but have a strong sense of communal responsibility to each other. That is only possible on a small scale, I think. After all, they only have 16m people on a tiny piece of land.
When I lived in Holland some years ago, one of locals pointed out this irony: "You Americans have only two political parties but can't agree on anything, while we Dutch have dozens but pretty much see eye-to-eye on everything."
Maybe I'm just ignorant, but I've found it necessary to use CSS, tables, & JavaScript (yes, all three) to produce acceptable dynamic layouts for web-based apps. This is unfortunate.