I backed Andrew‘s book on Kickstarter – looking forward to reading it.

This looks more complicated than the merge workflow. It is. It is not hard. It is valuable.

We have our pull command set up to pull --rebase, this is a great overview of why you (almost) always want to rebase. (thanks Sandy)

This post is part of the thread: Version Control – an ongoing story on this site. View the thread timeline for more context on this post.

The next morning the strangest thing happened. I was standing on the station platform in Milsons Point waiting for the train, reading a (Kindle) book on my iPad, and for the first time ever I could see the pixels. I mean I obviously had seen them before, but now I was noticing them every time I looked at the screen. My eyes were tripping over the slightly blurry sub-pixel text rendering when they should have been flowing easily from word to word.

Same thing happened to me. I wasn’t unhappy with the iPad 2 screen, but now it looks terrible.

After basically giving them up a few years back, I can’t drink a whole soda anymore either.

The main reason I’m not interested in LTE (yet): mobile data packages are so limiting you can’t do anything interesting with the additional speed.

I think everyone I respect already reads everything published on Rands in Repose by now, but just in case any of you have been living under a rock…

Tucking this away for the next time I hear someone say “MySQL doesn’t scale” (not that NoSQL solutions aren’t also good tools).

Some great tips, as usual, from Steve. I’d also point out that you need a strategy for how to you plan to update the resources you are telling browsers to cache. I typically favor the “update a query string var” approach.

Definitely agree with this approach; it’s pretty much how we designed FavePersonal. (thanks Rona)

This post is part of the thread: FavePersonal – an ongoing story on this site. View the thread timeline for more context on this post.