001387654 000__ 03463cam\a2200457Ii\4500
001387654 001__ 1387654
001387654 003__ MaCbMITP
001387654 005__ 20240325105204.0
001387654 006__ m\\\\\o\\d\\\\\\\\
001387654 007__ cr\cn\nnnunnun
001387654 008__ 181112s2018\\\\xxu\\\\\ob\\\\001\0\eng\d
001387654 020__ $$a9780262348201$$q(electronic bk.)
001387654 020__ $$a0262348209$$q(electronic bk.)
001387654 020__ $$z9780262038515
001387654 035__ $$a(OCoLC)1062397891
001387654 035__ $$a(OCoLC-P)1062397891
001387654 040__ $$aOCoLC-P$$beng$$erda$$epn$$cOCoLC-P
001387654 050_4 $$aQA76.76.D47$$bB373 2018eb
001387654 072_7 $$aCOM$$x051230$$2bisacsh
001387654 072_7 $$aTEC$$x000000$$2bisacsh
001387654 08204 $$a005.3$$223
001387654 1001_ $$aBarr, Adam,$$eauthor.
001387654 24514 $$aThe problem with software :$$bwhy smart engineers write bad code /$$cby Adam Barr.
001387654 264_1 $$aCambridge :$$bThe MIT Press,$$c2018
001387654 300__ $$a1 online resource (320 pages).
001387654 336__ $$atext$$btxt$$2rdacontent
001387654 337__ $$acomputer$$bc$$2rdamedia
001387654 338__ $$aonline resource$$bcr$$2rdacarrier
001387654 506__ $$aAccess limited to authorized users.
001387654 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."
001387654 588__ $$aOCLC-licensed vendor bibliographic record.
001387654 650_0 $$aComputer software$$xDevelopment$$vAnecdotes.
001387654 650_0 $$aComputer programmers$$vAnecdotes.
001387654 653__ $$aCOMPUTER SCIENCE/General
001387654 655_0 $$aElectronic books
001387654 852__ $$bebk
001387654 85640 $$3MIT Press$$uhttps://univsouthin.idm.oclc.org/login?url=https://doi.org/10.7551/mitpress/11250.001.0001?locatt=mode:legacy$$zOnline Access through The MIT Press Direct
001387654 85642 $$3OCLC metadata license agreement$$uhttp://www.oclc.org/content/dam/oclc/forms/terms/vbrl-201703.pdf
001387654 909CO $$ooai:library.usi.edu:1387654$$pGLOBAL_SET
001387654 980__ $$aBIB
001387654 980__ $$aEBOOK
001387654 982__ $$aEbook
001387654 983__ $$aOnline