The little I do know is that film companies once used different production methods and materials to make and process film. And because of that, the color we see in photos taken with different analog films look very distinct from one other.
La solution à tous les problèmes, réels et inventés, de l’iPad ? Des fenêtres, bien sûr ! D’accord, d’accord, j’exagère un peu. Mais de fait : certains n’arrivent pas à imaginer que le futur de l’iPad ne passe par un rapprochement fonctionnel avec le Mac.
Writing release notes is a contentious issue. There are some companies who simply don’t bother (often with good reason) and some companies who put their heart and soul into creating something truly engaging.
I gave a talk to my team at ARM today on Working Effectively with Legacy Code by Michael Feathers. Here are some notes I made in preparation, which are somewhat related to the talk I gave. This may be the most important book a software developer can read.
When writing code, the biggest enemy is complexity. Maintaining levels of abstraction and allowing the developers who work in our codebases to fluidly move up and down through those concepts is crucial to large software projects.
Here's the thing: sharing code is dangerous. Do it sparingly. Let's see some pictures. Purple Service here has some classes or functions that it finds useful, and the team thinks these would be useful elsewhere. Purple team breaks this code out into a library, the peachy circle.
I love the idea of the iMessage App Store. I love Apple’s focus on privacy. I love building on top of an app I use all day everyday. But, for several reasons, I’m afraid the store is dying. Stickers, apps, and store are deeply, excruciatingly buried in iMessage’s confusing UI.