東華大學圖書館 |

Language: English

Help

回圖書館首頁

手機版館藏查詢

Back

Switch To: Labeled | MARC Mode | ISBD

Working with coders = a guide to sof...

Gleeson, Patrick.

Linked to FindBook

Google Book

Amazon

博客來

Working with coders = a guide to software development for the perplexed non-techie /

Record Type:	Electronic resources : Monograph/item
Title/Author:	Working with coders/ by Patrick Gleeson.
Reminder of title:	a guide to software development for the perplexed non-techie /
Author:	Gleeson, Patrick.
Published:	Berkeley, CA :Apress : : 2017.,
Description:	xiv, 220 p. :ill., digital ;24 cm.
[NT 15003449]:	Chapter 1: Introductions -- Chapter 2: Why Writing Software Is Nothing Like Building A House -- Chapter 3: (Fr)Agile -- Chapter 4: What Do They Do All Day? -- Chapter 5: The Big Green Check Mark -- Chapter 6: Taking the "Arg!" out of Jargon -- Chapter 7: So You Need to Hire an Engineer -- Chapter 8: Programmer Preoccupations -- Chapter 9: Keeping Coders Happy -- Chapter 10: When It All Goes Wrong.
Contained By:	Springer eBooks
Subject:	Computer software - Handbooks, manuals, etc. - Development -
Online resource:	http://dx.doi.org/10.1007/978-1-4842-2701-5
ISBN:	9781484227015

Working with coders = a guide to software development for the perplexed non-techie /
Gleeson, Patrick.

Working with codersa guide to software development for the perplexed non-techie /[electronic resource] :by Patrick Gleeson. - Berkeley, CA :Apress :2017. - xiv, 220 p. :ill., digital ;24 cm.

Chapter 1: Introductions -- Chapter 2: Why Writing Software Is Nothing Like Building A House -- Chapter 3: (Fr)Agile -- Chapter 4: What Do They Do All Day? -- Chapter 5: The Big Green Check Mark -- Chapter 6: Taking the "Arg!" out of Jargon -- Chapter 7: So You Need to Hire an Engineer -- Chapter 8: Programmer Preoccupations -- Chapter 9: Keeping Coders Happy -- Chapter 10: When It All Goes Wrong.

Get introduced to the fascinating world inhabited by the professional software developer. Aimed at a non-technical audience, this book aims to de-obfuscate the jargon, explain the various activities that coders undertake, and analyze the specific pressures, priorities, and preoccupations that developers are prone to. In each case it offers pragmatic advice on how to use this knowledge to make effective business decisions and work productively with software teams. Software projects are, all too often, utter nightmares for everyone involved. Depending on which study you read, between 60 and 90 percent of all software projects are completed late, run over budget, or deliver an inferior quality end product. This blight affects everyone from large organizations trying to roll out business change to tiny startups desperately trying to launch their MVP before the money runs out. While there has been much attention devoted to understanding these failings, leading to the development of entire management methodologies aimed at reducing the failure rate, such new processes have had, at best, limited success in delivering better results. Based on a decade spent exploring the world of software, Patrick Gleeson argues that the underlying reason for the high failure rate of software projects is that software development, being a deeply arcane and idiosyncratic process, tends to be thoroughly and disastrously misunderstood by managers and leaders. So long as the people tasked with making decisions about software projects are unaware of these idiosyncrasies and their ramifications, software projects will be delivered late, software products will be unfit for purpose, and relations between software developers and their non-technical colleagues will be strained. Even the most potent modern management tools are ineffective when wielded blindly. To anyone who employs, contracts, manages, or works with software developers, Working with Coders: A Guide to Software Development for the Perplexed Non-Techie delivers the understanding necessary to reduce friction and inefficiencies at the intersection between software development teams and their non-technical colleagues. What You'll Learn: Discover why software projects are so commonly delivered late and with an abysmal end product Examine why the relationship between coders and their non-technical colleagues is often strained Understand how the software development process works and how to support it effectively Decipher and use the jargon of software development Keep a team of coders happy and improve the odds of successful software project delivery.

ISBN: 9781484227015

Standard No.: 10.1007/978-1-4842-2701-5doiSubjects--Topical Terms:

817673
Computer software
--Development--Handbooks, manuals, etc.

LC Class. No.: QA76.76.D47

Dewey Class. No.: 005.1

Working with coders = a guide to software development for the perplexed non-techie /
LDR:04027nmm a2200325 a 4500 001 2105434
003 DE-He213
005 20170704123632.0
006 m d
007 cr nn 008maaau
008 180417s2017 cau s 0 eng d
020 $a 9781484227015 $q (electronic bk.)
020 $a 9781484227008 $q (paper)
024 7 $a 10.1007/978-1-4842-2701-5 $2 doi
035 $a 978-1-4842-2701-5
040 $a GP $c GP
041 0 $a eng
050 4 $a QA76.76.D47
072 7 $a KJQ $2 bicssc
072 7 $a UF $2 bicssc
072 7 $a COM005000 $2 bisacsh
082 0 4 $a 005.1 $2 23
090 $a QA76.76.D47 $b G555 2017
100 1 $a Gleeson, Patrick. $3 3250268
245 1 0 $a Working with coders $h [electronic resource] : $b a guide to software development for the perplexed non-techie / $c by Patrick Gleeson.
260 $a Berkeley, CA : $b Apress : $b Imprint: Apress, $c 2017.
300 $a xiv, 220 p. : $b ill., digital ; $c 24 cm.
505 0 $a Chapter 1: Introductions -- Chapter 2: Why Writing Software Is Nothing Like Building A House -- Chapter 3: (Fr)Agile -- Chapter 4: What Do They Do All Day? -- Chapter 5: The Big Green Check Mark -- Chapter 6: Taking the "Arg!" out of Jargon -- Chapter 7: So You Need to Hire an Engineer -- Chapter 8: Programmer Preoccupations -- Chapter 9: Keeping Coders Happy -- Chapter 10: When It All Goes Wrong.
520 $a Get introduced to the fascinating world inhabited by the professional software developer. Aimed at a non-technical audience, this book aims to de-obfuscate the jargon, explain the various activities that coders undertake, and analyze the specific pressures, priorities, and preoccupations that developers are prone to. In each case it offers pragmatic advice on how to use this knowledge to make effective business decisions and work productively with software teams. Software projects are, all too often, utter nightmares for everyone involved. Depending on which study you read, between 60 and 90 percent of all software projects are completed late, run over budget, or deliver an inferior quality end product. This blight affects everyone from large organizations trying to roll out business change to tiny startups desperately trying to launch their MVP before the money runs out. While there has been much attention devoted to understanding these failings, leading to the development of entire management methodologies aimed at reducing the failure rate, such new processes have had, at best, limited success in delivering better results. Based on a decade spent exploring the world of software, Patrick Gleeson argues that the underlying reason for the high failure rate of software projects is that software development, being a deeply arcane and idiosyncratic process, tends to be thoroughly and disastrously misunderstood by managers and leaders. So long as the people tasked with making decisions about software projects are unaware of these idiosyncrasies and their ramifications, software projects will be delivered late, software products will be unfit for purpose, and relations between software developers and their non-technical colleagues will be strained. Even the most potent modern management tools are ineffective when wielded blindly. To anyone who employs, contracts, manages, or works with software developers, Working with Coders: A Guide to Software Development for the Perplexed Non-Techie delivers the understanding necessary to reduce friction and inefficiencies at the intersection between software development teams and their non-technical colleagues. What You'll Learn: Discover why software projects are so commonly delivered late and with an abysmal end product Examine why the relationship between coders and their non-technical colleagues is often strained Understand how the software development process works and how to support it effectively Decipher and use the jargon of software development Keep a team of coders happy and improve the odds of successful software project delivery.
650 0 $a Computer software $x Development $v Handbooks, manuals, etc. $3 817673
650 0 $a Software engineering. $3 559826
650 1 4 $a Business and Management. $2 eflch $3 1485455
650 2 4 $a Software Management. $3 2139173
650 2 4 $a Careers in Business and Mangagement. $3 2054514
650 2 4 $a Software Engineering. $3 890874
650 2 4 $a The Computing Profession. $3 895946
650 2 4 $a Project Management. $3 1567596
650 2 4 $a Business Strategy/Leadership. $3 1565354
710 2 $a SpringerLink (Online service) $3 836513
773 0 $t Springer eBooks
856 4 0 $u http://dx.doi.org/10.1007/978-1-4842-2701-5
950 $a Business and Management (Springer-41169)