Alan Gauld wrote:
>> I think you work at a much larger scale (of program size) than I do
>
> That's probably true.
>
> An average project for me involves about 3 months of architecture/design
> generating maybe 5 or 6 workpackages given to different teams, each of
> which will comprise between 10
> I think you work at a much larger scale (of program size) than I do
That's probably true.
My day job is as a systems architect/designer, most of the real coding
is done by development teams scattered across the country. I use
Python to prove the concepts of my design before converting it into
Ja
Alan Gauld wrote:
> I never use commonality of data to define a class. OK I lie, sometimes
> its just convenient to do it that way, but as a principle
> such classes are rarely extensible, they tend to be more like records in
> structured programming speak.
Very few of my classes are ever extend
Hi Kent,
>> point. Classes express behaviour, the data is only there to support
>> the behaviour. Thats why methods are polymorphic but not attributes.
>>
>> So you think of a class having an interface and users extending
>> or modifying the behaviour, not the data.
> I think of a class in ter
Alan Gauld wrote:
> That might be part of the problem, if you think of a class in terms
> of its data attributes then that is nearly always the wrong starting
> point. Classes express behaviour, the data is only there to support
> the behaviour. Thats why methods are polymorphic but not attribut
