I'm in the process of moving a CakePHP 1.3 app into the 2.1 world.

One thing that changed that I could not find documented anywhere is that the new migration plugin doesn't use the map.php file anymore but relies on a naming convention.

VersionNumber-name.php

Where VersionNumber is the version number of the migration. For example on my app:

001_initial.php
002_chapter_word_count.php
003_story_disclaimer_field.php
004_follows.php
005_reviews.php
006_chapter_review_count.php

You can pad with as many zeros as you feel you'll need. Are 999 migrations not enough? Also each class name needs to be changed to the camelized version of the file name without the version number, so 001_initial.php should start like this:

<?php
    class Initial extends CakeMigration {

And that way CakeDC's migration plugin will detect the migrations again.

PhantomJS is a headless WebKit with JavaScript API. It has fast and native support for various web standards: DOM handling, CSS selector, JSON, Canvas, SVG.

PhantomJS is an optimal solution for fast headless testing, site scraping, pages capture, network monitoring and many other use cases.

Very useful.

This American Life is a great podcast, the stories they air are greatly produced and they go to great lengths to research them.

The episode "Mr. Daisey and the Apple Factory", aired on January, started a big backlash against Apple's manufacturing operations and the fact they turn a blind eye to the terrible conditions the manufacturing workers are subjected to.

Today they are retracting that story.

[a Marketplace] China correspondent for the public radio show Marketplace tracked down the interpreter that Daisey hired when he visited Shenzhen China. The interpreter disputed much of what Daisey has been saying on stage and on our show. On this week's episode of This American Life, we will devote the entire hour to detailing the errors in "Mr. Daisey Goes to the Apple Factory."

The backlash this story generated did change the attitude of Apple, now they have become members of the Fair Labor Association and have become even more vocal about their standards of social responsibility across our worldwide supply chain.

Mike Daisey was wrong of abusing the loudspeaker that This American Life is, but I think he doesn't really regret it, from his blog:

What I do is not journalism. The tools of the theater are not the same as the tools of journalism. For this reason, I regret that I allowed THIS AMERICAN LIFE to air an excerpt from my monologue. THIS AMERICAN LIFE is essentially a journalistic ­- not a theatrical ­- enterprise, and as such it operates under a different set of rules and expectations. But this is my only regret. I am proud that my work seems to have sparked a growing storm of attention and concern over the often appalling conditions under which many of the high-tech products we love so much are assembled in China.

It's going to be interesting to listen to next week's TAL and find out what "creative licenses" Daisey took and what is the truth.

I agree with Daisey's take that his stunt shaked the status quo. That is good. Lying to TAL and Ira Glass. Not cool.

How did I work without this?

Via: Veerle

I'm learning Backbone.js and this article has helped me to get a first grasp on how to manage the separation of Views and model and how to wire them up to update each other as necessary: changes in the view will update the model which triggers the validation of the fields which in turns has to update the view.

It's very refreshing to finally have MVC on the client side, no more crazy jQuery wires all over.

I finished reading the Hunger Games in 4 days. That's how good it is.

I wrote a review on my wife's site, check it out. And of course, spoiler alert.

I've said it before, people need to stop working on updating their résumé and start working on publicly visible side-projects.

Now, this article shows a new trend where employers are not looking at résumés but want to know you better by your online interactions.

Companies are increasingly relying on social networks such as LinkedIn, video profiles and online quizzes to gauge candidates' suitability for a job. While most still request a résumé as part of the application package, some are bypassing the staid requirement altogether.

Marco proposes:

it would be more productive to significantly reduce or eliminate our support of the MPAA member companies starting today

Here's the list of studios you have to stop buying from:

it’s easy to see who the MPAA represents: Disney, Sony Pictures, Paramount, 20th Century Fox, Universal, and Warner Brothers. (Essentially, all of the major movie studios.)

Basically you have to stop watching things like (a quick selection from IMDb):

• The Simpson's
• Bones
• Lilo & Stitch
• Star Wars
• TRON
• A Clockwork Orange

This is depressing. Even Amélie was touched by 20th Century Fox for distribution purposes.

I agree with him, but it's near impossible to stop supporting "Essentially, all of the major movie studios".

This article complements the two comments I made on my previous post.

I said:

With Megaupload closed, should you backup your online backups?

Answer:

In short, if you stored important files on Megaupload, I really hope you had an up-to-date backup on your computer.

And then I said:

Also: will this takedown have an effect on the users? Are we gonna see the RIAA or MPAA sifting through the logs and suing en masse?

This what the article hast to offer:

It’s almost guaranteed that Megaupload stored the IP address of file uploaders, and the Feds could pursue individual copyright infringement cases at a later date.

Choose your acronym: RIAA, MPAA, FBI.

However, do the feds realize that hundreds of thousands, perhaps millions of people used the site to share research data, work documents, personal video collections and much more?

With Megaupload closed, should you backup your online backups?

Also: will this takedown have an effect on the users? Are we gonna see the RIAA or MPAA sifting through the logs and suing en masse?

Ash Furrow lists a great list of resources for learning iOS development.

He mentions that books didn't work for him although didn't list the books he tried.

To get started, some people buy a book or find some good online tutorials. I tried both approaches, and the online tutorials were definitely better.

I'm going through Nerd Ranch's "iOS Programming: The Big Nerd Ranch Guide" recommended to me by Marco Arment and it has been very good because it makes you do the example apps.

Emails are not safe:

• They are sent via the network in plain text so any attacker snooping the net could grab it.
• They are stored in plain text, if somebody gains access to my computer they could be read, same if someone breaks into my email account.

Double whammy if you send the login on the same email.

The linked pdf has a lot more information and solutions, if you're implementing password recovery in your site read it.

An interesting interview that really resonates with me and my current situation. Specially I liked Ben's replies on how to overcome procrastination and self-depreciation of your abilities.

I realized most great designers are actually busy finding clients, speaking at events, and doing the “office work” of running a small business, and raising families – they are just as strapped for time as I am, if not more so.

One of the biggest problems he experienced:

I’ve always struggled with a sense of urgency…

But you still got stuff done. So, explain your motivation process. Parkinson’s Law says work expands to fill the time available to complete it. So when I set long deadlines to avoid missing them, I also give myself a lot of time to procrastinate and have no urgency. It goes back to mini deadlines.

Read the whole interview, it's worth your time.

That article on how to selectively commit specific changes on a file I posted, not necessary anymore. Very cool.

Another interesting update:

The entire changes view has been redesigned. It's now easier to review your changes and roughly 5 gazillion times faster.

I was having this problem a couple of minutes ago. A couple of interesting comments already there:

your push works, you just get a confusing error about the other branches that git tries to auto-push.

So basically, the push on you branch does work. I checked on github immediatly and it didn't show, but it could have been just a matter on timing.

And this comment:

For whatever reason, by default git push pushes to all branches on the remote. To set this to the default that you’re expecting (and that really seems the only sane and reasonable default to me, but I digress), you can use git config remote.origin.push HEAD. But meanwhile, since you may wind up using git from other machines and forget that the default behavior is broken, you should probably always just specify the remote and branch explicitly.

So, using your example here, you would use:

git push origin fetch-flow

The problem with this is that if you mistype your branch, you could wind up creating a new branch on the remote with the typo, e.g. something like fletch-flow. So that brings us to what is likely the best git push habit to get into:

git push origin HEAD

This will push only the current branch to a branch of the same name on the remote.