To All,
Every now and then I have a 'holy war' with new colleagues (I hop a lot) about the naming of classlibs. E.g., should the highest/base classlib be named after the 'owning' company and should we only use a subclass of that classlib in a specific application, and name the subclassed lib after the application? Like:
abcBase.vcx Your company ABC?
abcReporting.vcx Based on base classes in abcBase.vcx?
defBase.vcx Subclass of abcBase.vcx for your customer 'company DEF'?
defReporting.vcx Subclass of abcReporting.vcx for your customer 'company DEF'?
ghiBase.vcx Subclass of defBase.vcx for your customer's application GHI?
ghiReporting.vcx Subclass of defReporting.vcx for your customer's application GHI?
I don't want to start a holy war, but I'm quite interested in your naming conventions!
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
