Status Updates From Code Complete: A Practical ...

This book continues to hand out bangers of knowledge. While not language specific, the first new chapters go over proper planning and architecture of projects as well as how to talk to business owners and product managers on project specifications. One school of thought that impressed me was not limiting myself to coding in a language but coding for a language.

Venter på ny låneperiode

“Traditionally, programming books wax mathematical when they arrive at the topic of abstract data types. They tend to make statements like “One can think of an abstract data type as a mathematical model with a collection of operations defined on it.” Such books make it seem as if you’d never actually use an abstract data type except as a sleep aid.”

“Voltaire said that a book is finished not when nothing more can be added, but when nothing more can be taken away. In software, this is especially true because extra code has to be developed, reviewed, tested, and considered when the other code is modified.

Future versions of the software must remain backward-compatible with the extra code. The fatal question is: It’s easy, so what will be hurt by putting it in?”

Reading this for my IT213 class

Learned that this book is all about "Software Construction"

Ready to dive in 🙂

Chapter 1
Welcome to Software Construction

Good!

Read the first 2 parts.

Very extensive

restarting one more time lol

5/5

5/5

5 stars so far.

"Design bugs are often subtle and occur by evolution with early assumptions being forgotten as new features or uses are added to a system." --- Fernando J. Corbato

A bit dry but contains alot of useful info. Maybe 3.5-4 stars right now

To this point it god quite boring and repetetive.

Really good so far, but I skipped the section on requirements documentation because it was a bit dull. The “Creating High Quality Code” section has been enlightening.

If you choose this approach, be sure the architect really is respected. Sometimes a project architect is just a senior person who has been around too long and is out of touch with production coding issues. Programmers will resent that kind of "architect" defining standards that are out of touch with the work they're doing.

Finished chapter 6 on Classes - wow, lots of great lessons learned!

"The single biggest way to improve both the quality of your code and your productivity is to reuse good code...Many algorithms have already been invented, tested, discussed in the trade literature, reviewed, and improved... take a few minutes to look through the code that's already been written and make sure you're not doing more work than necessary."

“In the Mars Pathfinder, for example, engineers left some of the debug code in by design. An error occurred after the Pathfinder had landed. By using the debug aids that had been left in, engineers at JPL were able to diagnose the problem and upload revised code to the Pathfinder, and the Pathfinder completed its mission perfectly (March 1999).”

“In defensive programming, the main idea is that if a routine is passed bad data, it won't be hurt, even if the bad data is another routine's fault. More generally, it's the recognition that programs will have problems and modifications, and that a smart programmer will develop code accordingly.” very nice and dense resource.

Good stuff. A bit dense but doable.

Yaay! finally finished this massive book!

Working on my skillz

Variable spam and lifetime, it's very interesting, I hadn't heard about it before

Talks about exception and the complexity that it can produce, when using it and to only generate exceptions on the domain, not low level exceptions