The Generosity Of Criticism

My point is that we expect judgment from each other but when it comes to critique, we take offence.

And this just seems insane as what is more generous than critique? It demands time and energy, a lending of oneself to the performance of another. Judgment leans back in its chair and, exerting the bare minimum of energy, points a thumb up or down. But critique leans forward in its chair, poised and attentive, heeding and contemplating, digesting and imagining.

via The Generosity Of Criticism « Thought Catalog.

Critique is good., judgement is bad.

If you like something, say so — but explain why, otherwise you might as well say it’s crap for the same net effect.

Mass Effect, Tolkien, and Your Bullshit Artistic Process – doyce testerman

Let’s pretend for a moment that The Lord of the Rings was released not as a series of books, but a series of games. More importantly, the company behind the series decided to do something really hard but rewarding with the game — they were going to let you make decisions during play that substantively altered the elements of the story. That means that some of people playing through this Lord of the Rings story would end up with a personal game experience that was pretty much exactly like the one you and I all remember from reading the books, but that story is just sort of the default. Whole forums were filled up by fans of the series comparing notes on their versions of the game, with guides on how to get into a romantic relationship with Arwen (the obvious one), Eowyn (more difficult, as you have to go without any kind of romance option through the whole first game, but considered by many to be far more rewarding), or even Legolas (finally released as DLC for the third game).

via Mass Effect, Tolkien, and Your Bullshit Artistic Process – doyce testerman.

If you have no idea why people are upset about the ending of Mass Effect, but have watched and understand the Lord of the Rings, then you should read this.

Actually, you should read this anyway, because it’s one of the best pieces of writing I’ve read in a while (not to mention the best Mass Effect 3 ending-explanation-kerfuffle to date).

You’re crap and paid too much for the little work you actually do

Note that the title is “get more money”, not “earn more”. I can’t make you better at your job, my aim is to get you better rewarded for it. You are worth what you can get, not a penny more or less. In negotiations it is useful to use the word “fair” so that the other side doesn’t feel too blackmailed, but never kid yourself that it means anything.

One serious programmer explained to me that “if the system goes down for 30 minutes, you’re incompetent. Bring it back after five hours and you’re a hero”. They key here is that you’re making a difference when it hits the fan, that’s not someone they want to lose.

How do people know if what you’ve achieved is great? Even if you work for Capita, you occasionally actually finish something useful so you must let people know. The logic is simple: if you invite a bunch of people for a quick beer to celebrate the completion of the data ingest module, then it must be good. The fact that it’s a VBA macro to import CSV files into Excel is not the issue, the message is that it’s working great. Each victory over the formless hell of Oracle is worthy of you picking up a box of chocolates from the supermarket and sharing them with people passing your desk. The £10 cost pays back very well as you build up an aura as “someone who gets things done”.

via You’re crap and paid too much for the little work you actually do • The Register.

I… I have no words. Where to start?

I’m not entirely sure if this article is just taking the piss or offering serious advice to programmers and other IT staff. The advice all seems sound in theory, and following it should make you “get more money” for the work you do, but, I mean, following it as if you life depended on it (i.e. all the time, all day, every day) would just make you somewhat of a jerk.

The Star Wars Saga: Introducing Machete Order

Introducing: Machete Order

Now I’d like to modify this into what I’ve named Machete Order on the off chance that this catches on because I’m a vain asshole.

Next time you want to in­tro­duce someone to Star Wars for the first time, watch the films with them in this order: IV, V, II, III, VI

Notice some­thing? Yeah, Episode I is gone.

via Absolutely No Machete Juggling » The Star Wars Saga: Introducing Machete Order.

Fantastic post on why you should be watching the Star Wars saga in a different order that what you’re probably traditionally used to. Long, but very well worth the read.

It’s a brick!

Tesla Motors’ lineup of all-electric vehicles — its existing Roadster, almost certainly its impending Model S, and possibly its future Model X — apparently suffer from a severe limitation that can largely destroy the value of the vehicle. If the battery is ever totally discharged, the owner is left with what Tesla describes as a “brick”: a completely immobile vehicle that cannot be started or even pushed down the street. The only known remedy is for the owner to pay Tesla approximately $40,000 to replace the entire battery. Unlike practically every other modern car problem, neither Tesla’s warranty nor typical car insurance policies provide any protection from this major financial loss.

What’s kinda funny is that you can brick your electric car by letting the battery go completely flat.

I mean, have you heard of anything more hilarious?