Knowledge

Software craftsmanship

Source 📝

97:"In spite of the rise of Microsoft and other giant producers, software remains in large part a craft industry. Because of the enormous variety of specialized applications, there will always be room for individuals to write software based on their unique knowledge. There will always be niche markets to keep small software companies alive. The craft of writing software will not become obsolete. And the craft of using software creatively is flourishing even more than the craft of writing it." 387: 395: 101:
Following initial discussion, conferences were held in both London and Chicago, after which, a manifesto was drafted and put online to gather signatories. This was followed by the development of practices to further develop the movement including the exchange of talent in "Craftsman Swaps" and the
53:, with its emphasis on "individuals and interactions over processes and tools" questioned some of these assumptions. The Software Craftsmanship Manifesto extends and challenges further the assumptions of the Agile Manifesto, drawing a metaphor between modern software development and the 45:
with connotations of precision, predictability, measurement, risk mitigation, and professionalism. Practice of engineering led to calls for licensing, certification and codified bodies of knowledge as mechanisms for spreading engineering knowledge and maturing the field.
199:, with the intent of establishing a set of principles for software craftsmanship. Three months later, a summary of the general conclusions was decided upon. It was presented publicly, for both viewing and signing, in the form of a Manifesto for Software Craftsmanship. 213:
The 'London Software Craftsmanship Community' (LSCC) was founded in 2010 and is today the largest and most active Software Craftsmanship community in the world, with more than 5000 craftspeople. In 2014,
174:
was published. Its sub-title, "From Journeyman to Master", suggested that programmers go through stages in their professional development akin to the medieval guild traditions of Europe.
117:
As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft. Through this work we have come to value:
77: 364: 168:
In 1992, Jack W. Reeves' essay "What Is Software Design?" suggested that software development is both a craft and an engineering discipline. Seven years later, in 1999,
181:
was published. It suggested that software developers need not see themselves as part of the engineering tradition and that a different metaphor would be more suitable.
222:. It brought the software craftsmanship movement additional visibility, reinforcing the efforts to achieve higher technical excellence and customer satisfaction. 577: 525: 37:
Historically, programmers have been encouraged to see themselves as practitioners of the well-defined statistical analysis and mathematical rigor of a
192:
proposed a fifth value for the Agile Manifesto, namely "Craftsmanship over Crap". He later changed his proposal to "Craftsmanship over Execution".
215: 372: 203: 618: 587: 566: 514: 468: 449: 81:
by Pete McBreen explicitly position software development as heir to the guild traditions of medieval Europe. The philosopher
238: 409: 545: 491: 210:
covered this event on 15 June 2009. In January 2010, a second Craftsman Swap was held between Obtiva and Relevance.
653: 162: 134:
That is, in pursuit of the items on the left we have found the items on the right to be indispensable.
170: 71: 319: 297: 93:, expands software crafts to include mastery of using software as a driver for economic benefit: 196: 149:
This statement may be freely copied in any form, but only in its entirety through this notice.
555: 90: 42: 23: 638: 633: 202:
In April 2009, two of the companies in the software craftsmanship movement, 8th Light and
8: 27: 583: 562: 510: 487: 480: 464: 445: 31: 34:, including the prioritization of financial concerns over developer accountability. 537: 189: 38: 603: 30:. It is a response by software developers to the perceived ills of the mainstream 441: 207: 82: 50: 526:"Craftsmanship versus engineering: Computer programming - An art or a science?" 54: 613: 503: 343: 278: 246: 111: 647: 579:
Software Craftsmanship: L'art du code et de l'agilité technique en entreprise
86: 127:
Not only individuals and interactions, but also a community of professionals
608: 260: 165:
movement which aimed to reform software project management in the 1990s.
58: 541: 69:
The movement traces its roots to the ideas expressed in written works.
628: 438:
Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman
85:
wrote about software as a modern craft in his book The Craftsman.
195:
In December 2008, a number of aspiring software craftsmen met in
130:
Not only customer collaboration, but also productive partnerships
124:
Not only responding to change, but also steadily adding value
557:
The Software Craftsman: Professionalism, Pragmatism, Pride
220:
The Software Craftsman: Professionalism, Pragmatism, Pride
121:
Not only working software, but also well-crafted software
185: 461:
Clean Code: A Handbook of Agile Software Craftsmanship
623: 161:
The origins of software craftsmanship came from the
554: 502: 479: 320:"Craftsmanship – the Fifth Agile Manifesto Value?" 41:with computational theory. This has changed to an 604:Software Craftsman - what it is and what it isn't 645: 365:"Employee swap gives two firms new perspectives" 102:assessment of skills in "Craftsmanship Spikes". 436:Hoover, Dave; Oshineye, Adewale (2009-10-09). 435: 629:Software Craftsmanship Community in Barcelona 639:Applying Software Craftsmanship to Big Teams 410:"Relevance Craftsman Swap Day 1 | 8th Light" 206:, experimented with a "Craftsman Swap." The 218:, one of its co-founders, published a book 482:Software Craftsmanship: The New Imperative 26:that emphasizes the coding skills of the 624:Latvian Software Craftsmanship Community 634:Software Craftsmanship Discussion Group 619:London Software Craftsmanship Community 575: 552: 500: 477: 646: 523: 458: 344:"Manifesto for Software Craftsmanship" 295: 261:"Software Craftsmanship North America" 346:. Manifesto.softwarecraftsmanship.org 609:Software Craftsmanship North America 385: 239:"Software Craftsmanship Conference" 13: 429: 279:"Software Craftsmanship Manifesto" 14: 665: 597: 75:by Andy Hunt and Dave Thomas and 614:Software Craftsmanship Manifesto 402: 379: 357: 336: 312: 289: 271: 253: 231: 112:Software Craftsmanship website 1: 386:Wong, Wailin (15 June 2009). 371:, 13 Jul 2009, archived from 296:Reeves, Jack W (2005-02-23), 225: 177:In 2001, Pete McBreen's book 91:"Science as a Craft Industry" 16:Software development approach 105: 7: 582:(in French). Editions ENI. 530:Bell Labs Technical Journal 64: 10: 670: 459:Martin, Robert C. (2008). 163:agile software development 156: 509:. Yale University Press. 501:Sennett, Richard (2008). 388:"Open to the competition" 184:In his August keynote at 576:Kokaina, Sallah (2019). 553:Mancuso, Sandro (2014). 299:What Is Software Design? 171:The Pragmatic Programmer 140:© 2009, the undersigned. 72:The Pragmatic Programmer 478:McBreen, Pete (2001). 283:Software Craftsmanship 265:Software Craftsmanship 197:Libertyville, Illinois 179:Software Craftsmanship 154: 78:Software Craftsmanship 20:Software craftsmanship 524:Pyritz, Bill (2003). 115: 654:Computer programming 398:on October 26, 2012. 302:, Developer Dot Star 43:engineering approach 24:software development 369:Ventura county star 39:scientific approach 28:software developers 542:10.1002/bltj.10079 486:. Addison Wesley. 463:. Addison Wesley. 22:is an approach to 589:978-2-409-02154-1 568:978-0-13-405250-2 561:. Prentice Hall. 516:978-0-300-11909-1 470:978-0-13-235088-4 451:978-0-596-51838-7 32:software industry 661: 593: 572: 560: 549: 544:. Archived from 520: 508: 497: 485: 474: 455: 424: 423: 421: 420: 406: 400: 399: 394:. Archived from 383: 377: 376: 361: 355: 354: 352: 351: 340: 334: 333: 332: 331: 316: 310: 309: 308: 307: 293: 287: 286: 275: 269: 268: 257: 251: 250: 245:. Archived from 235: 190:Robert C. Martin 669: 668: 664: 663: 662: 660: 659: 658: 644: 643: 600: 590: 569: 517: 494: 471: 452: 442:Ward Cunningham 432: 430:Further reading 427: 418: 416: 408: 407: 403: 392:Chicago Tribune 384: 380: 363: 362: 358: 349: 347: 342: 341: 337: 329: 327: 318: 317: 313: 305: 303: 294: 290: 277: 276: 272: 259: 258: 254: 237: 236: 232: 228: 208:Chicago Tribune 159: 108: 89:, in his essay 83:Richard Sennett 67: 59:medieval Europe 51:Agile Manifesto 17: 12: 11: 5: 667: 657: 656: 642: 641: 636: 631: 626: 621: 616: 611: 606: 599: 598:External links 596: 595: 594: 588: 573: 567: 550: 548:on 2013-01-05. 536:(3): 101–104. 521: 515: 498: 492: 475: 469: 456: 450: 440:. Foreword by 431: 428: 426: 425: 401: 378: 356: 335: 311: 288: 270: 252: 249:on 2009-02-06. 229: 227: 224: 216:Sandro Mancuso 158: 155: 153: 152: 151: 150: 144: 143: 142: 141: 132: 131: 128: 125: 122: 107: 104: 99: 98: 66: 63: 55:apprenticeship 15: 9: 6: 4: 3: 2: 666: 655: 652: 651: 649: 640: 637: 635: 632: 630: 627: 625: 622: 620: 617: 615: 612: 610: 607: 605: 602: 601: 591: 585: 581: 580: 574: 570: 564: 559: 558: 551: 547: 543: 539: 535: 531: 527: 522: 518: 512: 507: 506: 505:The Craftsman 499: 495: 493:0-201-73386-2 489: 484: 483: 476: 472: 466: 462: 457: 453: 447: 443: 439: 434: 433: 415: 411: 405: 397: 393: 389: 382: 375:on 2012-09-17 374: 370: 366: 360: 345: 339: 325: 321: 315: 301: 300: 292: 284: 280: 274: 266: 262: 256: 248: 244: 240: 234: 230: 223: 221: 217: 211: 209: 205: 200: 198: 193: 191: 187: 182: 180: 175: 173: 172: 166: 164: 148: 147: 146: 145: 139: 138: 137: 136: 135: 129: 126: 123: 120: 119: 118: 114: 113: 103: 96: 95: 94: 92: 88: 87:Freeman Dyson 84: 80: 79: 74: 73: 62: 60: 56: 52: 47: 44: 40: 35: 33: 29: 25: 21: 578: 556: 546:the original 533: 529: 504: 481: 460: 444:. O'Reilly. 437: 417:. Retrieved 414:8thlight.com 413: 404: 396:the original 391: 381: 373:the original 368: 359: 348:. Retrieved 338: 328:, retrieved 323: 314: 304:, retrieved 298: 291: 282: 273: 264: 255: 247:the original 242: 233: 219: 212: 201: 194: 183: 178: 176: 169: 167: 160: 133: 116: 109: 100: 76: 70: 68: 48: 36: 19: 18: 419:2018-02-02 350:2019-03-26 330:2015-06-24 326:, Aug 2008 306:2015-06-24 243:Parlez UML 226:References 186:Agile 2008 110:From the 106:Manifesto 57:model of 648:Category 65:Overview 157:History 586:  565:  513:  490:  467:  448:  204:Obtiva 324:Infoq 584:ISBN 563:ISBN 511:ISBN 488:ISBN 465:ISBN 446:ISBN 49:The 538:doi 650:: 532:. 528:. 412:. 390:. 367:, 322:, 281:. 263:. 241:. 188:, 61:. 592:. 571:. 540:: 534:8 519:. 496:. 473:. 454:. 422:. 353:. 285:. 267:.

Index

software development
software developers
software industry
scientific approach
engineering approach
Agile Manifesto
apprenticeship
medieval Europe
The Pragmatic Programmer
Software Craftsmanship
Richard Sennett
Freeman Dyson
"Science as a Craft Industry"
Software Craftsmanship website
agile software development
The Pragmatic Programmer
Agile 2008
Robert C. Martin
Libertyville, Illinois
Obtiva
Chicago Tribune
Sandro Mancuso
"Software Craftsmanship Conference"
the original
"Software Craftsmanship North America"
"Software Craftsmanship Manifesto"
What Is Software Design?
"Craftsmanship – the Fifth Agile Manifesto Value?"
"Manifesto for Software Craftsmanship"
"Employee swap gives two firms new perspectives"

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.