I’ve noticed time and again that if I perform an audit on any part of a project where no one before me has, I invariably stumble upon some horror. It’s almost worth taking bets on it soon.
Simply take something that’s been somewhat working for years, that no one has bothered to look into because it works, and you’ll discover that a process is being triggered 50 times when once would suffice, or there’s a security breach, or something else.
The reasons for this are usually an excessive adherence to the “if it ain’t broke, don’t fix it” principle, and not enough attention paid to “what could go wrong” during the development phase. It’s just that things “going wrong” don’t always lead to noticeable problems. If you have five million products in your catalogue, 10,000 broken ones hardly make a dent. Until some customer reports it, that is.
Maybe I should have gone into testing? I’ll go check what courses are available.
Hi, I'm Rauf Aliev. 