Friday, October 5, 2007

I guess this comes next: Aris eliminates a team of 118 million euros budget!!


Pictures soon, this qualification has been unbelievable!

Tuesday, May 1, 2007

Tuesday, April 24, 2007

Monday, April 23, 2007

An interesting point of view: Hackers and Painters by Paul Graham

Hackers and Painters by Paul Graham

May 2003

(This essay is derived from a guest lecture at Harvard, which incorporated an earlier talk at Northeastern.)

When I finished grad school in computer science I went to art school to study painting. A lot of people seemed surprised that someone interested in computers would also be interested in painting. They seemed to think that hacking and painting were very different kinds of work-- that hacking was cold, precise, and methodical, and that painting was the frenzied expression of some primal urge.

Both of these images are wrong. Hacking and painting have a lot in common. In fact, of all the different types of people I've known, hackers and painters are among the most alike.

What hackers and painters have in common is that they're both makers. Along with composers, architects, and writers, what hackers and painters are trying to do is make good things. They're not doing research per se, though if in the course of trying to make good things they discover some new technique, so much the better.



I've never liked the term "computer science." The main reason I don't like it is that there's no such thing. Computer science is a grab bag of tenuously related areas thrown together by an accident of history, like Yugoslavia. At one end you have people who are really mathematicians, but call what they're doing computer science so they can get DARPA grants. In the middle you have people working on something like the natural history of computers-- studying the behavior of algorithms for routing data through networks, for example. And then at the other extreme you have the hackers, who are trying to write interesting software, and for whom computers are just a medium of expression, as concrete is for architects or paint for painters. It's as if mathematicians, physicists, and architects all had to be in the same department.

Sometimes what the hackers do is called "software engineering," but this term is just as misleading. Good software designers are no more engineers than architects are. The border between architecture and engineering is not sharply defined, but it's there. It falls between what and how: architects decide what to do, and engineers figure out how to do it.

What and how should not be kept too separate. You're asking for trouble if you try to decide what to do without understanding how to do it. But hacking can certainly be more than just deciding how to implement some spec. At its best, it's creating the spec-- though it turns out the best way to do that is to implement it.



Perhaps one day "computer science" will, like Yugoslavia, get broken up into its component parts. That might be a good thing. Especially if it meant independence for my native land, hacking.

Bundling all these different types of work together in one department may be convenient administratively, but it's confusing intellectually. That's the other reason I don't like the name "computer science." Arguably the people in the middle are doing something like an experimental science. But the people at either end, the hackers and the mathematicians, are not actually doing science.

The mathematicians don't seem bothered by this. They happily set to work proving theorems like the other mathematicians over in the math department, and probably soon stop noticing that the building they work in says ``computer science'' on the outside. But for the hackers this label is a problem. If what they're doing is called science, it makes them feel they ought to be acting scientific. So instead of doing what they really want to do, which is to design beautiful software, hackers in universities and research labs feel they ought to be writing research papers.

In the best case, the papers are just a formality. Hackers write cool software, and then write a paper about it, and the paper becomes a proxy for the achievement represented by the software. But often this mismatch causes problems. It's easy to drift away from building beautiful things toward building ugly things that make more suitable subjects for research papers.

Unfortunately, beautiful things don't always make the best subjects for papers. Number one, research must be original-- and as anyone who has written a PhD dissertation knows, the way to be sure that you're exploring virgin territory is to to stake out a piece of ground that no one wants. Number two, research must be substantial-- and awkward systems yield meatier papers, because you can write about the obstacles you have to overcome in order to get things done. Nothing yields meaty problems like starting with the wrong assumptions. Most of AI is an example of this rule; if you assume that knowledge can be represented as a list of predicate logic expressions whose arguments represent abstract concepts, you'll have a lot of papers to write about how to make this work. As Ricky Ricardo used to say, "Lucy, you got a lot of explaining to do."

The way to create something beautiful is often to make subtle tweaks to something that already exists, or to combine existing ideas in a slightly new way. This kind of work is hard to convey in a research paper.



So why do universities and research labs continue to judge hackers by publications? For the same reason that "scholastic aptitude" gets measured by simple-minded standardized tests, or the productivity of programmers gets measured in lines of code. These tests are easy to apply, and there is nothing so tempting as an easy test that kind of works.

Measuring what hackers are actually trying to do, designing beautiful software, would be much more difficult. You need a good sense of design to judge good design. And there is no correlation, except possibly a negative one, between people's ability to recognize good design and their confidence that they can.

The only external test is time. Over time, beautiful things tend to thrive, and ugly things tend to get discarded. Unfortunately, the amounts of time involved can be longer than human lifetimes. Samuel Johnson said it took a hundred years for a writer's reputation to converge. You have to wait for the writer's influential friends to die, and then for all their followers to die.

I think hackers just have to resign themselves to having a large random component in their reputations. In this they are no different from other makers. In fact, they're lucky by comparison. The influence of fashion is not nearly so great in hacking as it is in painting.



There are worse things than having people misunderstand your work. A worse danger is that you will yourself misunderstand your work. Related fields are where you go looking for ideas. If you find yourself in the computer science department, there is a natural temptation to believe, for example, that hacking is the applied version of what theoretical computer science is the theory of. All the time I was in graduate school I had an uncomfortable feeling in the back of my mind that I ought to know more theory, and that it was very remiss of me to have forgotten all that stuff within three weeks of the final exam.

Now I realize I was mistaken. Hackers need to understand the theory of computation about as much as painters need to understand paint chemistry. You need to know how to calculate time and space complexity and about Turing completeness. You might also want to remember at least the concept of a state machine, in case you have to write a parser or a regular expression library. Painters in fact have to remember a good deal more about paint chemistry than that.

I've found that the best sources of ideas are not the other fields that have the word "computer" in their names, but the other fields inhabited by makers. Painting has been a much richer source of ideas than the theory of computation.

For example, I was taught in college that one ought to figure out a program completely on paper before even going near a computer. I found that I did not program this way. I found that I liked to program sitting in front of a computer, not a piece of paper. Worse still, instead of patiently writing out a complete program and assuring myself it was correct, I tended to just spew out code that was hopelessly broken, and gradually beat it into shape. Debugging, I was taught, was a kind of final pass where you caught typos and oversights. The way I worked, it seemed like programming consisted of debugging.

For a long time I felt bad about this, just as I once felt bad that I didn't hold my pencil the way they taught me to in elementary school. If I had only looked over at the other makers, the painters or the architects, I would have realized that there was a name for what I was doing: sketching. As far as I can tell, the way they taught me to program in college was all wrong. You should figure out programs as you're writing them, just as writers and painters and architects do.

Realizing this has real implications for software design. It means that a programming language should, above all, be malleable. A programming language is for thinking of programs, not for expressing programs you've already thought of. It should be a pencil, not a pen. Static typing would be a fine idea if people actually did write programs the way they taught me to in college. But that's not how any of the hackers I know write programs. We need a language that lets us scribble and smudge and smear, not a language where you have to sit with a teacup of types balanced on your knee and make polite conversation with a strict old aunt of a compiler.



While we're on the subject of static typing, identifying with the makers will save us from another problem that afflicts the sciences: math envy. Everyone in the sciences secretly believes that mathematicians are smarter than they are. I think mathematicians also believe this. At any rate, the result is that scientists tend to make their work look as mathematical as possible. In a field like physics this probably doesn't do much harm, but the further you get from the natural sciences, the more of a problem it becomes.

A page of formulas just looks so impressive. (Tip: for extra impressiveness, use Greek variables.) And so there is a great temptation to work on problems you can treat formally, rather than problems that are, say, important.

If hackers identified with other makers, like writers and painters, they wouldn't feel tempted to do this. Writers and painters don't suffer from math envy. They feel as if they're doing something completely unrelated. So are hackers, I think.



If universities and research labs keep hackers from doing the kind of work they want to do, perhaps the place for them is in companies. Unfortunately, most companies won't let hackers do what they want either. Universities and research labs force hackers to be scientists, and companies force them to be engineers.

I only discovered this myself quite recently. When Yahoo bought Viaweb, they asked me what I wanted to do. I had never liked the business side very much, and said that I just wanted to hack. When I got to Yahoo, I found that what hacking meant to them was implementing software, not designing it. Programmers were seen as technicians who translated the visions (if that is the word) of product managers into code.

This seems to be the default plan in big companies. They do it because it decreases the standard deviation of the outcome. Only a small percentage of hackers can actually design software, and it's hard for the people running a company to pick these out. So instead of entrusting the future of the software to one brilliant hacker, most companies set things up so that it is designed by committee, and the hackers merely implement the design.

If you want to make money at some point, remember this, because this is one of the reasons startups win. Big companies want to decrease the standard deviation of design outcomes because they want to avoid disasters. But when you damp oscillations, you lose the high points as well as the low. This is not a problem for big companies, because they don't win by making great products. Big companies win by sucking less than other big companies.

So if you can figure out a way to get in a design war with a company big enough that its software is designed by product managers, they'll never be able to keep up with you. These opportunities are not easy to find, though. It's hard to engage a big company in a design war, just as it's hard to engage an opponent inside a castle in hand to hand combat. It would be pretty easy to write a better word processor than Microsoft Word, for example, but Microsoft, within the castle of their operating system monopoly, probably wouldn't even notice if you did.

The place to fight design wars is in new markets, where no one has yet managed to establish any fortifications. That's where you can win big by taking the bold approach to design, and having the same people both design and implement the product. Microsoft themselves did this at the start. So did Apple. And Hewlett-Packard. I suspect almost every successful startup has.



So one way to build great software is to start your own startup. There are two problems with this, though. One is that in a startup you have to do so much besides write software. At Viaweb I considered myself lucky if I got to hack a quarter of the time. And the things I had to do the other three quarters of the time ranged from tedious to terrifying. I have a benchmark for this, because I once had to leave a board meeting to have some cavities filled. I remember sitting back in the dentist's chair, waiting for the drill, and feeling like I was on vacation.

The other problem with startups is that there is not much overlap between the kind of software that makes money and the kind that's interesting to write. Programming languages are interesting to write, and Microsoft's first product was one, in fact, but no one will pay for programming languages now. If you want to make money, you tend to be forced to work on problems that are too nasty for anyone to solve for free.

All makers face this problem. Prices are determined by supply and demand, and there is just not as much demand for things that are fun to work on as there is for things that solve the mundane problems of individual customers. Acting in off-Broadway plays just doesn't pay as well as wearing a gorilla suit in someone's booth at a trade show. Writing novels doesn't pay as well as writing ad copy for garbage disposals. And hacking programming languages doesn't pay as well as figuring out how to connect some company's legacy database to their Web server.



I think the answer to this problem, in the case of software, is a concept known to nearly all makers: the day job. This phrase began with musicians, who perform at night. More generally, it means that you have one kind of work you do for money, and another for love.

Nearly all makers have day jobs early in their careers. Painters and writers notoriously do. If you're lucky you can get a day job that's closely related to your real work. Musicians often seem to work in record stores. A hacker working on some programming language or operating system might likewise be able to get a day job using it. [1]

When I say that the answer is for hackers to have day jobs, and work on beautiful software on the side, I'm not proposing this as a new idea. This is what open-source hacking is all about. What I'm saying is that open-source is probably the right model, because it has been independently confirmed by all the other makers.

It seems surprising to me that any employer would be reluctant to let hackers work on open-source projects. At Viaweb, we would have been reluctant to hire anyone who didn't. When we interviewed programmers, the main thing we cared about was what kind of software they wrote in their spare time. You can't do anything really well unless you love it, and if you love to hack you'll inevitably be working on projects of your own. [2]



Because hackers are makers rather than scientists, the right place to look for metaphors is not in the sciences, but among other kinds of makers. What else can painting teach us about hacking?

One thing we can learn, or at least confirm, from the example of painting is how to learn to hack. You learn to paint mostly by doing it. Ditto for hacking. Most hackers don't learn to hack by taking college courses in programming. They learn to hack by writing programs of their own at age thirteen. Even in college classes, you learn to hack mostly by hacking. [3]

Because painters leave a trail of work behind them, you can watch them learn by doing. If you look at the work of a painter in chronological order, you'll find that each painting builds on things that have been learned in previous ones. When there's something in a painting that works very well, you can usually find version 1 of it in a smaller form in some earlier painting.

I think most makers work this way. Writers and architects seem to as well. Maybe it would be good for hackers to act more like painters, and regularly start over from scratch, instead of continuing to work for years on one project, and trying to incorporate all their later ideas as revisions.

The fact that hackers learn to hack by doing it is another sign of how different hacking is from the sciences. Scientists don't learn science by doing it, but by doing labs and problem sets. Scientists start out doing work that's perfect, in the sense that they're just trying to reproduce work someone else has already done for them. Eventually, they get to the point where they can do original work. Whereas hackers, from the start, are doing original work; it's just very bad. So hackers start original, and get good, and scientists start good, and get original.



The other way makers learn is from examples. For a painter, a museum is a reference library of techniques. For hundreds of years it has been part of the traditional education of painters to copy the works of the great masters, because copying forces you to look closely at the way a painting is made.

Writers do this too. Benjamin Franklin learned to write by summarizing the points in the essays of Addison and Steele and then trying to reproduce them. Raymond Chandler did the same thing with detective stories.

Hackers, likewise, can learn to program by looking at good programs-- not just at what they do, but the source code too. One of the less publicized benefits of the open-source movement is that it has made it easier to learn to program. When I learned to program, we had to rely mostly on examples in books. The one big chunk of code available then was Unix, but even this was not open source. Most of the people who read the source read it in illicit photocopies of John Lions' book, which though written in 1977 was not allowed to be published until 1996.



Another example we can take from painting is the way that paintings are created by gradual refinement. Paintings usually begin with a sketch. Gradually the details get filled in. But it is not merely a process of filling in. Sometimes the original plans turn out to be mistaken. Countless paintings, when you look at them in xrays, turn out to have limbs that have been moved or facial features that have been readjusted.

Here's a case where we can learn from painting. I think hacking should work this way too. It's unrealistic to expect that the specifications for a program will be perfect. You're better off if you admit this up front, and write programs in a way that allows specifications to change on the fly.

(The structure of large companies makes this hard for them to do, so here is another place where startups have an advantage.)

Everyone by now presumably knows about the danger of premature optimization. I think we should be just as worried about premature design-- deciding too early what a program should do.

The right tools can help us avoid this danger. A good programming language should, like oil paint, make it easy to change your mind. Dynamic typing is a win here because you don't have to commit to specific data representations up front. But the key to flexibility, I think, is to make the language very abstract. The easiest program to change is one that's very short.



This sounds like a paradox, but a great painting has to be better than it has to be. For example, when Leonardo painted the portrait of Ginevra de Benci in the National Gallery, he put a juniper bush behind her head. In it he carefully painted each individual leaf. Many painters might have thought, this is just something to put in the background to frame her head. No one will look that closely at it.

Not Leonardo. How hard he worked on part of a painting didn't depend at all on how closely he expected anyone to look at it. He was like Michael Jordan. Relentless.

Relentlessness wins because, in the aggregate, unseen details become visible. When people walk by the portrait of Ginevra de Benci, their attention is often immediately arrested by it, even before they look at the label and notice that it says Leonardo da Vinci. All those unseen details combine to produce something that's just stunning, like a thousand barely audible voices all singing in tune.

Great software, likewise, requires a fanatical devotion to beauty. If you look inside good software, you find that parts no one is ever supposed to see are beautiful too. I'm not claiming I write great software, but I know that when it comes to code I behave in a way that would make me eligible for prescription drugs if I approached everyday life the same way. It drives me crazy to see code that's badly indented, or that uses ugly variable names.



If a hacker were a mere implementor, turning a spec into code, then he could just work his way through it from one end to the other like someone digging a ditch. But if the hacker is a creator, we have to take inspiration into account.

In hacking, like painting, work comes in cycles. Sometimes you get excited about some new project and you want to work sixteen hours a day on it. Other times nothing seems interesting.

To do good work you have to take these cycles into account, because they're affected by how you react to them. When you're driving a car with a manual transmission on a hill, you have to back off the clutch sometimes to avoid stalling. Backing off can likewise prevent ambition from stalling. In both painting and hacking there are some tasks that are terrifyingly ambitious, and others that are comfortingly routine. It's a good idea to save some easy tasks for moments when you would otherwise stall.

In hacking, this can literally mean saving up bugs. I like debugging: it's the one time that hacking is as straightforward as people think it is. You have a totally constrained problem, and all you have to do is solve it. Your program is supposed to do x. Instead it does y. Where does it go wrong? You know you're going to win in the end. It's as relaxing as painting a wall.



The example of painting can teach us not only how to manage our own work, but how to work together. A lot of the great art of the past is the work of multiple hands, though there may only be one name on the wall next to it in the museum. Leonardo was an apprentice in the workshop of Verrocchio and painted one of the angels in his Baptism of Christ. This sort of thing was the rule, not the exception. Michelangelo was considered especially dedicated for insisting on painting all the figures on the ceiling of the Sistine Chapel himself.

As far as I know, when painters worked together on a painting, they never worked on the same parts. It was common for the master to paint the principal figures and for assistants to paint the others and the background. But you never had one guy painting over the work of another.

I think this is the right model for collaboration in software too. Don't push it too far. When a piece of code is being hacked by three or four different people, no one of whom really owns it, it will end up being like a common-room. It will tend to feel bleak and abandoned, and accumulate cruft. The right way to collaborate, I think, is to divide projects into sharply defined modules, each with a definite owner, and with interfaces between them that are as carefully designed and, if possible, as articulated as programming languages.



Like painting, most software is intended for a human audience. And so hackers, like painters, must have empathy to do really great work. You have to be able to see things from the user's point of view.

When I was a kid I was always being told to look at things from someone else's point of view. What this always meant in practice was to do what someone else wanted, instead of what I wanted. This of course gave empathy a bad name, and I made a point of not cultivating it.

Boy, was I wrong. It turns out that looking at things from other people's point of view is practically the secret of success. It doesn't necessarily mean being self-sacrificing. Far from it. Understanding how someone else sees things doesn't imply that you'll act in his interest; in some situations-- in war, for example-- you want to do exactly the opposite. [4]

Most makers make things for a human audience. And to engage an audience you have to understand what they need. Nearly all the greatest paintings are paintings of people, for example, because people are what people are interested in.

Empathy is probably the single most important difference between a good hacker and a great one. Some hackers are quite smart, but when it comes to empathy are practically solipsists. It's hard for such people to design great software [5], because they can't see things from the user's point of view.

One way to tell how good people are at empathy is to watch them explain a technical question to someone without a technical background. We probably all know people who, though otherwise smart, are just comically bad at this. If someone asks them at a dinner party what a programming language is, they'll say something like ``Oh, a high-level language is what the compiler uses as input to generate object code.'' High-level language? Compiler? Object code? Someone who doesn't know what a programming language is obviously doesn't know what these things are, either.

Part of what software has to do is explain itself. So to write good software you have to understand how little users understand. They're going to walk up to the software with no preparation, and it had better do what they guess it will, because they're not going to read the manual. The best system I've ever seen in this respect was the original Macintosh, in 1985. It did what software almost never does: it just worked. [6]

Source code, too, should explain itself. If I could get people to remember just one quote about programming, it would be the one at the beginning of Structure and Interpretation of Computer Programs.

Programs should be written for people to read, and only incidentally for machines to execute.

You need to have empathy not just for your users, but for your readers. It's in your interest, because you'll be one of them. Many a hacker has written a program only to find on returning to it six months later that he has no idea how it works. I know several people who've sworn off Perl after such experiences. [7]

Lack of empathy is associated with intelligence, to the point that there is even something of a fashion for it in some places. But I don't think there's any correlation. You can do well in math and the natural sciences without having to learn empathy, and people in these fields tend to be smart, so the two qualities have come to be associated. But there are plenty of dumb people who are bad at empathy too. Just listen to the people who call in with questions on talk shows. They ask whatever it is they're asking in such a roundabout way that the hosts often have to rephrase the question for them.



So, if hacking works like painting and writing, is it as cool? After all, you only get one life. You might as well spend it working on something great.

Unfortunately, the question is hard to answer. There is always a big time lag in prestige. It's like light from a distant star. Painting has prestige now because of great work people did five hundred years ago. At the time, no one thought these paintings were as important as we do today. It would have seemed very odd to people at the time that Federico da Montefeltro, the Duke of Urbino, would one day be known mostly as the guy with the strange nose in a painting by Piero della Francesca.

So while I admit that hacking doesn't seem as cool as painting now, we should remember that painting itself didn't seem as cool in its glory days as it does now.

What we can say with some confidence is that these are the glory days of hacking. In most fields the great work is done early on. The paintings made between 1430 and 1500 are still unsurpassed. Shakespeare appeared just as professional theater was being born, and pushed the medium so far that every playwright since has had to live in his shadow. Albrecht Durer did the same thing with engraving, and Jane Austen with the novel.

Over and over we see the same pattern. A new medium appears, and people are so excited about it that they explore most of its possibilities in the first couple generations. Hacking seems to be in this phase now.

Painting was not, in Leonardo's time, as cool as his work helped make it. How cool hacking turns out to be will depend on what we can do with this new medium.




Notes

[1] The greatest damage that photography has done to painting may be the fact that it killed the best day job. Most of the great painters in history supported themselves by painting portraits.

[2] I've been told that Microsoft discourages employees from contributing to open-source projects, even in their spare time. But so many of the best hackers work on open-source projects now that the main effect of this policy may be to ensure that they won't be able to hire any first-rate programmers.

[3] What you learn about programming in college is much like what you learn about books or clothes or dating: what bad taste you had in high school.

[4] Here's an example of applied empathy. At Viaweb, if we couldn't decide between two alternatives, we'd ask, what would our competitors hate most? At one point a competitor added a feature to their software that was basically useless, but since it was one of few they had that we didn't, they made much of it in the trade press. We could have tried to explain that the feature was useless, but we decided it would annoy our competitor more if we just implemented it ourselves, so we hacked together our own version that afternoon.

[5] Except text editors and compilers. Hackers don't need empathy to design these, because they are themselves typical users.

[6] Well, almost. They overshot the available RAM somewhat, causing much inconvenient disk swapping, but this could be fixed within a few months by buying an additional disk drive.

[7] The way to make programs easy to read is not to stuff them with comments. I would take Abelson and Sussman's quote a step further. Programming languages should be designed to express algorithms, and only incidentally to tell computers how to execute them. A good programming language ought to be better for explaining software than English. You should only need comments when there is some kind of kludge you need to warn readers about, just as on a road there are only arrows on parts with unexpectedly sharp curves.

Thanks to Trevor Blackwell, Robert Morris, Dan Giffin, and Lisa Randall for reading drafts of this, and to Henry Leitner and Larry Finkelstein for inviting me to speak.

Thursday, April 5, 2007

This is what I call reviewing!

LOL: Internet slang meaning = Laugh(ing) Out Loud

And this is exactly what you are going to do when you read the following review from "The New Yorker" columnist, Anthony Lane.

Fan or not, you will enjoy this!


Space Case “Star Wars: Episode III”

Sith. What kind of a word is that? Sith. It sounds to me like the noise that emerges when you block one nostril and blow through the other, but to George Lucas it is a name that trumpets evil. What is proved beyond question by “Star Wars: Episode III—Revenge of the Sith,” the latest—and, you will be shattered to hear, the last—installment of his sci-fi bonanza, is that Lucas, though his eye may be greedy for sensation, has an ear of purest cloth. All those who concoct imagined worlds must populate and name them, and the resonance of those names is a fairly accurate guide to the mettle of the imagination in question. Tolkien, earthed in Old English, had a head start that led him straight to the flinty perfection of Mordor and Orc. Here, by contrast, are some Lucas inventions: Palpatine. Sidious. Mace Windu. (Isn’t that something you spray on colicky babies?) Bail Organa. And Sith.

Lucas was not always a rootless soul. He made “American Graffiti,” which yielded with affection to the gravitational pull of the small town. Since then, he has swung out of orbit, into deep nonsense, and the new film is the apotheosis of that drift. One stab of humor and the whole conceit would pop, but I have a grim feeling that Lucas wishes us to honor the remorseless non-comedy of his galactic conflict, so here goes. Obi-Wan Kenobi (Ewan McGregor) and his star pupil, Anakin Skywalker (Hayden Christensen), are, with the other Jedi knights, defending the Republic against the encroachments of the Sith and their allies—millions of dumb droids, led by Count Dooku (Christopher Lee) and his henchman, General Grievous, who is best described as a slaying mantis. Meanwhile, the Chancellor of the Republic, Palpatine (Ian McDiarmid), is engaged in a sly bout of Realpolitik, suspected by nobody except Anakin, Obi-Wan, and every single person watching the movie. Anakin, too, is a divided figure, wrenched between his Jedi devotion to selfless duty and a lurking hunch that, if he bides his time and trashes his best friends, he may eventually get to wear a funky black mask and start breathing like a horse.

This film is the tale of his temptation. We already know the outcome—Anakin will indeed drop the killer-monk Jedi look and become Darth Vader, the hockey goalkeeper from hell—because it forms the substance of the original “Star Wars.” One of the things that make Episode III so dismal is the time and effort expended on Anakin’s conversion. Early in the story, he enjoys a sprightly light-sabre duel with Count Dooku, which ends with the removal of the Count’s hands. (The stumps glow, like logs on a fire; there is nothing here that reeks of human blood.) Anakin prepares to scissor off the head, while the mutilated Dooku kneels for mercy. A nice setup, with Palpatine egging our hero on from the background. The trouble is that Anakin’s choice of action now will be decisive, and the remaining two hours of the film—scene after scene in which Hayden Christensen has to glower and glare, blazing his conundrum to the skies—will add nothing to the result. “Something’s happening. I’m not the Jedi I should be,” he says. This is especially worrying for his wife, Padmé (Natalie Portman), who is great with child. Correction: with children.

What can you say about a civilization where people zip from one solar system to the next as if they were changing their socks but where a woman fails to register for an ultrasound, and thus to realize that she is carrying twins until she is about to give birth? Mind you, how Padmé got pregnant is anybody’s guess, although I’m prepared to wager that it involved Anakin nipping into a broom closet with a warm glass jar and a copy of Ewok Babes. After all, the Lucasian universe is drained of all reference to bodily functions. Nobody ingests or excretes. Language remains unblue. Smoking and cursing are out of bounds, as is drunkenness, although personally I wouldn’t go near the place without a hip flask. Did Lucas learn nothing from “Alien” and “Blade Runner”—from the suggestion that other times and places might be no less rusted and septic than ours, and that the creation of a disinfected galaxy, where even the storm troopers wear bright-white outfits, looks not so much fantastical as dated? What Lucas has devised, over six movies, is a terrible puritan dream: a morality tale in which both sides are bent on moral cleansing, and where their differences can be assuaged only by a triumphant circus of violence. Judging from the whoops and crowings that greeted the opening credits, this is the only dream we are good for. We get the films we deserve.

The general opinion of “Revenge of the Sith” seems to be that it marks a distinct improvement on the last two episodes, “The Phantom Menace” and “Attack of the Clones.” True, but only in the same way that dying from natural causes is preferable to crucifixion. So much here is guaranteed to cause either offense or pain, starting with the nineteen-twenties leather football helmet that Natalie Portman suddenly dons for no reason, and rising to the continual horror of Ewan McGregor’s accent. “Another happy landing”—or, to be precise, “anothah heppy lending”—he remarks, as Anakin parks the front half of a burning starcruiser on a convenient airstrip. The young Obi-Wan Kenobi is not, I hasten to add, the most nauseating figure onscreen; nor is R2-D2 or even C-3PO, although I still fail to understand why I should have been expected to waste twenty-five years of my life following the progress of a beeping trash can and a gay, gold-plated Jeeves.

No, the one who gets me is Yoda. May I take the opportunity to enter a brief plea in favor of his extermination? Any educated moviegoer would know what to do, having watched that helpful sequence in “Gremlins” when a small, sage-colored beastie is fed into an electric blender. A fittingly frantic end, I feel, for the faux-pensive stillness on which the Yoda legend has hung. At one point in the new film, he assumes the role of cosmic shrink—squatting opposite Anakin in a noirish room, where the light bleeds sideways through slatted blinds. Anakin keeps having problems with his dark side, in the way that you or I might suffer from tennis elbow, but Yoda, whose reptilian smugness we have been encouraged to mistake for wisdom, has the answer. “Train yourself to let go of everything you fear to lose,” he says. Hold on, Kermit, run that past me one more time. If you ever got laid (admittedly a long shot, unless we can dig you up some undiscerning alien hottie with a name like Jar Jar Gabor), and spawned a brood of Yodettes, are you saying that you’d leave them behind at the first sniff of danger? Also, while we’re here, what’s with the screwy syntax? Deepest mind in the galaxy, apparently, and you still express yourself like a day-tripper with a dog-eared phrase book. “I hope right you are.” Break me a fucking give.

The prize for the least speakable burst of dialogue has, over half a dozen helpings of “Star Wars,” grown into a fiercely contested tradition, but for once the winning entry is clear, shared between Anakin and Padmé for their exchange of endearments at home:

“You’re so beautiful.” “That’s only because I’m so in love.” “No, it’s because I’m so in love with you.”

For a moment, it looks as if they might bat this one back and forth forever, like a baseline rally on a clay court. And if you think the script is on the tacky side, get an eyeful of the décor. All of the interiors in Lucasworld are anthems to clean living, with molded furniture, the tranquillity of a morgue, and none of the clutter and quirkiness that signify the process known as existence. Illumination is provided not by daylight but by a dispiriting plastic sheen, as if Lucas were coating all private affairs—those tricky little threats to his near-fascistic rage for order—in a protective glaze. Only outside does he relax, and what he relaxes into is apocalypse. “Revenge of the Sith” is a zoo of rampant storyboards. Why show a pond when C.G.I. can deliver a lake that gleams to the far horizon? Why set a paltry house on fire when you can stage your final showdown on an entire planet that streams with ruddy, gulping lava? Whether the director is aware of John Martin, the Victorian painter who specialized in the cataclysmic, I cannot say, but he has certainly inherited that grand perversity, mobilized it in every frame of the film, and thus produced what I take to be unique: an art of flawless and irredeemable vulgarity. All movies bear a tint of it, in varying degrees, but it takes a vulgarian genius such as Lucas to create a landscape in which actions can carry vast importance but no discernible meaning, in which style is strangled at birth by design, and in which the intimate and the ironic, not the Sith, are the principal foes to be suppressed. It is a vision at once gargantuan and murderously limited, and the profits that await it are unfit for contemplation. I keep thinking of the rueful Obi-Wan Kenobi, as he surveys the holographic evidence of Anakin’s betrayal. “I can’t watch anymore,” he says. Wise words, Obi-Wan, and I shall carry them in my heart.

Indie Rock jems recently discovered!

1. midlake – roscoe
2. benoit pioulard – palimend
3. peter bjorn and john – young folks
4. the teenagers – homecoming
5. munk & james murphy – kick out the chairs
6. rah rah – winter sun
7. califone – pink and sour
8. andrew bird – a nervous tic motion of the head to the left
9. jose gonzales –teardrop (massive attack cover, live at bazaar curieux)
10. beirut - postcards from Italy

Movie of the week: 300 (2007)



Ancient greeks, kicking ass..

Big screen and faithful adaptation of the historically-inspired graphic novel series written and illustrated by Frank Miller. This is a retelling of the Battle of Thermopylae and the events leading up to it from the perspective of Leonidas of Sparta. 300 was particularly inspired by the 1962 film The 300 Spartans, a movie that Miller watched as a young boy.

Worth watching for being visually stunning, catching up with your history and getting an overdose of washboard abs!

Sunday, March 25, 2007

A very early zugzwang!

Zugzwang: “Compulsion to move.” A German term referring to a situation in which a player would like to do nothing (pass), since any move will damage his game.

Well, in this case, my oponent spent most of the game in this situation. Pretty much everything after move 10!

Game 13 (23-03-2007) Division 5


Wednesday, March 21, 2007

My best game! until the next one..

A game for the Club Championship, against a 120+ rated oponent.
After a normal opening (rather clumsy on the black side) an underdeveloped oponent wasted valuable tempi by manouvering his queen and tempted his luck by castling long.

I think it represents my best game so far, look out for the cool knight sacrifice (19.Nb5) that can not be refuted! I also think that the timing of the sacrifice is quite unique, less chances of being effective if played sooner or later than the given moment.


Thursday, March 1, 2007

They're back!!


Portishead delighted fans in Bristol on Sunday night by playing a surprise show and previewing material from their forthcoming album. Geoff Barrow, Adrian Uttley and Beth Gibbons were billed as 'Grumpy Man DJ's', but surprised everybody by performing live as Portishead for the first time since 2005 at the tsunami support concert alongside Massive Attack (By the way.. I was there! Not Sunday though..).

Saturday, February 24, 2007

More of my games.

Game 3 (5-12-2006) Division 6
Nice knight sacrifice, for two pawns, providing both much needed defence, and attacking prospects.




Game 1 (21/11/2006) Division 4

And the usual 1.f4 action. I'm a Bird opening addict! Moves 18-23 (23.Re5!) are a good example of creating advantage out of thin air.


Wednesday, February 21, 2007

A draw to remember!




Moro in time trouble (2 minutes on the clock) missed a chance for glory with:

38.Qd8+ Kg7 39.f6+ Kh6 40.Kh4!! Qxd4+ 41.g4 Qb4 42.Qf8! Qxf8 43.g5#

Nevermind, it's games like this that make him my favourite active player.

Movie of the week: The last kiss (2006)




Zach Braff's effort to top up Garden State is an engaging bitter sweet experience.
29 year olds in crisis, relationships realism and yet another worthwhile soundtrack.
Worth watching, even if you're not around 30!

Monday, February 19, 2007

"Just another bedroom rocker – Volume 1" by yours truely

1. bonobo – kota
2. gak sato – penetrare (beleville mix by kid loco)
3. j-walk – following the noughties
4. big bud – persian blues
5. invisible pair of hands – once upon a time
6. peace orchestra – the man (gotan project remix)
7. moped – after the pain
8. a forest mighty black – reflections of a fake night
9. dj spinna – bahia blues
10. nightmares on wax – bleu my mind
11. sneaker pimps – wasted early sunday morning
12. sumo – limpid
13. the herbalizer – theme from control centre (reprise)
14. the chess cadet all stars feat. etta james – see me smile
15. the stic – levitation dub
16. marshmellow – splendid
17. sukia – the dream machine (space echo mix)
18. layo & bushwacka – blind tiger

Friday, February 16, 2007

DJ Krush megamix tribute

Tracklisting only for now. I might post the mix soon. Sounds amazing!

1. DJ Vadim – Variations in USSR (DJ Krush remix)
2. Sugizo – Spiritual Prayer (DJ Krush remix)
3. DJ Krush feat. Abijah – What about tomorrow?
4. DJ Krush feat. Eri Ohno – Mind games
5. DJ Krush – Dig this vibe
6. DJ Krush – Edge of blue
7. Hamid Baroudi – Arabica (DJ Krush mix)
8. DJ Krush & Ronny Jordan – Season for change
9. DJ Krush feat. Deflon Sallahr of Hedrush – Ground
10. kudO – Ibuki reconstruction (DJ Krush remix)
11. DJ Krush – Big city lover
12. DJ Krush – Keeping the motion
13. DJ Krush & Toshinori Kondo – Shoh ka
14. Boom boom satellites – On the painted desert (DJ Krush remix)
15. DJ Krush feat. Ahmir ?uestlove Thompson – Endless Railway (sentiment mix)
16. DJ Krush feat. D-Madness & Masato Nakamura – But the world moves on
17. DJ Krush feat. Angelina Esparza – Alepheuo (truthspeaking)
18. DJ Krush feat. C.L Smooth – Only the strong survive (attica blues remix)
19. DJ Krush – 3rd eye
20. DJ Krush feat. Sunja Lee – Paradise bird theory
21. DJ Krush feat. Zap Mamma – Danger of love (gray sky mix)
22. DJ Krush & Toshinori Kondo – sun is shinning
23. DJ Krush feat. Deborah Anderson – Skin against skin
24. DJ Krush feat. Rino – Shin Sekai
25. DJ Krush feat. Black Thought and Malik B. of The Roots – Meiso (Silent gun mix)
26. DJ Krush feat. Mos def. – Shinjiro (Harsh mix)

Thursday, February 15, 2007

More 1. f4

Good queenside play.


And a good one..

Calculated, merciless attack!


A bad game..

Thinking only about attacking and creating complications does not pay off!


Tuesday, February 13, 2007

Power play : recent and frequent tracks on my playlist

Should I do this weekly again?
Well, we'll see..

In no particular order, here it goes:

1. 8mm - you know
2. boom boom satellites - on the painted desert (dj krush remix)
3. joel - won't take no (giorgios lights out dub)
4. lyrics born - concentration (instrumental)
5. kosheen - catch (beauty's confusion night mix)
6. sugizo - spiritual prayer (dj krush remix)
7. rodney hunter - work that body
8. tekitha - walking through the darkness
9. urchin - nile rose
10. zero one - inner space
11. mylo - sunworshipper
12. urbs - the incident
13. lemongrass - passengers
14. dutch rhythm combo - come on
15. shantel - your hands
16. millenia nova - I'm dead
17. dzihan & kamien - ay ay ay
18. sofa surfers - tsetse fly (remixed & dubbed by the hi tek steppas)
19. obO - forelash
20. dj krush feat. Ahmir Questlove Thompson - endless railway (sentiment mix)

Slight dj krush influence, but what can I say, the guy is brilliant!
And I've had some new material recently..

Movie of the week: Brick (2006)


New proposal, every week, if I can keep up with it.
Don't be surprised if I turn it into Movie of the month soon..

I'm not gonna say much about it, just watch it and see!
Best described as: "High school confidential, film noir in a teen movie package".

Thursday, January 18, 2007

Next please...




Once again, the hottest home court in Europe has made a difference.
Italian champions, Benetton Treviso bowed before those crazy fans, loosing 65-60 to Aris. The "yellows" are now one win away from the 16 best teams in Europe.
Great night from Terrel Castle, who despite recent surgery led the team with 22 points and 5 three-pointers, alongside Scales (17) and Iliadis (10).
More soon on the Emperor of greek basketball, including video footage from the Aris - Napoli (80-72) game , that I was fortunate to attend.

Monday, January 15, 2007

Wednesday, January 10, 2007

Dark matter mapped in 3D for first time

Blue Foundation



Blue Foundation is a music - artist collective with members from Denmark, Japan and England. The music reflects their metropolitian life in urban culture of today. With influences from hip hop, turntablism, trip hop, classical music, film noir and contemporary music, Blue Foundation creates a musical world that takes you back into the history of music.
They are mostly known for their 2004 release Sweep of Days. Their track "Sweep" featured on the Miami Vice OST.

Tracklisting (Sweep of Days):
1 History
2 As I Moved On Guitar - Hans Landgreen
3 End of the Day (Silence)
4 Ricochet
5 02.17 AM
6 Embers
7 Bonfires
8 The Yellow Man
9 Shine
10 Save This Town
11 Sweep
12 My Day

Their selftitled release from 2001 is equally enjoyable.

Tracklisting (Blue Foundation):
1 Wiseguy (5:06)
2 Grand (5:03)
3 Witch Of Trouble (3:39)
4 Crushed (3:07)Scratches - Kruzh'em
5 Jabber (4:18)
6 Hollywood (3:58)
7 Burgeon (1:50)
8 Black S (4:54)
9 Mazda (0:58)
10 Hide (4:07)
11 Cutting Me Up (3:58) Vocals - MC 'Iruk , MC Reef K.
12 J. Hurt (4:17)
13 Evo (4:17)

Now I just need to get my hands on this year's release!

Sunday, January 7, 2007

Happy New Year!



1st sunset of 2007 in Thessaloniki. What can I say? I love this city.