In the spirit of Dr. Seuss, this video begins, When a coder sits down to start banging out code, the first thing to start crowding his cognitive load is whether his program will do what it should. “Correctness,” he says, “is what makes my code good.” But it goes on to explain why clean, readable
October 2011 saw the passing of giants: Steve Jobs. You work with his toys everyday. Dennis Ritchie, inventor of the C programming language, co-inventor of Unix. You work with his stuff everyday (but we forget that). John McCarthy, inventor of Lisp. We use the descendants of his invention every day (without realizing it). By his
With few exceptions, using Xcode preprocessor macros is a code smell. C++ programmers have had this beat into them: “Don’t use the preprocessor to do something the language itself provides.” Unfortunately, more than a few Objective-C programmers have yet to get that message. This post is part of the Code Smells in Objective-C series. Here’s
Code smells. I’ve mentioned “code smells” at work, only to discover that my coworkers didn’t know what I meant. It’s basically a diaper-changing metaphor: “If it stinks, change it.” A code smell isn’t “awful code that makes you hold your nose.” Rather, it’s a simple indication that something may need to be changed. Quite often,
What would you give to be able to improve your existing codebase with complete safety? Disclosure: The book links below are affiliate links. If you buy anything, I earn a commission, at no extra cost to you. The Refactoring book completely changed the way I code. In 2001 while searching for information on design patterns, I discovered the
Page [tcb_pagination_current_page] of [tcb_pagination_total_pages]