🔗 97 Things Every Programmer Should Know – Contributions Appearing in the Book

97 Things Every Programmer Should Know – Contributions Appearing in the Book Act with Prudence by Seb Rose Apply Functional Programming Principles by Edward Garson Ask “What Would the User Do?” (You Are not the User) by Giles Colborne Automate Your Coding Standard by Filip van Laenen Beauty Is in Simplicity by Jørn Ølmheim Before You Refactor by Rajith Attapattu Beware the Share by Udi Dahan The Boy Scout Rule by Uncle Bob Check Your Code First before Looking to Blame Others by Allan Kelly Choose Your Tools with Care by Giovanni Asproni Code in the Language of the Domain by Dan North Code Is Design by Ryan Brush Code Layout Matters by Steve Freeman Code Reviews by Mattias Karlsson Coding with Reason by Yechiel Kimchi A Comment on Comments by Cal Evans Comment Only What the Code Cannot Say by Kevlin Henney Continuous Learning by Clint Shank Convenience Is not an -ility by Gregor Hohpe Deploy Early and Often by Steve Berczuk Distinguish Business Exceptions from Technical by Dan Bergh Johnsson Do Lots of Deliberate Practice by Jon Jagger Domain-Specific Languages by Michael Hunger Don’t Be Afraid to Break Things by Mike Lewis Don’t Be Cute with Your Test Data by Rod Begbie Don’t Ignore that Error!...

July 26, 2013 · 4 min · 831 words

📜 Programmers waste enormous amounts of time thinking about, or worrying

Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil. Yet we should not pass up our opportunities in that critical 3%. Donald Knuth (via When optimal matters )...

July 18, 2013 · 1 min · 95 words

🔗 When optimal matters | Playing with Objects

When optimal matters | Playing with Objects The rules of optimization (…) When you are thinking on making an optimization: First time: Don’t do it! Second time: Don’t do it yet! Third time: Ok, but you first profile and measure, and then optimize

July 18, 2013 · 1 min · 43 words

🏞 (image)

Basic Features: Overview of iOS Crash Reporting Tools: Part ½ | Ray Wenderlich Setup Procedures: Overview of iOS Crash Reporting Tools: Part 2/2 | Ray Wenderlich

June 15, 2013 · 1 min · 26 words

📺 Apple – Making a difference. One app at a time.

Apple – Making a difference. One app at a time. (by Apple ) THIS!

June 13, 2013 · 1 min · 14 words

🔗 iPhone & iPad GUI PSD | Teehan Lax

iPhone & iPad GUI PSD | Teehan Lax iPhone PSD This Photoshop template contains all the major iPhone iOS elements to help you design your app. iPad PSD Another PSD template that is made specifically for iPad to help you design your app.

June 2, 2013 · 1 min · 43 words

🔗 Starters Guide to iOS Design

Starters Guide to iOS Design (…) I find that many designers struggle with the transition to UI work, or with the different processes involved in iPhone and iPad app design. In this guide I’ll describe the deliverables you’ll be expected to produce, outline the constraints of the medium and introduce fundamental iOS and UI design concepts.

May 28, 2013 · 1 min · 56 words

🔗 Develop Cross Platform Mobile Apps and Games | Corona Labs

Develop Cross Platform Mobile Apps and Games | Corona Labs Interesting cross-platform mobile development kit, which compiles to native binaries. Uses the Lua programming language . Corona dramatically boosts your productivity. Thanks to our elegant APIs, tasks like animating objects, creating UI widgets or enabling physics take only a few lines of code. Corona is the best solution for developing cross-platform apps for all major platforms and devices. Write once and build to iOS, Android, Kindle Fire and NOOK at the touch of a button....

May 22, 2013 · 1 min · 115 words

🔗 POP – Prototyping on Paper | iPhone App Prototyping Made Easy

POP – Prototyping on Paper | iPhone App Prototyping Made Easy Design on Paper Take Pictures Simulate

May 19, 2013 · 1 min · 17 words

📜 The first 90% of the code accounts for the first 90% of the

The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time. Tom Cargill, Bell Labs (the Ninety-ninety rule )

May 3, 2013 · 1 min · 38 words