704 karma · joined February 26, 2008
http://lifehacker.com/software/mac-tip/display-the-date-on-t...
The usual technique for evaluating something is to compare it to its competitors, and some of those are functional!
One of the bad things about PHP is that it lacks the higher-order capabilities of most functional languages. It's also inconsistent, easy to write slow code in, makes it easy to introduce massive vulnerabilities, and ugly.
It's 2009. Nobody should be using PHP any more.
If you have difficulty naming a variable, it could be because you don't have a good grasp of either the problem or your solution, or concepts are conflated. It could be because you don't yet have a vocabulary that provides the terms you need -- imagine if you didn't have the words "result" or "set", but were trying to name a variable to hold the output of a query. It could be that your functions don't do just one thing.
It could even be because your language isn't expressive enough.
I can generally tell when I'm doing things 'right' because decomposing the problem into functions, naming them, and composing them into a solution is easy: it feels like I'm cutting with the grain, not against it.
In this way, coding is like writing a speech or a poem. Deliberating on precisely the right words to use is a key part of the process, and the better your grip on the domain and your arguments, the easier it is to find the words.
Ruby is hardly difficult.
(For the sake of anecdotes: I find Python to be stultifyingly simplistic, with a number of negative features, and generally poor libraries. I find Ruby to be the wrong balance between dynamism and performance. I find both of them to lack syntactic abstraction.)
Granted, that's not true of S3, SQS, or SDB... but seriously, how hard is it to program against an abstraction layer? Easy enough to rewrite your own "store_photo" function to use a replacement for S3.
It's cheaper than buying machines (by a huge amount!), cheaper than keeping them running, and I can make changes on the fly that would otherwise take a week to grind through netops.
If load spikes (as it did recently for one of our customers), the conventional answer is "we can't buy 20 more servers in 2 days"! My response was "why not use EC2?"
For a new project, rather than submitting a PO for $20k+ in hardware, I can say "it'll cost $140 for the first month". Much easier to approve -- I can put that through on expenses!
Finally, if you consider that most large companies outsource datacenter management, whether truly outsourced to a services company, or "internally outsourced" to another division, using a cloud system that at least acknowledges your right to remotely administer your own service is a step forward, not a step back.
Interaction: calling back to the singer, requesting a song. Fidelity: being right there. Shared experience: being right there with a whole bunch of other excited people.
I've had tremendously emotional experiences listening to recorded music, but none so potent as hearing the same song live.
You might extend this to teaching: a recording of even the greatest lecturer can't answer your question.
Further to the discussion, though: mass production increased the base quality of tools like axes and knives, and improved efficiency. However, if you want something bespoke, mass production doesn't care. I like my semi- and full-custom knives: they were made for me, according to my specifications. Modern tooling can bridge the gap, too, yielding full-custom items of the same quality as mass-produced items.
I was raised in the UK, and used celsius. Now I live in the US and have learned to use Fahrenheit.
On a related note, I was very annoyed that Yahoo Weather will allow you to either choose centigrade and kilometers per hour, or Fahrenheit and MPH, but not to mix and match. Insane.
It's a blind pig with fifteen legs, trying to put on its own lipstick while riding a unicycle.
What you're saying is that you want your programs to blow up when a function returns a known error (such as "disk full").
One of the points of the article is that C makes you think about all the possible, well-documented, errors that each function can encounter. You know when you write C precisely what can go wrong at each stage, and decide the right way to handle it.
Seeing a dialog box pop up with some exception backtrace is one of the things that annoys me about 'modern' Java-esque languages: they seem to encourage developers to default to ignoring most exceptions.
Computer Science != Software Engineering.
I would follow up by saying that, no matter how wonderful Road to Reality is, it's also not about CS, and GEB only overlaps the field.
An incorrectly titled post, perhaps?
Your comment is a little like saying "man, a visual text editor sure beats using ex on a teletype!" in the middle of a vi/emacs war.
Everyone has outages: it's what you learn from them that counts.
On the other hand, if you're just being patriotic, go right ahead.
The UX folks do, but that doesn't mean they get their way.