i'd slightly disagree with this point. i think the patch addressed the 3 biggest issues in the released game, the regular crashes, the inability to play shots in large areas of the field, and the guarantee that the AI would hit the last ball of the over for 4. we can say it was a "successful" patch in those terms.
but, i believe the patch introduced some issues too: i think the AI is weaker in terms of general batting strength. in FC, they pace themselves well but don't bat long enough to build a big score. they'll bat for circa 80-90 overs at a rate around 3-3.5 an over, so they can't build a big score. (individually i've not had anyone score a ton against me). i've personally had less stability since the patch (less crashes, but several instances of frankly crazy gameplay that could be resolved only by deleting all data). the bottom line is pre-patch 3 i completed nearly every game i started. since the patch i've completed very few, probably less than i did in dbc14 before franco's hack.
i don't believe we should criticise a studio for over-ambition, but it's clear that BA's reach exceeded their grasp and it has led to a game that has some sublime things and some really poor things. the UX is just one of the worst things i've ever endured*, and the management of the data in the game is shockingly bad. i don't even just mean stats (though they combine being both meagre and wrong, which is quite an acheivement) but also things like when you link a player, that should leave you with only 1 instance of the player but you end up with 3. my player database in DBC14 was clean: it took a while because of the amount of players but otherwise it was easy enough to ensure I had only 1 instance of each player and where possible they were linked correctly. in DBC17 i've never been able to get that sorted, because attempting to do so is a Kafka-esque nightmare (and since the game can't track the stats properly, what is the point anyway?).
sadly at the moment the game is less than the sum of its parts. i still haven't quite worked out how we've ended up with a game made by people who understand and love cricket enough that the hardness of the pitch can effect where you want your keeper / slips to stand, yet who also somehow thought having moving adboards and mexican-waving crowds behind the bowler's arm was acceptable? (i get it might have been different teams, but still... how did nobody ever spot the movement behind the bowler's arm and say no?)
that said - i think BA have more than enough credibility to be given the benefit of the doubt and the time to get it right.
*this community bears a lot of responsibility for the UX. last summer i had a lot going on and for lots of reasons wasn't really involved in the academy beta. but i saw so many posts here along the lines of "great update, this academy is great, easy to use etc." and not one saying "2012 called: Windows 8 sucked ass take your tiles and do one..."