Skip to main content

Good Bye, Spec! Hello Direct Contact with Customers!

It’s been years since I’ve reviewed or wrote a classical specification document. I don’t hear the demand for these documents from engineers anymore, or anyone belabor 30-50 pages of market and functional requirements. So, what’s changed?  Why aren’t people still focused on creating these very important artifacts?

For one, the tools for software development and design have evolved, eliminating a lot of steps and possibly some job functions. I remember coding in the late 90s.  The project I was working involved using C++ and MFC to create a client server system for home loan servicing. In order to create every screen, there was a lot of work that needed to be done – creating the C++ classes, laying out the dialogs, writing stored procedures, etc.  Once completed, getting customer feedback required the business analysts and executives to travel to the customer site and show the software on their machines, or install it off a CD.  It was during this time that the cost of a mistake and the turnaround for feedback could set an entire project back a few days, or even weeks.

Today, I watch my teams execute and it’s a whole different world!  Sometimes they are on a WebEx with a prospective customer adjusting the style sheets and re-rendering the pages on the fly. Writing a document about how a page should look is sometimes a longer process than actually making the page look that way. Chrome developer tools now allow you to render the final product on the screen and make some adjustments in real time. For a lot of technology stacks like Node.js, Ruby and Python, re-compilation is not necessary, and the re-deployment involves just a copy of the files to the demo location.

As a result, I see a lot more engineers take customer meetings. Going through an intermediary to reproduce a bug or get feedback creates the need to translate the message into words, then into documentation, and then back out again.  Of course, there is still support and account management available so the customers aren’t just dialing engineer’s cell phones, however, there is a whole set of activities that seems to have now been eliminated.

This has big implications on the software development world. Think about it - what about the army of product managers, program managers and business analysts?  A big portion of the job required with spec writing seems to have shrunk from fifty pages down to about five. Some have moved into other activities such as analyzing customer usage data, doing competitive analysis, working on market penetration plans. Some long spec writers are still trying to stay relevant, but often times look silly because by the time they are done writing their detailed specification, the engineer already has a working prototype and no one needs to read the spec anymore.

The second relevant change is the importance of soft skills within software development.  All of a sudden the ability to work with people has increased in value dramatically, especially if most of the engineering organization can now do a customer visit, or get on a conference call. Just one loose cannon on your staff will break the culture and patterns. The asshole programmers can only survive in a world where there is a buffer between them and the customers.
Going forward, I expect the tools and methodologies to keep evolving to deliver more customer value faster, resulting in two priorities for everyone – more focus on the value and speed.

Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!

SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Pull Requests and Code Reviews

Software development involves a great deal of collaboration.  One of the most basic blocks of collaboration on a software development team is a code review.  There have been many different ways of doing code reviews over time, some of this has been dictated by the tools available.  Git and online source collaboration tools created a set of best practices that are worthwhile of adopting on any team.

About a month ago I have looked at various articles about how to best create a Pull Request (PR) and do a code review and the attached presentation is the result of this research.  The presentation can help you guide your team and develop a set of collaboration practices that works for your particular situation.

It’s good to start out with why to seek a code review.  Having clarity about your intentions helps you guide the person helping you with code reviews and also to manage your expectations about you can get out of the code review.  The reasons for seeking a code review are generally …

Why you should take the software job in San Francisco (or not).

Silicon Valley is an iconic place for technology.  Many people say this is the place for the “best and the brightest.”. Apple, Google, Facebook, Salesforce, Twitter and other top companies draw a lot of talent form all over the world and the largest chunk of VC capital goes to companies in the Bay Area, so it seems like moving here is a no brainer!

The real situation is actually not that simple, I believe there are three scenarios where it makes sense, but in many cases living in the Bay yields disappointing results.  The cost of living, housing situation, homeless catastrophe make places like San Francisco a lot less appealing to a lot of people.  So in what situations does it make sense to move to SF?

Startup founder raising millions There are many places to be a startup founder, but if you are looking to raise capital the largest pool of VC money is in the Bay Area.  There is an established network, events and conferences which give founders an opportunity to pitch more people th…