Intellectual Control [Pragmatic Designer]
In the early days of software engineering, Edsger Dijkstra warned us not to let the size and complexity of our programs cause us to lose “intellectual control” due to the limited nature of our minds. To my knowledge, he never defined precisely what intellectual control was. Our software today is sta...
Gespeichert in:
| Veröffentlicht in: | IEEE software 2019-01, Vol.36 (1), p.91-94 |
|---|---|
| 1. Verfasser: | |
| Format: | Artikel |
| Sprache: | eng |
| Schlagworte: | |
| Online-Zugang: | Volltext bestellen |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
| container_end_page | 94 |
|---|---|
| container_issue | 1 |
| container_start_page | 91 |
| container_title | IEEE software |
| container_volume | 36 |
| creator | Fairbanks, George |
| description | In the early days of software engineering, Edsger Dijkstra warned us not to let the size and complexity of our programs cause us to lose “intellectual control” due to the limited nature of our minds. To my knowledge, he never defined precisely what intellectual control was. Our software today is staggeringly larger than the programs of the 1960s, so does that mean we have it under our intellectual control, or did we find ways to make progress without Dijkstra’s high standards? I see signs that we have some software that is under intellectual control and other software that is not. In this column, I’m going to discuss how we can recognize these two categories, what happens when engineers on a project have different attitudes about intellectual control, some advice on when we probably should insist on it, and some ideas about how we achieve it. |
| doi_str_mv | 10.1109/MS.2018.2874294 |
| format | Article |
| fullrecord | <record><control><sourceid>proquest_RIE</sourceid><recordid>TN_cdi_ieee_primary_8611447</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>8611447</ieee_id><sourcerecordid>2169460368</sourcerecordid><originalsourceid>FETCH-LOGICAL-c330t-8f85f7a61aa8e6d7024819eb1c7fd9cd8b7244d09cff112046b7e5f21dcf365b3</originalsourceid><addsrcrecordid>eNo9kE1LAzEURYMoWKtrF24KrlxM-16SycdSxqqFFoXqSiRkMkmZMp2pyXThv7elxdXdnHsvHEJuEcaIoCeL5ZgCqjFVklPNz8gANZMZR83PyQAkh0zyXF-Sq5TWAJAjgwF5mLW9bxrv-p1tRkXX9rFrRl_v0a42tq_d6MmnetX6-H1NLoJtkr855ZB8Pk8_itds_vYyKx7nmWMM-kwFlQdpBVqrvKgkUK5Q-xKdDJV2lSol5bwC7UJApMBFKX0eKFYuMJGXbEjuj7vb2P3sfOrNutvFdn9pKArNBTCh9tTkSLnYpRR9MNtYb2z8NQjm4MMslubgw5x87Bt3x0btvf-nlUDkXLI_GElaZQ</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>2169460368</pqid></control><display><type>article</type><title>Intellectual Control [Pragmatic Designer]</title><source>IEEE Electronic Library (IEL)</source><creator>Fairbanks, George</creator><creatorcontrib>Fairbanks, George</creatorcontrib><description>In the early days of software engineering, Edsger Dijkstra warned us not to let the size and complexity of our programs cause us to lose “intellectual control” due to the limited nature of our minds. To my knowledge, he never defined precisely what intellectual control was. Our software today is staggeringly larger than the programs of the 1960s, so does that mean we have it under our intellectual control, or did we find ways to make progress without Dijkstra’s high standards? I see signs that we have some software that is under intellectual control and other software that is not. In this column, I’m going to discuss how we can recognize these two categories, what happens when engineers on a project have different attitudes about intellectual control, some advice on when we probably should insist on it, and some ideas about how we achieve it.</description><identifier>ISSN: 0740-7459</identifier><identifier>EISSN: 1937-4194</identifier><identifier>DOI: 10.1109/MS.2018.2874294</identifier><identifier>CODEN: IESOEG</identifier><language>eng</language><publisher>Los Alamitos: IEEE</publisher><subject>Intelligent control ; Project management ; Software engineering</subject><ispartof>IEEE software, 2019-01, Vol.36 (1), p.91-94</ispartof><rights>Copyright IEEE Computer Society 2019</rights><lds50>peer_reviewed</lds50><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c330t-8f85f7a61aa8e6d7024819eb1c7fd9cd8b7244d09cff112046b7e5f21dcf365b3</citedby><cites>FETCH-LOGICAL-c330t-8f85f7a61aa8e6d7024819eb1c7fd9cd8b7244d09cff112046b7e5f21dcf365b3</cites><orcidid>0000-0003-2595-2801</orcidid></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/8611447$$EHTML$$P50$$Gieee$$H</linktohtml><link.rule.ids>314,780,784,796,27915,27916,54749</link.rule.ids><linktorsrc>$$Uhttps://ieeexplore.ieee.org/document/8611447$$EView_record_in_IEEE$$FView_record_in_$$GIEEE</linktorsrc></links><search><creatorcontrib>Fairbanks, George</creatorcontrib><title>Intellectual Control [Pragmatic Designer]</title><title>IEEE software</title><addtitle>S-M</addtitle><description>In the early days of software engineering, Edsger Dijkstra warned us not to let the size and complexity of our programs cause us to lose “intellectual control” due to the limited nature of our minds. To my knowledge, he never defined precisely what intellectual control was. Our software today is staggeringly larger than the programs of the 1960s, so does that mean we have it under our intellectual control, or did we find ways to make progress without Dijkstra’s high standards? I see signs that we have some software that is under intellectual control and other software that is not. In this column, I’m going to discuss how we can recognize these two categories, what happens when engineers on a project have different attitudes about intellectual control, some advice on when we probably should insist on it, and some ideas about how we achieve it.</description><subject>Intelligent control</subject><subject>Project management</subject><subject>Software engineering</subject><issn>0740-7459</issn><issn>1937-4194</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2019</creationdate><recordtype>article</recordtype><sourceid>RIE</sourceid><recordid>eNo9kE1LAzEURYMoWKtrF24KrlxM-16SycdSxqqFFoXqSiRkMkmZMp2pyXThv7elxdXdnHsvHEJuEcaIoCeL5ZgCqjFVklPNz8gANZMZR83PyQAkh0zyXF-Sq5TWAJAjgwF5mLW9bxrv-p1tRkXX9rFrRl_v0a42tq_d6MmnetX6-H1NLoJtkr855ZB8Pk8_itds_vYyKx7nmWMM-kwFlQdpBVqrvKgkUK5Q-xKdDJV2lSol5bwC7UJApMBFKX0eKFYuMJGXbEjuj7vb2P3sfOrNutvFdn9pKArNBTCh9tTkSLnYpRR9MNtYb2z8NQjm4MMslubgw5x87Bt3x0btvf-nlUDkXLI_GElaZQ</recordid><startdate>201901</startdate><enddate>201901</enddate><creator>Fairbanks, George</creator><general>IEEE</general><general>IEEE Computer Society</general><scope>97E</scope><scope>RIA</scope><scope>RIE</scope><scope>AAYXX</scope><scope>CITATION</scope><scope>JQ2</scope><orcidid>https://orcid.org/0000-0003-2595-2801</orcidid></search><sort><creationdate>201901</creationdate><title>Intellectual Control [Pragmatic Designer]</title><author>Fairbanks, George</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c330t-8f85f7a61aa8e6d7024819eb1c7fd9cd8b7244d09cff112046b7e5f21dcf365b3</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2019</creationdate><topic>Intelligent control</topic><topic>Project management</topic><topic>Software engineering</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Fairbanks, George</creatorcontrib><collection>IEEE All-Society Periodicals Package (ASPP) 2005-present</collection><collection>IEEE All-Society Periodicals Package (ASPP) 1998-Present</collection><collection>IEEE Electronic Library (IEL)</collection><collection>CrossRef</collection><collection>ProQuest Computer Science Collection</collection><jtitle>IEEE software</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Fairbanks, George</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Intellectual Control [Pragmatic Designer]</atitle><jtitle>IEEE software</jtitle><stitle>S-M</stitle><date>2019-01</date><risdate>2019</risdate><volume>36</volume><issue>1</issue><spage>91</spage><epage>94</epage><pages>91-94</pages><issn>0740-7459</issn><eissn>1937-4194</eissn><coden>IESOEG</coden><abstract>In the early days of software engineering, Edsger Dijkstra warned us not to let the size and complexity of our programs cause us to lose “intellectual control” due to the limited nature of our minds. To my knowledge, he never defined precisely what intellectual control was. Our software today is staggeringly larger than the programs of the 1960s, so does that mean we have it under our intellectual control, or did we find ways to make progress without Dijkstra’s high standards? I see signs that we have some software that is under intellectual control and other software that is not. In this column, I’m going to discuss how we can recognize these two categories, what happens when engineers on a project have different attitudes about intellectual control, some advice on when we probably should insist on it, and some ideas about how we achieve it.</abstract><cop>Los Alamitos</cop><pub>IEEE</pub><doi>10.1109/MS.2018.2874294</doi><tpages>4</tpages><orcidid>https://orcid.org/0000-0003-2595-2801</orcidid><oa>free_for_read</oa></addata></record> |
| fulltext | fulltext_linktorsrc |
| identifier | ISSN: 0740-7459 |
| ispartof | IEEE software, 2019-01, Vol.36 (1), p.91-94 |
| issn | 0740-7459 1937-4194 |
| language | eng |
| recordid | cdi_ieee_primary_8611447 |
| source | IEEE Electronic Library (IEL) |
| subjects | Intelligent control Project management Software engineering |
| title | Intellectual Control [Pragmatic Designer] |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-15T05%3A10%3A07IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_RIE&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Intellectual%20Control%20%5BPragmatic%20Designer%5D&rft.jtitle=IEEE%20software&rft.au=Fairbanks,%20George&rft.date=2019-01&rft.volume=36&rft.issue=1&rft.spage=91&rft.epage=94&rft.pages=91-94&rft.issn=0740-7459&rft.eissn=1937-4194&rft.coden=IESOEG&rft_id=info:doi/10.1109/MS.2018.2874294&rft_dat=%3Cproquest_RIE%3E2169460368%3C/proquest_RIE%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=2169460368&rft_id=info:pmid/&rft_ieee_id=8611447&rfr_iscdi=true |