Differences between current version and predecessor to the previous major change of CorporateProgramming.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 3 | Last edited on Sunday, May 7, 2006 1:11:29 pm | by LawrenceDoliveiro | |
| Older page: | version 2 | Last edited on Sunday, May 7, 2006 11:11:35 am | by CraigBox | Revert |
@@ -1,11 +1,11 @@
__Controversial__--a term proposed to describe a culture of software development which puts greater emphasis on the processes followed than on the actual results. Often found in environments, such as internal development projects in large corporate companies, where the users don't have any choice about the software they are given.
-Fond of adopting new, complicated-sounding technologies in the fond belief that they will improve software quality (e.g. [UML]), in spite of complete lack of any evidence to this effect. Prefers ObjectOrientation to [data abstraction|WikiPedia:Data_abstraction]; [design patterns|PPR:DesignPatterns] to [code reuse|PPR:SoftwareReuse]. Where languages like [Java] or [C++] are in heavy use, there is a good chance you will find Corporate Programming at work.
+Fond of adopting new, complicated-sounding technologies in the fond belief that they will improve software quality (e.g. [UML]), in spite of complete lack of any evidence to this effect. Prefers ObjectOrientation to [data abstraction|WikiPedia:Data_abstraction]; [design patterns|PPR:DesignPatterns] to [code reuse|PPR:SoftwareReuse]. Where languages like [Java], [C#
] or [C++] are in heavy use, there is a good chance you will find Corporate Programming at work.
See ''[It Takes A Project To Raze A Forest|http://www.linuxplanet.com/linuxplanet/opinions/6233/1/]'' for an argument similar to this. Also a quote from elsewhere:
For example, in the OO world you hear a good deal about "patterns". I wonder if these patterns are not sometimes evidence of ... the human compiler, at work. When I see patterns in my programs, I consider it a sign of trouble. The shape of a program should reflect only the problem it needs to solve. Any other regularity in the code is a sign, to me at least, that I'm using abstractions that aren't powerful enough....
-- [Paul Graham|http://www.paulgraham.com/icad.html]
CategoryProgramming
