Re: OO Specs
- From: "black ares" <matematicianu2003@xxxxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Fri, 8 Oct 2010 08:42:51 +0300
let me stress some point on your affirmation.
It is true that doing real projects gain you the experience necesary to grow
in this domain.
But, reading different materials on the subject is also important, because
you can find there technics that you may be not are aware of, or you didn't
discover them by simply working.
There are a lot of software developer out there that develop better or less
software working on their own knowledge, but a few of them go the right way
because they knew the ood principles, knew some pragmatic principles and
aplied best technology ant methodology for their project.
For example, for business logic in a project there are out there five or
more patterns to work with, each of them having its own advantages and
disatvantages.
For example I know
transaction script process
table module
Active Record
Domain model.
I gained awareness of some of them simply reading, because beeing onest I
simply found two of them in the real world project of mine, domain model and
active record.
But the other two are not less important, because, thei offer speed in
developing if the project permits it.
In conclusion, is a fact that all of us can write classes, properties and
methods, but its matter how do you write them.
Other way, there are a great colection of antipaterns out there, which,
first viewed make use of all oop principles, encapsulation, inheritance and
polymorphism.
On the other hand, working with out lecture in etail on the subject, may
arise to another strange situation.
For example I worked a lot of years, creating architectures, creating
software, doing things because the comon sense dicted me that that way is
better to do things and not the other.
Now I decided to read some books on the subject to see what is new.
Surprise a lot of concepts discovered there in the books I have already
known them by my own discovering, but I didn't know their standardised name
and therminology.
For example I used domain driven principles even earlier than 2003 when it
was standardised, but I didn't feel that it was so great, it was simply a
thing which have done my things work.
After the standardisation, I was in some interviews where I was asked if I
know domain driven design.
Not knowing that that is the name of what I've used, I sincerely said no,
loosing the interview.
Now, In 2010 I decided to see what the hell is that domain driven design and
realised what stupid I was.
Don't take it personaly, I simply presented some of my experiences.
Best regards
Black Ares
----- Original Message -----
From: "Jamal Mazrui" <empower@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Cc: "Homme, James" <james.homme@xxxxxxxxxxxx>
Sent: Friday, October 08, 2010 4:58 AM
Subject: Re: OO Specs
Hi,
I do not have an answer to the particular question, and would be
interested in reading that article, too, so please share the web address
if you find it.
My understanding of OOP involves the following points:
* In the context of the application, think of nouns as potential objects,
which would be defined as classes with certain attributes, defined as
either public properties or private fields (variables that retain
configuration values of any data type), and methods, which define actions
that the object is capable of performing.
* The properties are attributes that may be changed by external clients of
the API.
* The fields are attributes of the object that can only be changed by
internal procedures of the API, not accessible to external clients.
* Any time an object could benefit from automatically being informed of an
action by another object, particularly if it includes a change of one of
its own properties by an external client, a method of that object may be
automatically be triggered in response to that action, which is also
called an event handler method.
Personally, I think the best way to learn most programming concepts is to
try to implement them in a project of personal interest, usually one of
direct, practical significance, or at least, passionate, principled
interest. Keep asking questions until you find the answers to implement
that project of personal significance. In my opinion, without the real
application of knowledge, little conceptual understanding is actually
gained.
Best,
Jamal
On 10/7/2010 3:02 PM, yHomme, James wrote:
Hi,
I used to have a bookmark that lead to something that told me how to
take a description of what you want a piece of software to do and decide
the objects, methods, and behaviors it would have. Does anyone have
links to this kind of thing?
Thanks.
Jim
Jim Homme,
Usability Services,
Phone: 412-544-1810. Skype: jim.homme
Internal recipients, Read my accessibility blog
<http://mysites.highmark.com/personal/lidikki/Blog/default.aspx>.
Discuss accessibility here
<http://collaborate.highmark.com/COP/technical/accessibility/default.aspx>.
Accessibility Wiki: Breaking news and accessibility advice
<http://collaborate.highmark.com/COP/technical/accessibility/Accessibility%20Wiki/Forms/AllPages.aspx>
This e-mail and any attachments to it are confidential and are intended
solely for use of the individual or entity to whom they are addressed.
If you have received this e-mail in error, please notify the sender
immediately and then delete it. If you are not the intended recipient,
you must not keep, use, disclose, copy or distribute this e-mail without
the author's prior permission. The views expressed in this e-mail
message do not necessarily represent the views of Highmark Inc., its
subsidiaries, or affiliates.
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
Other related posts:
