OFFRE LISEUSES
Une liseuse achetée = une housse offerte* jusqu'au 21 juin
Paranoid Programming. How Software Projects Fail (and What Works)
Par :Formats :
Actuellement indisponible
Cet article est actuellement indisponible, il ne peut pas être commandé sur notre site pour le moment. Nous vous invitons à vous inscrire à l'alerte disponibilité, vous recevrez un e-mail dès que cet ouvrage sera à nouveau disponible.
Disponible dans votre compte client Decitre ou Furet du Nord dès validation de votre commande. Le format ePub est :
- Compatible avec une lecture sur My Vivlio (smartphone, tablette, ordinateur)
- Compatible avec une lecture sur liseuses Vivlio
- Pour les liseuses autres que Vivlio, vous devez utiliser le logiciel Adobe Digital Edition. Non compatible avec la lecture sur les liseuses Kindle, Remarkable et Sony
, qui est-ce ?Notre partenaire de plateforme de lecture numérique où vous retrouverez l'ensemble de vos ebooks gratuitement
Pour en savoir plus sur nos ebooks, consultez notre aide en ligne ici
C'est si simple ! Lisez votre ebook avec l'app Vivlio sur votre tablette, mobile ou ordinateur :
- Nombre de pages248
- Date de parution02/01/2079
- FormatePub
- ISBN978-1-7185-0487-5
- EAN9781718504875
- Protection num.pas de protection
- Infos supplémentairesepub
- ÉditeurNo Starch Press
Résumé
A blunt, experience-driven guide to real-world software engineering that explains why software projects fail in predictable ways-and how teams can prevent those failures by consistently applying fundamentals that actually work. Most software engineering books describe an orderly world: clear requirements, rational decisions, and well-defined processes. That is not the world most teams work in. Paranoid Programming focuses on how software projects actually unfold when deadlines compress, priorities shift, and "obvious" steps quietly get skipped.
In this environment, no one may be intentionally out to get you, but a combination of vague requirements, premature coding, weak testing, organizational pressure, and wishful thinking reliably produces the same outcomes: late projects, fragile systems, burned-out teams, and expensive failures. Drawing on decades of real-world experience and advice delivered to Fortune 500 companies, Steve Oualline explains the common failure patterns that plague software projects-and how to defend against them.
The book emphasizes fundamentals that teams routinely endorse in theory but abandon in practice: writing requirements instead of assuming alignment, designing before coding, and treating testing as essential engineering work rather than cleanup. What looks like obvious advice becomes urgent when you see the cost of ignoring it. This book offers practical, unsentimental guidance for recognizing trouble early, putting simple guardrails in place, and building software that fails less often-and recovers faster when it does.
In this environment, no one may be intentionally out to get you, but a combination of vague requirements, premature coding, weak testing, organizational pressure, and wishful thinking reliably produces the same outcomes: late projects, fragile systems, burned-out teams, and expensive failures. Drawing on decades of real-world experience and advice delivered to Fortune 500 companies, Steve Oualline explains the common failure patterns that plague software projects-and how to defend against them.
The book emphasizes fundamentals that teams routinely endorse in theory but abandon in practice: writing requirements instead of assuming alignment, designing before coding, and treating testing as essential engineering work rather than cleanup. What looks like obvious advice becomes urgent when you see the cost of ignoring it. This book offers practical, unsentimental guidance for recognizing trouble early, putting simple guardrails in place, and building software that fails less often-and recovers faster when it does.
