development

development

A call for simplicity

Posted on Tue, 10/01/2013 - 15:44

You've heard it all before. "The old programmer did this and it's crap" or "This person used this tool and it's no good". It's the age old grudge match between the old and the new. And, it doesn't help anyone move forward. Ultimately, people don't care about the how or why. They want results. What can be done to help limit this scenario moving forward? Standardization (frameworks, design choices, etc) and common practices help, especially when they are documented. Team members can come and go, the work remains consistent. But, this has been well adopted and this issue still exists. Let's try a

development people

Don't solve the same problem twice

Posted on Wed, 09/18/2013 - 23:04

If you spent hours solving a problem, what is the likelihood you will remember exactly what you did the next time it comes around? Don't solve the same problem twice. Find a way to automate routine tasks so you can focus on other challenges. What are some strategies used? Let's start by proposing a frame of reference: We have features, representing software requirements or components We have tools, which create or support features We have configuration, which sets options or behaviors of tools for use in features Let's consider the following example. A restaurant has content management needs

development drupal