Software Development Pearls: Lessons from Fifty Years of Software Experience
$0.99
Price: $0.99
(as of Oct 13, 2024 05:37:47 UTC – Details)
Experience is a powerful teacher, but it’s also slow and painful.
You can’t afford to make every mistake yourself! Software Development Pearls helps you improve faster and bypass much of the pain by learning from others who have already climbed the learning curve. Drawing on 25-plus years of helping software teams succeed, Karl Wiegers has crystallized 60 concise, practical lessons for all your projects, regardless of your role, industry, technology, or methodology.
Wiegers’ insights and specific recommendations cover six crucial elements of success: requirements, design, project management, culture and teamwork, quality, and process improvement. For each, Wiegers offers first steps for reflecting on your own experiences before you start; detailed lessons with core insights, real case studies, and actionable solutions; and next steps for planning adoption in your project, team, or organization. This is knowledge you weren’t taught in college or boot camp. It can boost your performance as a developer, business analyst, quality professional, or manager.
Clarify requirements to gain a shared vision and understanding of your real problem; create robust designs that implement the right functionality and quality attributes and can evolve; anticipate and avoid ubiquitous project management pitfalls; grow a culture in which behaviors actually align with what people claim to value; plan realistically for quality and build it in from the outset; use process improvement to achieve desired business results, not as an end in itself; and choose your next steps to get full value from all these lessons.
PLEASE NOTE: When you purchase this title, the accompanying PDF will be available in your Audible Library along with the audio.
8 reviews for Software Development Pearls: Lessons from Fifty Years of Software Experience
Add a review
You must be logged in to post a review.
$0.99
Tanya Charbury –
Useful — Immediately
I’m a software developer with some decades’ experience. I own dozens of books on software … that I’ve never read. This one, by contrast, I have indeed read. I love it. It’s easy to digest, and it helps me to implement these ideas so that the suggestions are immediately useful.By contrast, so many other “get better at making software” books are overly abstruse. They just remind me that there is such a wide gap between where I am and where I need to be, yet how to apply what I learn remains nebulous.Karl’s book is very different from that. It is clear and informative, but best of all: he helps me implement his suggestions so that my professional skills are improved right away, as a result.
Michael Cohn –
An excellent book with something in it for software team members & leaders of all levels
I absolutely love books like this. The book is a collection of short (three- to four-page) tips earned through the authorâs decades of experience developing software.Karl Wiegersâ has collected 60 âpearlsâ of wisdom and has grouped them into categories: requirements, design, project management, quality, culture, teamwork, and process improvement.Youâve likely learned some of the pearls already (âthe hard wayâ). Thatâs how I learned most of them. But this book can help you learn the other pearls much more easily.This book has something in it for software team members and leaders of all levels of experience.
Oregon Guy –
Well Written with Impressive Content
Software Development Pearls: Lessons from 50 years of software experienceBy Karl WiegersPublished by Addison-Wesley, 2022Review by Robert L. Glass, author of Facts and Fallacies of Software Engineering, and a couple of dozen other computing/software booksI like everything Karl Wiegers writes. He writes it well, and he has impressive content. This book is no exception. I suppose that means either this is a glowing review, or it s so biased you neednât read any further!The book is, as the title says, a collection of programming pearls, 60 in all, presented as âlessons.â It is organized in chapters regarding requirements, design, project management, culture and teamwork, quality, process improvement, and the final chapter, What to do next? Each chapter is preceded by a âfirst stepsâ section and concluded with a ânext stepsâ one.I like to judge a book on, among other things, the number of âpithy quotesâ (alias pearls of wisdom) the author chooses in the book. Here are several of then from this one:In the section titled âRequirements are Foundational,â the author quotes a seminar attendee as asking âHow do companies that are really good at requirements handle them?â and then comes up with the wonderfully apt answer âI donât know; they donât call meâ (presumably because they donât need his consulting help).Lesson 12, in the section âElicitation techniques,â is âRequirements elicitation must bring the customerâs voice close to the developerâs ear.â In the section âProgressive Refinement of Detail,â the author notes âI could never discover all the requirements up front, even for a small application. … But thatâs OK…âUnder lesson 9, the author says âIf someone finds problems with my requirements, it doesnât matter how good I think they are.âAt the beginning of the chapter on Design, he says âThe boundary between requirements and design is a fuzzy grey area, not a crisp black line.âIn lesson 21, he says âAn ounce of design is worth a pound of recording.âAnd lesson 24 is âDonât give anyone an estimate off the top of your head.â In the section âWhere did you get that number?â he notes âHope is not a strategy.âAfter lesson 33, he concludes âThe customer is not always right, but the customer always has a point.âAppropriate to contemporary issues, lesson 38 is âPeople talk a lot about their rights, but the flip side of every right is a responsibility.âAnd lesson 49 is âSoftware people love tools, but a fool with a tool is an amplified fool.âAnd finally, this light bulb joke:Q: How many process improvement leaders does it take to change a light bulb?A: Only one, but the light bulb must be willing to change.âI find only one fault with the book. Its subtitle, you will note, says it is about â50 years of software experience.â But its back jacket says, much more modestly, that the author draws on â25+ years helping software teams succeed.â Which is it? Or is there a subtle difference between the two measurements?
Gary K. Evans –
Value: broad and deep
I must first share that I have known and collaborated with Karl Wiegers for many years. I have always admired his writing and the depth of his thinking. However, I admit that after my own 4 decades in software development I wondered if Karl’s book would have much new for me. I was so wrong. In Software Development Pearls Karl has captured an amazing trove of wisdom in every major aspect of software development.As an author and consultant Karl is known best for his expertise in software requirements, and this expertise is obvious in the first chapter of this book. Karl covers the specification of requirements in both Waterfall and Agile approaches. While it is the requirements activities and presentation that will differ between these approaches, he explodes the misleading mantra that “agile” requirements are somehow different from traditional requirements. He succinctly states that “a developer needs the same information to correctly implement the right functionality no matter what development process the project uses.”In the Design chapter Karl advocates for the embrace of abstraction, and stepping back from the details. I agree 100%. On my own projects I have found those that are most successful explore multiple design approaches before laying down code. His sections on user interface design are crisp. There is an old and cynical software joke that “if it was hard to write it ought to be hard to use.” Karl offers the counter-guidance: Make products easy to use correctly and hard to use incorrectly. How obvious! But we don’t always keep this precept – analogous to the error prevention concept of poka yoke – in the front of our thinking.Project management gives me a headache, yet this may be Karl’s most valuable chapter for me. The geography he covers is broad, and his approach to this topic is quintessentially pragmatic. He laments how much we ‘pretend’ in software development, how we game the numbers on our projects, how we ignore risk that is right in our faces, and why we lie about our estimates. And he offers clear guidance on avoiding these self-deceptions.I have only similar praise for his remaining chapters on Culture and Teamwork, Quality, and Process Improvement. But I would be remiss not to note two final and important observations. First, Karl concludes this offering with a Next Steps chapter to give you some very concrete ideas for applying his content to your project. Second, the Index is really good. I rely heavily on a well-structured Index and Karl has provided one that is very thorough and useful for finding that elusive topic when you can’t quite remember in which chapter you read it.
PashaT –
Iâve become a BA after reading K.W.âs Software Requirements. Now Iâm impressed yet again with all the âknow howâ that he is sharing in this book. These are indeed the pearls. Totally recommend to software professionals – PMs, BAs, QAs, and the end clients of course.
Bernard H. –
Holding Karl WIEGERS in high regard for the quality of his books on requirements engineering, I looked with anticipation at reading this one.I was not disapointed at all.The notes from his experience are very useful and resonate with mine.I strongly recommend this book.
Peter North –
Heâs best book to date! Easy to read and great experience content in these pages. Do yourself a favour and get a copy!
Mosunmola J –
Cheap quality. Looks really good but it is cheap quality for sure. Ended up buying from Ikea at a much cheaper price