Technical Consultants

As I wind down from my client in Cincinnati, I have been reflecting on the job of technical consultants. In my previous posts, I have reviewed my knowledge and understanding of code. But there’s more to my job, and really all application development members’ jobs than code knowledge. A technical consultant needs to know the internal political climate, the processes in place, and the personnel. The client may be risk averse to technology change, or open source software. It could be a corporate edict, or it could be that your client doesn’t know the benefits of the new technology. The processes may be flawed, but are flawed for a reason. A good consult needs to work within the existing process, move that process to a better one if needed. People are always initially wary of technical consultants, because they fear that they will be replaced. Conversely, technical consultants are keenly aware that they are replaceable, and that they should be replaced, if they have done their job right. A good technical consultant knows the trends, but also knows to read people. Which ones need assurance that their job is not in danger, which ones should focus more on their job, and which ones are ready to pick up new ideas. A good technical consultant has confidence in his abilities, but isn’t afraid to learn new ideas from others. I consider an assignment a success if I have left my client in better shape than when I arrived. I am many things, including an application development person, but my job is more than code.