Getting Things Done in Programming: Part 1

As farse as the title sounds, every character of code I write, less is certainly more. In programming its natural to complicate a task. However you begin to realize that its about taking the path of least resistance. Lets take a look.Extraction

With the continual rise of OOP methodologies, extraction is becoming more of a concern. Whether you’re streamlining a big content management system or sprinkling dynamic functionality on a single web page, you’ll be more or less extracting

DRY (Don’t Repeat Yourself)

A problem programmers have with languages like PHP is a lack of good DRY methods. In most cases this at the mercy and skill level of the developer. The best way to approach this is to take simple aspects of a task and extract them. When push comes to shove its always small details that get the most attention anyway. There is nothing worse than retyping the same small details over and over.

Sometimes It Just Doesn’t Matter

Often times I find myself spending to much time on a feature. Usually you find there are simpler ways to get the job done or its just not necessary. Making decisions in web development is important. Discerning between the necessary and the bells and whistles will get you further along than expected. Keep it lean and simple. Get out of your user’s way.

In part 2 I will be discussing programmer-t0-designer communication. Stay tuned.


About this entry