cgitechs-public
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Cgitechs-public] moisten appallingly


From: Neville Tolbert
Subject: [Cgitechs-public] moisten appallingly
Date: Fri, 13 Oct 2006 15:42:37 -0000
User-agent: Thunderbird 1.5.0.7 (Windows/20060909)


This is what feels most comfortable to me.
There are fewer places to modify when the requirements change.
Justifiably, these people then become skeptical about polymorphism as well, because it is so strongly linked to inheritance.
Did it bring the expected benefits ?
They are then tempted to give up on OO altogether. There are practical, economic and affective differences. They are then tempted to give up on OO altogether.
Offers subject to change. This is throwing the baby out with the bathwater. Now, more than one protein can have the proper shape to fit into that slot.
Why do you make such a big deal of using index cards for user stories, rather than an electronic document ? Do the same thing on the right hand side, for electronic stories.
Economical in effort - you have hardly moved a muscle. You make a mental note to give Bob a pat on the back soon.
Why do you make such a big deal of using index cards for user stories, rather than an electronic document ? Economical in effort - you have hardly moved a muscle.
It looks great as documentation, but is more cumbersome to write.
You have also not had a conversation, or a chance to notice your coworkers.
At a lower level of abstraction, we may well have different kinds of edits: major, minor, spellcheck, file upload, page deletion.
In fact, you may have sensible reasons to insist on duplication. Responding here serves my purposes just as well.
You make a mental note to give Bob a pat on the back soon.
If allowed to accumulate, waste material interferes with the function of such systems.
Now, more than one protein can have the proper shape to fit into that slot.
It was incredibly simple - I.
We can say everything we have a need to say about that role in one and only one place.
Learn how to use it effectively !
I am sure that people.
For instance, we use tactics like the binary chop: delete half the code, if the bug still occurs it must be in the remaining half, otherwise it was in the deleted half. But I find myself looking at the issue from the other side.
There are fewer places to look for bugs.
We invest time in refactoring duplication out of the code. It feels like ascending a steep slope - sometimes it feels like making no progress at all, in fact.
Kind of spooky - the conference that reads your mind. In fact, you may have sensible reasons to insist on duplication. It feels like ascending a steep slope - sometimes it feels like making no progress at all, in fact.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]