Bugs, bugs, bugs
-
I love it! In the latest CodeProject news article you have: "A select few beta testers will get their chance to find the unplanned features first, and once they are dealt with appropriately (the bugs, not the beta testers) we'll release to the general audience." Kind of makes me feel that you'll try to fix the bugs found. Microsoft documents them and they remain features. I was certainly happy to see some SQL 2000 "features" bite the dust in Vs. 2005. PS I originally put the title as "Bugs", then that tune that starts out "Men Men Men Men, Men..." started playing in my head for some reason. You may as well suffer with the tune too.
-
I love it! In the latest CodeProject news article you have: "A select few beta testers will get their chance to find the unplanned features first, and once they are dealt with appropriately (the bugs, not the beta testers) we'll release to the general audience." Kind of makes me feel that you'll try to fix the bugs found. Microsoft documents them and they remain features. I was certainly happy to see some SQL 2000 "features" bite the dust in Vs. 2005. PS I originally put the title as "Bugs", then that tune that starts out "Men Men Men Men, Men..." started playing in my head for some reason. You may as well suffer with the tune too.
He he. Back in the early 90s we had a field tester who would always show up with a notepad (paper!), saying "Bugs, bugs, bugs!". We usually managed to convince him that they were "features" or that he was using it wrong. Thanks for reminding me of his catchphrase!
-
He he. Back in the early 90s we had a field tester who would always show up with a notepad (paper!), saying "Bugs, bugs, bugs!". We usually managed to convince him that they were "features" or that he was using it wrong. Thanks for reminding me of his catchphrase!
Would that be a "feature" like code dying? I was asked to test the db processing side of this code. Read the schema for one table. Said to myself, "It makes absolutely no sense to set this field to null, so that's a good one to test." Yep, the UI died. Wrote up a bug saying it doesn't make sense, but if the table field won't be changed, code should handle it gracefully. Code was fixed by next morning. (Way to handle schema you don't own or can't change in this iteration.)
-
I love it! In the latest CodeProject news article you have: "A select few beta testers will get their chance to find the unplanned features first, and once they are dealt with appropriately (the bugs, not the beta testers) we'll release to the general audience." Kind of makes me feel that you'll try to fix the bugs found. Microsoft documents them and they remain features. I was certainly happy to see some SQL 2000 "features" bite the dust in Vs. 2005. PS I originally put the title as "Bugs", then that tune that starts out "Men Men Men Men, Men..." started playing in my head for some reason. You may as well suffer with the tune too.
-
d@nish wrote:
Bugs bugs bugs bugs
Bugly bugs bugs bugs
Bugs bugs bugs bugs bugly bugs wohoo oo oo oo ooftfy
MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
-
d@nish wrote:
Bugs bugs bugs bugs
Bugly bugs bugs bugs
Bugs bugs bugs bugs bugly bugs wohoo oo oo oo ooftfy
MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')