Some perspective on difficult customers

Posted on Wed, 10/02/2013 - 20:03

We've all had to deal with difficult people at work. It doesn't get easier when the difficult people are those you serve. My director once shared his thoughts on a particular audience and it has stuck with me. In higher ed, some of those served are faculty members that have made their living questioning the world around them in research. This same perspective very likely is what elevated these folks above their peers and afforded them opportunities. Looking at this group in this light, it's no suprise that they are labeled as critical or difficult to work with. Some do not have the ability to

people

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

Learning is giving, not just receiving

Posted on Thu, 09/26/2013 - 21:13

I recently read this article: http://bryanbraun.com/2013/09/21/please-stop-stewing-and-start-blogging… You can't ask for a better justification to throw up a blog and share some information. It made me realize a few things. First: You have an opportunity to help others out because you most likely learned something someone could benefit from. Second: Don't be shy. If anything, someone may post a comment and share information with you again. Third: Tools like Drupal were built by people who were not afraid to give back. Step up and take your turn.

drupal 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

Welcome

Posted on Wed, 09/18/2013 - 22:06

Well... here goes nothing. I've always wanted a way to share the things I've learned. Good programmers learn from their mistakes. The best programmers then share the love. I welcome your thoughts and encourage you to engage in conversation through comments. Thanks for visiting.