>>> The only people likely to be offended are those who recognise themselves
>>> to be guilty of the bad practices which I have identified, and as I
>>> don't place any value on the opinions of such people I don't care if
>>> they are offended or not.
>> Thanks for the best 'coffee moment' of the day.
>> Golly, you are a self-opinionated little prick, aren't you?
> At least I have opinions.
That the whole problem. That's all they are.
Opinions.
And you seem PROUD of that?
>The fact that you don't like them doesn't
> concern me in the least.
Its not the opinions I don't like....they are not worth liking or disliking..
-- Ineptocracy
(in-ep-toc’-ra-cy) – a system of government where the least capable to lead are elected by the least capable of producing, and where the members of society least likely to sustain themselves or succeed, are rewarded with goods and services paid for by the confiscated wealth of a diminishing number of producers.
On 2012-11-05, Tony Marston <TonyMars...@hotmail.com> wrote:
> When you design your database for your application are you aware that
> some of your design decisions can have a detrimental effect when it comes to
> writing the code to access that database? I have been designing databases,
> and building the applications which use them, for several decades, and I
> have learned over the years that there are some design decisions which help
> the developer while others do nothing more than hinder. I have produced a
> document which lists 14 of these “hindrances” which can be read at
> http://www.tonymarston.net/php-mysql/database-design-ru-novice-ninja-...
I know that database design is *very* important. One needs to think longer
and harder about its structure than almost all people think. For it is
important.
>On 2012-11-05, Tony Marston <TonyMars...@hotmail.com> wrote:
>> When you design your database for your application are you aware that
>> some of your design decisions can have a detrimental effect when it comes >> to
>> writing the code to access that database? I have been designing >> databases,
>> and building the applications which use them, for several decades, and I
>> have learned over the years that there are some design decisions which >> help
>> the developer while others do nothing more than hinder. I have produced a
>> document which lists 14 of these “hindrances” which can be read at
>> http://www.tonymarston.net/php-mysql/database-design-ru-novice-ninja-...
>I know that database design is *very* important. One needs to think longer
>and harder about its structure than almost all people think. For it is
>important.
Yes, it *IS* important. Very, very important. It is also important that it is designed correctly otherwise it could have a detrimental effect on the software which is supposed to access it. It is wrong to say that *any* design is acceptable because after many years of being exposed to different design ideas I can say that some ideas are definitely better than others. The purpose of my article was to say "you may think that these database design ideas are good, but they are not as good as you think, and here are the reasons why".
>>>> The only people likely to be offended are those who recognise >>>> themselves
>>>> to be guilty of the bad practices which I have identified, and as I
>>>> don't place any value on the opinions of such people I don't care if
>>>> they are offended or not.
>>> Thanks for the best 'coffee moment' of the day.
>>> Golly, you are a self-opinionated little prick, aren't you?
>> At least I have opinions.
>That the whole problem. That's all they are.
>Opinions.
>And you seem PROUD of that?
>>The fact that you don't like them doesn't
>> concern me in the least.
>Its not the opinions I don't like....they are not worth liking or >disliking..
Why don't you grow up and criticise the message instead of the messenger. I don't care whether you like me or not, or the way that I say things. It is *WHAT* I say which is important.
By saying that you disagree with my message you are announcing to the world that you regularly employ all those bad practices in your database designs, which means that your database designs are not as good as you think they are. If you disagree with the numerous points which I identified in my article can you do the grownup thing and provide contra-arguments? Or are you incapable of anything except personal abuse?
>On 2012-11-05, Tony Marston <TonyMars...@hotmail.com> wrote:
>> When you design your database for your application are you aware that
>> some of your design decisions can have a detrimental effect when it comes >> to writing the code to access that database? I have been designing >> databases,
>> and building the applications which use them, for several decades, and I
>> have learned over the years that there are some design decisions which >> help the developer while others do nothing more than hinder. I have >> produced a
>> document which lists 14 of these “hindrances” which can be read at
>> http://www.tonymarston.net/php-mysql/database-design-ru-novice-ninja-...
>I know that database design is *very* important. One needs to think longer
>and harder about its structure than almost all people think. For it is
>important.
Yes, it *IS* important. Very, very important. It is also important that it
is designed correctly otherwise it could have a detrimental effect on the
software which is supposed to access it. It is wrong to say that *any*
design is acceptable because after many years of being exposed to different
design ideas I can say that some ideas are definitely better than others.
The purpose of my article was to say "you may think that these database
design ideas are good, but they are not as good as you think, and here are
the reasons why".
>>>>> The only people likely to be offended are those who recognise
>>>>> themselves
>>>>> to be guilty of the bad practices which I have identified, and as I
>>>>> don't place any value on the opinions of such people I don't care if
>>>>> they are offended or not.
>>>> Thanks for the best 'coffee moment' of the day.
>>>> Golly, you are a self-opinionated little prick, aren't you?
>>> At least I have opinions.
>> That the whole problem. That's all they are.
>> Opinions.
>> And you seem PROUD of that?
>>> The fact that you don't like them doesn't
>>> concern me in the least.
>> Its not the opinions I don't like....they are not worth liking or
>> disliking..
> Why don't you grow up and criticise the message instead of the
> messenger. I don't care whether you like me or not, or the way that I
> say things. It is *WHAT* I say which is important.
Except they are not new and not important.
> By saying that you disagree with my message you are announcing to the
> world that you regularly employ all those bad practices in your database
> designs, which means that your database designs are not as good as you
> think they are.
No, I am not announcing anything of the sort, and its yours blinded egotiss that makes you say that.
> If you disagree with the numerous points which I
> identified in my article can you do the grownup thing and provide
> contra-arguments? Or are you incapable of anything except personal abuse?
Oh *I* am capable of much more ..its you that is resorting to personal abuse.
"Let me tell you a secret I learnt from a witch: Water is Wet!".
Its only the crass ignorance you must have laboured under to regard anything you have said as more than the most basic elementary knowledge that anyone who approaches database design must know already.
The astonishing thing is not that you have arrived at it, but that you appear to think that no one else has - the reality is its second nature to the point where its not worth remarking upon.
-- Ineptocracy
(in-ep-toc’-ra-cy) – a system of government where the least capable to lead are elected by the least capable of producing, and where the members of society least likely to sustain themselves or succeed, are rewarded with goods and services paid for by the confiscated wealth of a diminishing number of producers.
>> On 2012-11-05, Tony Marston <TonyMars...@hotmail.com> wrote:
>>> When you design your database for your application are you aware that
>>> some of your design decisions can have a detrimental effect when it
>>> comes to writing the code to access that database? I have been
>>> designing databases,
>>> and building the applications which use them, for several decades, and I
>>> have learned over the years that there are some design decisions
>>> which help the developer while others do nothing more than hinder. I
>>> have produced a
>>> document which lists 14 of these “hindrances” which can be read at
>>> http://www.tonymarston.net/php-mysql/database-design-ru-novice-ninja-...
>> I know that database design is *very* important. One needs to think
>> longer
>> and harder about its structure than almost all people think. For it is
>> important.
> Yes, it *IS* important. Very, very important. It is also important that it
> is designed correctly otherwise it could have a detrimental effect on the
> software which is supposed to access it. It is wrong to say that *any*
> design is acceptable because after many years of being exposed to different
> design ideas I can say that some ideas are definitely better than others.
> The purpose of my article was to say "you may think that these database
> design ideas are good, but they are not as good as you think, and here are
> the reasons why".
Breathing is very important too, to the point where if you stop, its a permanent bug.
-- Ineptocracy
(in-ep-toc’-ra-cy) – a system of government where the least capable to lead are elected by the least capable of producing, and where the members of society least likely to sustain themselves or succeed, are rewarded with goods and services paid for by the confiscated wealth of a diminishing number of producers.
>>>>>> The only people likely to be offended are those who recognise
>>>>>> themselves
>>>>>> to be guilty of the bad practices which I have identified, and as I
>>>>>> don't place any value on the opinions of such people I don't care if
>>>>>> they are offended or not.
>>>>> Thanks for the best 'coffee moment' of the day.
>>>>> Golly, you are a self-opinionated little prick, aren't you?
>>>> At least I have opinions.
>>> That the whole problem. That's all they are. Opinions.
>>> And you seem PROUD of that?
>>>> The fact that you don't like them doesn't
>>>> concern me in the least.
>>> Its not the opinions I don't like....they are not worth liking or
>>> disliking..
>> Why don't you grow up and criticise the message instead of the
>> messenger. I don't care whether you like me or not, or the way that I
>> say things. It is *WHAT* I say which is important.
>Except they are not new and not important.
Then show me any resource on the internet which identifies these same points.
>> By saying that you disagree with my message you are announcing to the
>> world that you regularly employ all those bad practices in your database
>> designs, which means that your database designs are not as good as you
>> think they are.
>No, I am not announcing anything of the sort, and its yours blinded egotiss >that makes you say that.
>> If you disagree with the numerous points which I
>> identified in my article can you do the grownup thing and provide
>> contra-arguments? Or are you incapable of anything except personal abuse?
>Oh *I* am capable of much more ..its you that is resorting to personal >abuse.
Show me where in any of my posts where I have used personal abuse? *YOU* are the one who keeps calling me a self-opinionated prick, not the other way around.
