EVERY. SINGLE. PIECE. OF. SOFTWARE. has these kind of stupid bugs. No matter how big, how well funded, or how experienced the team working on it was. It *happens*. Maybe it's typos, off by one errors, a flipped boolean, who knows. But it's there.
-
-
এই থ্রেডটি দেখান
-
Maybe some of the early NASA software came pretty close to being dumb-bug-free, because they were crazy rigorous about that stuff. But modern software is just too damn big to catch it all. We're only human.
এই থ্রেডটি দেখান -
That being said, when I see this particular class of errors I can't help but think...
pic.twitter.com/QJFVamBEUh
এই থ্রেডটি দেখান
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
-
-
True, but: it was exactly stuff like this why we banned any sort of interpreted scripting language about 15 years ago from all workflows. And this sort of problem happens when the bean counters declare that a proper QA team right from the start of the project is too expensive.
-
...of course similar bugs *are* lurking in every code base (e.g. Ghandi overflow bug in Civ), but I think in this case at least the QA should have noticed that the AI suddenly broke from one day to the other. It *does* sound like there was no proper build-test-fix loop in place.
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
লোড হতে বেশ কিছুক্ষণ সময় নিচ্ছে।
টুইটার তার ক্ষমতার বাইরে চলে গেছে বা কোনো সাময়িক সমস্যার সম্মুখীন হয়েছে আবার চেষ্টা করুন বা আরও তথ্যের জন্য টুইটারের স্থিতি দেখুন।