Everything is Broken…
There’s more than one occasion where I have uttered the phrase, “Why can’t this just work?” Usually after battling it out with some piece of software that the marketing fluff described as “simple” and “easy-to-use” and turns out to be more like incredibly complex and completely undocumented. I want my technology to just work, but I also want it to be cutting-edge, infinitely configurable, and fully documented. Those who are familiar with the Project Management Triangle may realize that having all three is impossible. To which I say, what about in n-th dimensions?
Seriously though, I have noticed that with the speed of innovation, especially in the cloud, most things that are released are at least partly broken. And that’s not just for beta or preview features, generally available features and functionality are buggy and partly undocumented. Major releases of software have always had some bugs, which is why “It ain’t done till SP1” was a mantra among the Microsoft cognoscenti.
Continue reading “Everything is Broken”
There’s a really good Coalesce song called Burned Bridges, which The Get Up Kids covered. Both versions are awesome so go take a listen, I’ll wait.
The reason I bring it up is not just because it’s a good song, which it is, but because some people prefer to flame out and burn bridges. Recently, I heard that someone I worked with had put in their notice, which was probably a good idea. He had been at the same place a long time, and had become enmeshed in the politics of the organization, and not in a positive way. This led him to be defensive, secretive, and at times cantankerous. A fresh start was definitely in order for both him, and the department he worked in. So, a win-win for everyone. Continue reading “Burned Bridges”
In the last six years I have been lucky enough in IT to be fairly successful and advance my career. Lately I’ve been reflecting on what I did right, and what I might change. In looking to the future and where my path is going, I find I have to look into the past and better understand how I got here. While there was no definitive five year plan, I think there were three pillars that served me faithfully to enable growth and advancement. Continue reading “My Three Pillars”
One of the things that I found most surprising about working in technology, and consulting in particular, is the sheer amount of writing we have to do. When I think about it, on a daily basis I am writing emails, IMs, text messages, documentation, memos, blog entries, or even newsletter articles. You would think that working in technology would be all plugging in cables, configuring software, and running scripts. But instead each day is full of reading and writing. That’s why it is so critical to be mindful of what you write and how you write it. In short, you need to Write it Right.
Writing it Right means adhering to some fundamentals of writing, which include making sure your spelling and grammar are correct. That goes for any writing whether it is an IM, email, or formal document. Obviously, some spelling and grammar errors in chat and text are inevitable, and the medium expects a certain level of informality and brevity. In more formal mediums, such as email and documentation, there really is no excuse for misspelled words or incorrect grammar. The tools to prevent such errors are built right into the products we use to write! It may sound silly, but clients and coworkers can and will judge you by the quality of your writing, so make it easy on yourself and utilize the tools in Word and Outlook to prevent common errors.
Writing it Right also means being aware of the context and content of what you are writing. The language and style you use in an email to a coworker will probably be a little different than what you would use for client communication. Depending on the document type the content should have a sliding level of formality going from the most informal (text/IM) to the most formal (Statement of Work/Final Documentation). Just as you would not put legal verbiage in to a text message or tweet, you also should not put a humorous pun into an SOW. Clients and customer expect professionalism in communication, and may share or forward anything you write to other persons in their organization. When sending an email, think to yourself “Would I want everyone in the client’s company to read this?”. If the answer is “no”, then it’s probably best to reword or skip it. Don’t forget that anything you release out into wild is subject to sharing and legal discovery.
Writing it Right means writing less and being more concise. It also means creating templates and forms to replace manual creation of documents. This is important to create consistency in solution delivery and speed up the process of generating documentation. Writing it Right also means have a back catalog of documentation available. There are many times that I have been able to shorten delivery times or avoid common pitfalls by referring back to documentation on a previous project. Clients also appreciate solid documentation, especially if someone takes over the environment and never received knowledge transfer from the previous custodian. Having an excellent document to refer to can be a lifesaver for them, and a great advertisement for you. When the project is over and you are long gone, the only thing a client has to refer back to is the documentation they were left with. Their impression of the project and its execution is largely informed by the final documentation left behind. Every communication and document that you write is an advertisement for yourself and your competency. Don’t miss a chance to leave a lasting, positive impression.