New post: Ask A Silly Question..

“@_meglet: @jasonmcdermott are you ever going back to Aus???” never! Well, not until December...

RT @tjn: Love this little ditty by @jasonmcdermott, "Make spectacular mistakes." http://t.co/XV4QXsxA

http://t.co/XME8vEPM Screaming Rapture in the SMH, check out the video of the artwork in action!

Last year my son Liam was one of the team that created Social Fireflies for the Vivid festival. This year they’re producing Screaming Rapture. The social fireflies moved in response to light, from outside or from each other. The louvres of the rapture respond to sound. You make a noise. They flash. I don’t know about the title, but it’s looking cool.

New post: Fulfillment Calculus

New post: Spoiler Alert

New post: Araabmuzik

In case you're curious, this is where I've been for the last 8 weeks... http://t.co/yLc1pst9 bring on the next 6 months! #bigtrip

New post: Key To The Mind

New post: Agua Azul

Screaming Rapture interview today, soon to be featured on http://t.co/vUFWP27O more to come! #screamingrapture @frankmaguire

Pour le festival Vivid 2011, qui aura lieu en Nouvelle-Galles du Sud (Australie). Les artistes Jason McDermott, Lian Ryan et Franck Maguire ont été mis à contribution afin de réaliser et d’installer une innovante œuvre d’art lumineuse.

Installée dans Circular Quay, un quartier de Sydney, Social Firefly (Luciole en français) sont des éclairages intelligents qui s’influence mutuellement. Les « fireflies » sont programmées pour répondre à la lumière de leurs voisins.

Social Firefly devient une démonstration de ce que pourrait être le design d’interaction, quelque chose de dynamique, de beau, d’enjoué et à la fois nous renseigne sur nos relations avec les autres créatures.

New post: Tyrion Hitting Joffrey For 10 Minutes

back on the tweets... oh no!

RT @frankmaguire: Screaming Rapture is alive, with only 17 days til launch! http://t.co/TTCo3inA

New post: Big Trip

TUXTLA

Galerias Boulevard
Boulevard Belisario Dominguez No. 1861 Loc. D6 y D7
Col. Bugambilias
Tuxtla Gutierrez
C.P. 29056
Tel: (961) 6157401 y (961) 6155163

Mimo 710S “Mobile Slider” Model
Same slick design features as our popular 720S model but without touchscreen capability, a great entry-level display-only model.  The Mimo 710S is a sleek, foldable and highly portable unit, with a tiny footprint when folded (weighs less than a pound!). The integrated stand protects the screen from scratches when closed; when opened, the screen can display in either landscape or portrait orientations.

fullscreen Aperture looks amazing on an ipad...

New post: Checking In, Daring Fireball Edition

New post: Make spectacular mistakes

@AleSol_MK vaya! regresamos a Australia en diciembre :)

Pseudo rainy-sunny day in Tulum, very confusing. To beach or to breach?

@adamjohnrussell depends on the complexity of site and design, in my opinion SKP isn't up to task. Hope it goes well, mate!

@AleSol_MK are you going to be in Chile later this year? I'm tempted but very time poor :)

@AleSol_MK rocking through Guatemala is very similar to rocketing down parramatta rd in sydney, can't yet tell if it's a good thing or bad!

New post: Caye Caulker

But then, AHA! I googled one of your forum archives, and down at the bottom a suggestion was made which didn't seem to work one of the readers - perhaps because of some Mac problem, but it worked WONDERFULLY and INSTANTLY for me, and should work for anyone with a windows machine.

Here's part of the post:
You can use Adobe Acrobat (not the Reader):

1. Choose Adobe PDF printer
2. Set Page Scaling to "Tile Large Pages", set Tile Scale to 100% and overlap to 0
3. Print the document with Adobe PDF printer as a new .pdf file

When I did this with an old book (with hand notations), it ended up with each of the facing pages on a separate page with a lot of white space around it, easily cropped with alternate page cropping.

After alternate page cropping, I used the OCR recognition, which straightened up each of the pages almost perfectly for the best OCR possible.

I had to clean up a few badly skewed pages - and one that had a fold-out chart, but that only took a few minutes, as opposed to the terribly tedious drag and drop from two files method.

Result: Nice, clean, straight, OCRed text which could be used for reading on any PDF reading device.

(In addition, I found that good new copiers have a SCANNER feature which will scan in books and magazines almost instantly as well, instead of the tedious 1-minute-per-page thing which can take hours to do.)

I hope this helps some folks, as it as been a wonderful fi

New post: Hating on the iTunes

New post: Sunburnt And Loving It

New post: Learning another tongue

Hey @julienbayle, don't mean to pester you, how did you solve the libofxiPhone_iphoneos_Release.a link error, from http://t.co/zGRJxCBb ?

New post: jasonmcdermott: Annandale galleries + wine in hand, from my…

New post: Semuc Champey

New post: Caine’s Arcade

New post: iTunes or bust

New post: Not evacuating, yet

One reason programmers dislike meetings so much is that they're on a different type of schedule from other people. Meetings cost them more.

There are two types of schedule, which I'll call the manager's schedule and the maker's schedule. The manager's schedule is for bosses. It's embodied in the traditional appointment book, with each day cut into one hour intervals. You can block off several hours for a single task if you need to, but by default you change what you're doing every hour.

When you use time that way, it's merely a practical problem to meet with someone. Find an open slot in your schedule, book them, and you're done.

Most powerful people are on the manager's schedule. It's the schedule of command. But there's another way of using time that's common among people who make things, like programmers and writers. They generally prefer to use time in units of half a day at least. You can't write or program well in units of an hour. That's barely enough time to get started.

When you're operating on the maker's schedule, meetings are a disaster. A single meeting can blow a whole afternoon, by breaking it into two pieces each too small to do anything hard in. Plus you have to remember to go to the meeting. That's no problem for someone on the manager's schedule. There's always something coming on the next hour; the only question is what. But when someone on the maker's schedule has a meeting, they have to think about it.

Last week we talked about the importance of having predictable ‘office hours.’ They’re important for your productivity and for your sanity. But they’re only important for your productivity if you actually do important work during the hours you set.
So, today, I’d like to offer one, simple tip for how to make sure the time you intentionally set aside for work actually works:
Set three goals.
When you wake up in the morning, or when you finish at the office the day before, set three goals for the next day. No more, no less.

U.K. Government Digital Service Design Principles http://t.co/zLc0c5Ch @feltysurface via @khoi

New post: Hard pressed to find an alternative

WordPress’ biggest challenge over the next two years, and where we’re focusing core development, will be around evolving our dashboard to be faster and more accessible, especially on touch devices. Many of our founding assumptions about how, where, and why people publish are shifting, but the flexibility of WordPress as a platform and the tens of thousands of plugins and themes available are hard to match. We might not always be the platform people start with, but we want to be what the best graduate to.

New post: Updating…………

New post: Wrapping up on Instagram

Background

C++ is the main development language used by many of Google's open-source projects. As every C++ programmer knows, the language has many powerful features, but this power brings with it complexity, which in turn can make code more bug-prone and harder to read and maintain.

The goal of this guide is to manage this complexity by describing in detail the dos and don'ts of writing C++ code. These rules exist to keep the code base manageable while still allowing coders to use C++ language features productively.

Style, also known as readability, is what we call the conventions that govern our C++ code. The term Style is a bit of a misnomer, since these conventions cover far more than just source file formatting.

One way in which we keep the code base manageable is by enforcing consistency. It is very important that any programmer be able to look at another's code and quickly understand it. Maintaining a uniform style and following conventions means that we can more easily use "pattern-matching" to infer what various symbols are and what invariants are true about them. Creating common, required idioms and patterns makes code much easier to understand. In some cases there might be good arguments for changing certain style rules, but we nonetheless keep things as they are in order to preserve consistency.

Another issue this guide addresses is that of C++ feature bloat. C++ is a huge language with many advanced features. In some cases we constrain, or even ban, use of certain features. We do this to keep code simple and to avoid the various common errors and problems that these features can cause. This guide lists these features and explains why their use is restricted.

Open-source projects developed by Google conform to the requirements in this guide.

Note that this guide is not a C++ tutorial: we assume that the reader is familiar with the language.

First time on the tweets since march. True story! Guatemala is keeping me busy..