From a New York Times article, we learn how Apple was able to build its devices:

Apple executives say that going overseas, at this point, is their only option. One former executive described how the company relied upon a Chinese factory to revamp iPhone manufacturing just weeks before the device was due on shelves. Apple had redesigned the iPhone’s screen at the last minute, forcing an assembly line overhaul. New screens began arriving at the plant near midnight.
A foreman immediately roused 8,000 workers inside the company’s dormitories, according to the executive. Each employee was given a biscuit and a cup of tea, guided to a workstation and within half an hour started a 12-hour shift fitting glass screens into beveled frames. Within 96 hours, the plant was producing over 10,000 iPhones a day.

In a related news, the President of United States want to get manufacturing jobs back in the USA:

No, we will not go back to an economy weakened by outsourcing, bad debt, and phony financial profits. Tonight, I want to speak about how we move forward, and lay out a blueprint for an economy that’s built to last -– an economy built on American manufacturing, American energy, skills for American workers, and a renewal of American values.

Apple is far from being the only one to profit from outsourcing its production but with its stunning profits, it is emblematic of the failure of capitalism to balance profit with humanity bien-être.

Apple success is well deserved, they have an outstanding line of products and I own many of them. I bought an iPhone 4S during this quarter and it is the best phone (and pocket camera) I ever had. However, I can not accept that someone is woken up in the middle of a night, given a biscuit and a cup of tea and has to work 12-hour to build a device I use sitting in my couch.

We would live in a better world if the companies profits (from Apple and all the others) could be used to create new jobs or at least provide decent working conditions when they outsource their production.

• The Pummeling Pages
• Pub Rules
• Readable Future

In other words, content! content! content! (as in quality, not quantity).

It’s a sad state for Web publishing when I need to use a mix of Instapaper, Readability, Safari Reader to have a sane reading experience without advertisement overload (and unfortunately, I know what an interstitial is…).

⚑

Jeff Lindsay requested to pull one of his branch of stomp-websocket where he converted all the code to CoffeeScript, added unit tests with a mock implementation of a WebSocket server. This work is a preliminary for more features (including a much-needed support for STOMP 1.1).

When he offered to pull its branch, he wonders if the move to CoffeeScript was controversial and if I would accept it.

stomp-websocket is meant to run inside Web browsers and leverage the Web Sockets API. When I wrote it, JavaScript was a no-brainer.

However I have started to question this choice recently.

I have a pet project where I use node.js and I am making countless JavaScript code mistakes (I was bitten by this one last week, thankfully I have not released my project yet).

As much as I like JavaScript and its related HTML5 APIs, I must admint I am not a good JavaScript programmer and I want a language that helps me instead of trapping me. I started to read about CoffeeScript as a replacement of JavaScript. I find the language more pleasing to read even though some syntax conventions makes it more cryptic than concise.

I am quite pleased with the new code of stomp-websocket in stomp.coffee. It reads much better than the original stomp.js, there are no longer noisy this, that or vars (when they are not missing by errors!).

However, the JavaScript code compiled by CoffeeScript does not look good. I suppose I must stop to look at the compiled JavaScript and instead consider it as the assembly language of the Web.

In any case, the transition should be transparent for developers using stomp.js: the new generated stomp.js offers the same API than the previous one.

If that is not the case, please report any regression or bug on GitHub issue tracker.

As usual, do not hesitate to contribute:

git clone git://github.com/jmesnil/stomp-websocket.git

As Jeff Lindsay can attest, I welcome good contributions :)

Uncle Bob:

Rich [Hickey] makes the point that sprinters run fast, but not long. Then he says that Agile “solved” this problem by just firing the starting gun over and over again in quick succession. He grins, and the audience laughs. Then he goes on to say that continuous sprinting does not necessarily makes systems simple, and simplicity is the real key to speed.

That is exactly the issue I have with Scrum and other so-called “agile” methods. It sacrifices long-term design and overall quality for fast short-term hacks. Sometimes there are no shortcuts for long hard work to end up with something simple.

Simple and easy are not interchangeable concepts…

As a bonus fo French readers, a post with a different perspective on the different meanings of simplicity by a colleague, Johan Martinsonn: Pas si simple de faire simple.

The concept of an address book or contacts feels so lame and dated, it’s like ‘an address book is this little thing with this faux leather cover!
— Matias Duarte

Touché! The Address Book app is a sore point in the iOS (and Mac OS X) experience.

It is a chore to use this application to update contacts information and the “real life” user interface makes it even more frustrating.

⚑

It’s too bad that James Duncan Davidson announced they shut down the Daily Shoot when I finally have a good camera in my pocket all the time everyday.

⚑

Steve Jobs:

Your time is limited, so don’t waste it living someone else’s life. Don’t be trapped by dogma — which is living with the results of other people’s thinking. Don’t let the noise of others’ opinions drown out your own inner voice. And most important, have the courage to follow your heart and intuition. They somehow already know what you truly want to become. Everything else is secondary.

For all the products and ideas that Steve Jobs delivered during his life, nothing from him has inspired me more than when he talked about life, love and death and what we can do from our life in his Stanford commencement speech:

All my thoughts go to his family, friends and coworkers at Pixar & Apple.

• James wrote about its reluctance to use creative commons licenses for his professional photographs
• Tim then explained how one of his photographs that he uploaded on Wikipedia (in a compressed size) under Creative Commons licenses was chosen to be a book cover and that he got paid for the full size version
• James then replied with additional food for thought

At the moment, I upload my photos on Flickr under an “Attribution, Share Alike” Creative Commons license. I do not take photos professionally but if people would be interested to use them in commercial products, I would like to get paid for their use.

Tim’s proposal to use different licenses depding on the resolution is a good idea:

• use a creative commons licenses for low-to-moderate resolution and make them available liberally (on Wikipedia, Flickr, etc.)
• keep a more restrictive licenses on the full resolution

As a web developer, learning the internals of browser operations helps you make better decisions and know the justifications behind development best practices. While this is a rather lengthy document, we recommend you spend some time digging in; we guarantee you’ll be glad you did.

All you have ever wanted to know about the internals of Web browsers and more…

I link to the document on HTML5 rocks which is nicely presented but the original is available on Tali Garsiel web site.

(via FunctionSource)

⚑