http://dbpedia.org/ontology/abstract
|
Comment programming, also known as comment … Comment programming, also known as comment-driven development (CDD), is a (mostly) satirical software development technique that is heavily based on commenting out code. In comment programming, the comment tags are not used to describe what a certain piece of code is doing, but rather to stop some parts of the code from being executed. The aim is to have the commented code at the developer's disposal at any time it might be needed. This is especially useful when the requirements change rapidly. In this case, they happen to revert to older versions of themselves, thus making the programmer either write the code again, or revert parts of the code from the versioning repository, which would be more time-consuming. With comment programming, when such a request for reverting to an old implementation arises, the developer just comments the current implementation and uncomments the previous. It is advisable to add short descriptive comments to blocks of commented code. A lot of programmers' code acts as a fingerprint. Most of the time, it is sloppy and can be hard to dissect. Even experienced programmers write sloppy code. Comments guide and provide context for the user. Comments can also serve as placeholders for future work. They are useful when constructing outlines of large programs.n constructing outlines of large programs.
|
http://dbpedia.org/ontology/wikiPageExternalLink
|
http://msdn.microsoft.com/sv-se/default.aspx +
|
http://dbpedia.org/ontology/wikiPageID
|
20513631
|
http://dbpedia.org/ontology/wikiPageLength
|
2751
|
http://dbpedia.org/ontology/wikiPageRevisionID
|
1116162811
|
http://dbpedia.org/ontology/wikiPageWikiLink
|
http://dbpedia.org/resource/Class_%28computer_science%29 +
, http://dbpedia.org/resource/Comment_%28computer_programming%29 +
, http://dbpedia.org/resource/Category:Software_development_philosophies +
, http://dbpedia.org/resource/April_Fools%27_Day +
, http://dbpedia.org/resource/Source_code +
, http://dbpedia.org/resource/Design_pattern +
, http://dbpedia.org/resource/Software_development +
, http://dbpedia.org/resource/Code_refactoring +
, http://dbpedia.org/resource/Event_handler +
|
http://dbpedia.org/property/wikiPageUsesTemplate
|
http://dbpedia.org/resource/Template:Compu-prog-stub +
, http://dbpedia.org/resource/Template:Reflist +
, http://dbpedia.org/resource/Template:Short_description +
|
http://purl.org/dc/terms/subject
|
http://dbpedia.org/resource/Category:Software_development_philosophies +
|
http://purl.org/linguistics/gold/hypernym
|
http://dbpedia.org/resource/Technique +
|
http://www.w3.org/ns/prov#wasDerivedFrom
|
http://en.wikipedia.org/wiki/Comment_programming?oldid=1116162811&ns=0 +
|
http://xmlns.com/foaf/0.1/isPrimaryTopicOf
|
http://en.wikipedia.org/wiki/Comment_programming +
|
owl:sameAs |
http://rdf.freebase.com/ns/m.052465k +
, http://yago-knowledge.org/resource/Comment_programming +
, https://global.dbpedia.org/id/4hySx +
, http://dbpedia.org/resource/Comment_programming +
, http://www.wikidata.org/entity/Q5152377 +
|
rdf:type |
http://dbpedia.org/class/yago/Abstraction100002137 +
, http://dbpedia.org/class/yago/Content105809192 +
, http://dbpedia.org/class/yago/Belief105941423 +
, http://dbpedia.org/class/yago/Cognition100023271 +
, http://dbpedia.org/class/yago/PsychologicalFeature100023100 +
, http://dbpedia.org/class/yago/WikicatSoftwareDevelopmentPhilosophies +
, http://dbpedia.org/class/yago/Doctrine105943300 +
, http://dbpedia.org/ontology/TopicalConcept +
|
rdfs:comment |
Comment programming, also known as comment … Comment programming, also known as comment-driven development (CDD), is a (mostly) satirical software development technique that is heavily based on commenting out code. In comment programming, the comment tags are not used to describe what a certain piece of code is doing, but rather to stop some parts of the code from being executed. The aim is to have the commented code at the developer's disposal at any time it might be needed. This is especially useful when the requirements change rapidly. In this case, they happen to revert to older versions of themselves, thus making the programmer either write the code again, or revert parts of the code from the versioning repository, which would be more time-consuming. With comment programming, when such a request for reverting to an old implement request for reverting to an old implement
|
rdfs:label |
Comment programming
|