000 | 03809nam a2200529 i 4500 | ||
---|---|---|---|
001 | 8544147 | ||
003 | IEEE | ||
005 | 20220712204921.0 | ||
006 | m o d | ||
007 | cr |n||||||||| | ||
008 | 181218s2018 mau ob 001 eng d | ||
020 |
_a9780262348201 _qelectronic bk. |
||
020 |
_z0262348209 _qelectronic bk. |
||
020 | _z9780262038515 | ||
035 | _a(CaBNVSL)mat08544147 | ||
035 | _a(IDAMS)0b000064888833cb | ||
040 |
_aCaBNVSL _beng _erda _cCaBNVSL _dCaBNVSL |
||
050 | 4 |
_aQA76.76.D47 _bB373 2018eb |
|
082 | 0 | 4 |
_a005.3 _223 |
100 | 1 |
_aBarr, Adam, _eauthor. _925359 |
|
245 | 1 | 4 |
_aThe problem with software : _bwhy smart engineers write bad code / _cby Adam Barr. |
264 | 1 |
_aCambridge : _bThe MIT Press, _c2018 |
|
264 | 2 |
_a[Piscataqay, New Jersey] : _bIEEE Xplore, _c[2018] |
|
300 | _a1 PDF (320 pages). | ||
336 |
_atext _2rdacontent |
||
337 |
_aelectronic _2isbdmedia |
||
338 |
_aonline resource _2rdacarrier |
||
490 | 1 | _aThe MIT Press | |
504 | _aIncludes bibliographical references and index. | ||
506 | _aRestricted to subscribers or individual electronic text purchasers. | ||
520 | _aAn industry insider explains why there is so much bad software - and why academia doesn't teach programmers what industry wants them to know. Why is software so prone to bugs? So vulnerable to viruses? Why are software products so often delayed, or even canceled? Is software development really hard, or are software developers just not that good at it? In The Problem with Software , Adam Barr examines the proliferation of bad software, explains what causes it, and offers some suggestions on how to improve the situation. For one thing, Barr points out, academia doesn't teach programmers what they actually need to know to do their jobs: how to work in a team to create code that works reliably and can be maintained by somebody other than the original authors. As the size and complexity of commercial software have grown, the gap between academic computer science and industry has widened. It's an open secret that there is little engineering in software engineering, which continues to rely not on codified scientific knowledge but on intuition and experience. Barr, who worked as a programmer for more than twenty years, describes how the industry has evolved, from the era of mainframes and Fortran to today's embrace of the cloud. He explains bugs and why software has so many of them, and why today's interconnected computers offer fertile ground for viruses and worms. The difference between good and bad software can be a single line of code, and Barr includes code to illustrate the consequences of seemingly inconsequential choices by programmers. Looking to the future, Barr writes that the best prospect for improving software engineering is the move to the cloud. When software is a service and not a product, companies will have more incentive to make it good rather than "good enough to ship." | ||
530 | _aAlso available in print. | ||
538 | _aMode of access: World Wide Web | ||
588 | 0 | _aPrint version record. | |
650 | 0 |
_aComputer software _xDevelopment _vAnecdotes. _925360 |
|
650 | 0 |
_aComputer programmers _vAnecdotes. _925361 |
|
650 | 7 |
_aComputer programmers. _2fast _923019 |
|
650 | 7 |
_aComputer software _xDevelopment. _2fast _93349 |
|
655 | 4 |
_aElectronic books. _93294 |
|
655 | 7 |
_aAnecdotes. _2fast _925362 |
|
710 | 2 |
_aIEEE Xplore (Online Service), _edistributor. _925363 |
|
710 | 2 |
_aMIT Press, _epublisher. _925364 |
|
776 | 0 | 8 |
_iPrint version: _aBarr, Adam, author. _tProblem with software _z9780262038515 _w(DLC) 2018013460 _w(OCoLC)1035770912 |
830 | 0 |
_aThe MIT Press _925365 |
|
856 | 4 | 2 |
_3Abstract with links to resource _uhttps://ieeexplore.ieee.org/xpl/bkabstractplus.jsp?bkn=8544147 |
942 | _cEBK | ||
999 |
_c73546 _d73546 |