Skip to main content

First Public Beta of DS Pro is *DONE*

The last signature has gone on the sign off document.  The team is gathering early feedback on the product and everyone is starting to get a warm fuzzy feeling of accomplishment.  Releasing software is fun.

To a certain degree it is always a gamble.  You are gambling that people will find your software useful.  You are gambling that you can achieve the quality customers expect.  You are gambling that you can provide the solutions for the problems scheduled by the sprint.

At the time of shipping a lot of the stars need to align.  If I was to compare shipping software to something I would compare it to the game of football - absolutely everyone needs to play their position and know what other people are doing or the entire process doesn't work.

Project Management needs to clear up the obstacles and take the paper work load off the technical staff.  Development needs to produce features and minimize bugs.  Quality Assurance needs to define the right test passes and run them to show the quality of the product.  If any one of those disciplines doesn't play their role correctly the product doesn't ship.

While all these people are involved in any part of the software process it is only during shipping that you see the hard decisions being made and the trade offs play out.  When I was at Microsoft it was a pleasure working with people who have gone through this process many times.  Everyone knew what to expect and what tradeoffs meant.

DS Pro team uses Agile, iterative approach.  It works out great because people get to practice making tradeoffs every single month.  Every month you have to deliver something useful and every month people understand how to cut features, what resources are needed, who needs to do what and by when.

Some people think that you can teach this through a book.  I don't believe so.  You need to experience this first hand before you start getting a feeling of what's important and why. 

Asides from technical issues every new group of individuals poses it's own challenges.  We started out with people taking really hard positions on certain issues and over time they realized that the most important thing is how we play together in order to deliver innovation to the market place.

We are currently in a position where we can make a lot of people's lives easier.  While there is a potential for a profit it is also important to realize that if we can't get our act together we miss an opportunity to improve someone's quality of life.

Comments

Popular posts from this blog

Quality of Code is Quality of Life

About 20 years ago when I started working in technology companies I remember “the best” engineers had similar patterns:
-They worked crazy hours
-They knew the systems no one else knew
-They could react and deliver something faster than anyone else
You could always hear other employees say: “Bob is really smart, no one knows how to get anything done in system X besides him!”

This reinforced optimization around being the only person who knew how to do something in some part of the code.  That in turn reinforced job security and bargaining for those engineers, but also chained them to a particular system.  We had big code bases of C++ or Java code where some “Bob” hacked up features as soon as he possibly could.  “Bob” would have occasional nuclear disasters where he’d sleep in the office or through the weekend and then everyone would thank him for how he “saved the day.”  “Bob” sacrificed his quality of life to get praise when he hacked stuff up quickly and then the second time when n…

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!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of
different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers.

Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily accessible…