Kevin,

Mike is beating a dead horse; we all have seen very crappy code. There is a reason why there is a demand for good programmers.
I totally understand his position on some of the stuff but I'm dumbfounded on some other position. It actually is the first time I saw Mike acknowledge that you can write good systems without mdot. At least that is progress.

I would not even care whether one is using mdot or not.. I'm not, and I have good enough reasons for it.

The problem is that Mike does not seem able to understand that others might no want to put one function in a separate PRG, Not want to have one class per class library, have a sufficient way to avoid the variable-field clash, are not interested to squeeze the last CPU cycle out of the code while 99% of the performance issues are database related.

The inability to understand that other developers might have equally valid reasons to do things differently seems to escape mike entirely. His urge to "teach" people his best practices has become a personal religion, a doctrine, which cannot be questioned or ridiculed, and if you do be prepared for the unavoidable name-calling, insults and so on.

To be honest, this has been a problem with Mike from the beginning. I've been telling him for 2 decades now that in his position where you don't have control over field and variable naming, mdot is the best way to avoid this problem, yet he keeps on claiming that I hold a position that I don't: "mdot should not be used EVER, banned or mdot coders should be outlawed or executed".

Ironically, he labels me as a bully, but if you look at his way of communication towards others, it is clear he is unable to see how he, himself, has been bullying others for over two decades.

I'm going to do my best to ignore mike directly in the future, as long as he does not try to smear my name with lies (as he has done here lately).
He definitely needs to calm down and sort out his troubles.

Walter,




>>Don't bully me to not to push better practices and ignore facts.
>
>Mike, I'm not bullying you. I'm trying to get you to screw your head on straight.
>
>If you don't understand the difference between promoting good practices and common sense, versus these "crappy coder" rants that clearly are laced with personal baggage and invective , then maybe you're not getting half the kicking around you need.
>
>Yes, I've seen apps that were suppose to reset a counter or handle a recycle gracefully, and either kept assigning dupe numbers or did something that caused major issues. Here's a news flash: this industry in practice has never been more than a craft at best. Last week I discovered something in Microsoft Power BI in their "analytics" area that had me dumb-founded. It happens.
>
>Here's an idea: start a blog or a regular series of these "anti-patterns" (for lack of a better term). I used to have a community session for SQL Server user groups on T-SQL no-nos....things that the product allows you to do, but you shouldn't.
>
>You can go a long way towards doing something positive with this, instead of these crybaby-like rants. You are not a victim (except maybe of yourself).