Engineering Software , the third volume in the landmark Write Great Code series by Randall Hyde, helps you create readable and maintainable code that will generate awe from fellow programmers.
The field of software engineering may value team productivity over individual growth, but legendary computer scientist Randall Hyde wants to make promising programmers into masters of their craft. To that end, Engineering Software --the latest volume in Hyde's highly regarded Write Great Code series--offers his signature in-depth coverage of everything from development methodologies and strategic productivity to object-oriented design requirements and system documentation.
You'll learn:
This advanced apprenticeship in the skills, attitudes, and ethics of quality software development reveals the right way to apply engineering principles to programming. Hyde will teach you the rules, and show you when to break them. Along the way, he offers illuminating insights into best practices while empowering you to invent new ones.
Brimming with resources and packed with examples, Engineering Software is your go-to guide for writing code that will set you apart from your peers.
This comprehensive guide to software engineering provides valuable insights and practical advice for software developers of all levels.
This book delves deep into the various stages of software development, from design and implementation to testing and optimization.
It provides a wealth of information and techniques for improving software performance, reliability, and efficiency, making it an indispensable resource for anyone looking to up their software engineering game.
Whether you're a seasoned pro or just starting out, this book will help you write great code and achieve the best possible results.
A truly exceptional read, highly recommended for all software developers.
Em… I really don’t know how to write a review about this one. One thing I can say for sure is that it is full of chapters about documentation, SDLC, UML. But, was it helpful? I don’t know. My opinion - it’s not.
The whole book, mostly, just tells about UML, what are the definitions, classes, etc. So I had a feeling that I’m just going through UML documentation I can find on the internet.
And the it finishes off with a chapter about documentation, how to write requirements.
I agree that these are needed things for very large applications, but I can’t say that this stuff must be taught via the book.
So in result, I just read the book diagonally, because most of it was like I’m reading a spec for UML.