OO culture
From CSSEMediaWiki
(Difference between revisions)
(New page: * Ward's wiki * OO gurus) |
m (Reverted edits by Ebybymic (Talk); changed back to last version by Warwick Irwin) |
||
| (9 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| + | OO design is not simply about a set of ideas. In order to understand the subject area one must first have an understanding of the minds behind it and the historical circumstances in which it came to exist in its current form. | ||
| + | |||
| + | == People and History == | ||
| − | |||
* [[OO gurus]] | * [[OO gurus]] | ||
| + | * [[The Alexander conspiracy]] | ||
| + | * [[Ward's wiki]] | ||
| + | * [[Hillside Group]] | ||
| + | * [[Gang of Four]] | ||
| + | |||
| + | == More "Culture" == | ||
| + | |||
| + | * [[JUnit]] | ||
| + | * [[427 design standard]] | ||
| + | * [[OO tools]] is a list of a software engineer's arsenal. | ||
| + | * [[What is Bad Design]]? | ||
| + | * [[Professionalism]] is a discussion on professionalism in software engineering. | ||
| + | |||
| + | == Anecdotes from the Industry == | ||
| + | |||
| + | * [http://www.folklore.org/StoryView.py?project=Macintosh&story=Negative_2000_Lines_Of_Code.txt&sortOrder=Sort%20by%20Date&detail=medium&search=lines%20of%20code -2000 Lines Of Code] | ||
| + | |||
| + | == Things to Think About == | ||
| + | |||
| + | * ''The beginning of wisdom for a programmer is to recognize the difference between getting his program to work and getting it right.'' -- M. A. Jackson, 1975 | ||
| + | * [[media:DeMarco.pdf|Software Engineering: An Idea Whose Time Has Come and Gone?]] (PDF) | ||
| + | * [http://doc.cat-v.org/programming/bad_properties_of_OO Bad Engineering Properties of OO Languages] | ||
| + | * [http://heim.ifi.uio.no/~trygver/2009/dci_vision.html The DCI Architecture: A New Vision of Object-Oriented Programming] | ||
| + | * [http://bytebaker.com/2009/03/31/python-properties-vs-java-access-modifiers/ Encapsulation: Python Properties vs Java Access Modifiers] - Has Python got it wrong? | ||
| + | * Can patterns be patented? should they be? [http://www.patentstorm.us/patents/6163813/description.html US Patent 6163813] | ||
| + | * [[Quotes]] | ||
Latest revision as of 03:11, 25 November 2010
OO design is not simply about a set of ideas. In order to understand the subject area one must first have an understanding of the minds behind it and the historical circumstances in which it came to exist in its current form.
Contents |
People and History
More "Culture"
- JUnit
- 427 design standard
- OO tools is a list of a software engineer's arsenal.
- What is Bad Design?
- Professionalism is a discussion on professionalism in software engineering.
Anecdotes from the Industry
Things to Think About
- The beginning of wisdom for a programmer is to recognize the difference between getting his program to work and getting it right. -- M. A. Jackson, 1975
- Software Engineering: An Idea Whose Time Has Come and Gone? (PDF)
- Bad Engineering Properties of OO Languages
- The DCI Architecture: A New Vision of Object-Oriented Programming
- Encapsulation: Python Properties vs Java Access Modifiers - Has Python got it wrong?
- Can patterns be patented? should they be? US Patent 6163813
- Quotes
