Who’s more annoying for the product & technology team in a tech/online company like carsales.com – a member of the executive team who knows little to nothing about developing product or one that knows something about it (or thinks they do)?
I’m in the latter group of this question having started as a software developer at the end of 1988 moving into the 90’s. I look at changes we need to make and get impatient on delivery times. I can’t help it. I think back to when I was developing and if I had something in front of me that could make a difference in the product, we just seemed to make it happen, “from go to whoa“.
The software life cycle for me went like this as I would:
— Scope the product;
— Develop the product;
— Test it;
— Document (in the code and for users, sometimes);
— Deploy the product into the release cycle; and
— Then support it (when a software release was made available).
I was in total control. We had over a dozen developers all with the same life cycle for changes big and small. We would do a new software release containing hundreds of changes twice a year. The end product was used by hundreds of dealers and thousands of users around Australia.
There are quite a few differences from the 90’s to now in software development but the number 1 difference has to be plainly and simply 1 thing:
The rate of change, always available and number of users make the processes of the 90’s obsolete. Like today, we had thousands of features as well as integrations and dependencies throughout many products but 3 things we didn’t have to factor in were:
1. Code being pushed live multiple times per day – the quarterly release schedule that regularly got pushed to half yearly is long gone
2. 99.9% plus availability for users – we always had windows where we could bring the system down for a number of hours to fix or upgrade something
3. Having a scalable and reliable system and code base to handle millions of users and millions of actions per second not to mention hosting in “the cloud” – this adds complexity and cost, especially for disaster recovery which has to be a staple
We all take the Internet for granted and the change it has had on our lives.
Oh for the good old days of software development….