GoFuckYourself.com - Adult Webmaster Forum - View Single Post

sarettah · 08-05-2012, 10:32 AM

SOMP produces most of the code you are talking about. Programmers that use the SOMP methodology usual produce working code very rapidly but it often is not up to the SNOB methodology of programming standards in that it often produces straight line, right to the heart of the matter code.

SOMP programmers feel that a lot of internal documentation is unnecessary for several reasons:

1. It adds time to a project. As many SOMP studies have demonstrated. The time taken to develop a project can actually double bedause of ANAL documentation. This increases the time and therefore the cost of the project.

2. SOMP developers feel that any decent developer can read code and should be able to decipher what is going on. They do not feel that it is totally necessary to caption every "If...then...Else" statement with ridiculous paragraphs stating that they are going to now make a decision and take some action on the basis of that decision.

3. SOMP developers have found that it is in their best survival interests to produce commentless code because it is the common misconception of clients (usually being told this by SNOB developers) that commentless code is very hard to follow and therefore the client feels they need to stick with the original developer. This ensures that the original developer gets first shot at upgrades in the future.

SOMP developers often do not use many classes and some do not even use modules or developer designed functions. Often the code is just a straight line or loop. Start, do this, do this, do this, end. SOMP developers feel that many developers stress classes and modularity to excess and that SNOB programmers often waste time and effort building classes and modules for no other reason that they have bought into the dogma that object orientation solves everything and that if something is not built into classes then it is inherently wrong (25 years ago the same arguments were made by the then SNOB developers that everything had to use a relational structure or it was wrong).

Most SOMP developers can use classes, modules and functions as well as any other developers. They prefer to use the best tool, of the available tools, for the job at hand.

They go in. They do the job and they are done. They do not bullshit around worrying about whether they could have made it prettier. They do not worry about whether someone else will be able to follow them up. They are down and dirty, rapid fire developers.

Or at least that's what I've heard.

.

08-05-2012, 10:32 AM
sarettah see you later, I'm gone Industry Role: Join Date: Oct 2002 Posts: 14,099	SOMP produces most of the code you are talking about. Programmers that use the SOMP methodology usual produce working code very rapidly but it often is not up to the SNOB methodology of programming standards in that it often produces straight line, right to the heart of the matter code. SOMP programmers feel that a lot of internal documentation is unnecessary for several reasons: 1. It adds time to a project. As many SOMP studies have demonstrated. The time taken to develop a project can actually double bedause of ANAL documentation. This increases the time and therefore the cost of the project. 2. SOMP developers feel that any decent developer can read code and should be able to decipher what is going on. They do not feel that it is totally necessary to caption every "If...then...Else" statement with ridiculous paragraphs stating that they are going to now make a decision and take some action on the basis of that decision. 3. SOMP developers have found that it is in their best survival interests to produce commentless code because it is the common misconception of clients (usually being told this by SNOB developers) that commentless code is very hard to follow and therefore the client feels they need to stick with the original developer. This ensures that the original developer gets first shot at upgrades in the future. SOMP developers often do not use many classes and some do not even use modules or developer designed functions. Often the code is just a straight line or loop. Start, do this, do this, do this, end. SOMP developers feel that many developers stress classes and modularity to excess and that SNOB programmers often waste time and effort building classes and modules for no other reason that they have bought into the dogma that object orientation solves everything and that if something is not built into classes then it is inherently wrong (25 years ago the same arguments were made by the then SNOB developers that everything had to use a relational structure or it was wrong). Most SOMP developers can use classes, modules and functions as well as any other developers. They prefer to use the best tool, of the available tools, for the job at hand. They go in. They do the job and they are done. They do not bullshit around worrying about whether they could have made it prettier. They do not worry about whether someone else will be able to follow them up. They are down and dirty, rapid fire developers. Or at least that's what I've heard. . __________________ All cookies cleared! Last edited by sarettah; 08-05-2012 at 10:37 AM..