Perfect Code. (Code Complete)

This book by Steve McConnell was a hit at the time, and it helped me a lot to become a software develoment engineer. A year in 2006 I started writing code for money for the first time, and I did it at a company where the previous web development department had completely disbanded. The new head of the department came in and started tidying up and I moved from technical support to interns-developers. With the code base, we were initially on you, the process of deploying was manual, there was no testing, some systems had to be rebooted once an hour, otherwise they fell on their own, but with unpredictable consequences. Against this background, Steve’s book has given me answers to questions about whether software development is always so painful or if there are less painful ways. After this book, I loved using metaphors for complex concepts, understood the importance of quality assurance, learned about software design, and more.)

The book itself looked like a monumental brick on almost a thousand pages of A4 format and it consisted of 7 parts.

I. Laying the Foundation It’s about metaphors, collecting requirements, thinking through options and making key decisions. II. Creating High-Quality Code Design, classes and methods, security programming, and the importance of using pseudocode III. Variables Principles of use of variables, their name and data types (conventional and non-standard) IV. Statements - about code organization, conditional operators, cycles, non-standard control structures (goto and recursion)Table methods and general management issues implementation n V. Code Improvements The quality of the software (A lot has improved since then:)) VI. System Considerations A little bit of statistics about big projects and how size affects development, how to manage it (A lot has changed since then, for example, incremental approaches have become dominant.) VII. Software Craftsmanship - the skill part. It’s interesting that engineering and craftmanship once pitted themselves against each other, but now it’s clear that engineering approaches are common:) You can see that. Dave Farley performing with goto 2022 "Taking Back “Software Engineering” “Craftsmanship is Insufficient” and it’s interesting to see him, as he once sank behind the craftmanship.

P.S. I’m not sure this book is as relevant as it is today. 30 and 20 A few years ago, I couldn’t remember it on my channel.) Steve has a book called “An Even More Effective Agile.” ("More Effective Agile: A Roadmap for Software Leaders")In which the author goes well through the development processes (More specifically, Scrum.) And I thought of her in post.

#Software #SoftwareDevelopment #SoftwareArchitecture #Devops #Engineering