6: Poor reliability is worse than poor efficiency

I agree with this statement. The fastest system that doesn't do it's job is worse than the slow system that does. Landon Noll gave a keynote at XP2019 and talked about his multiple prime number accomplishments. One of the things he pointed out is that the results had to be…

5: Don't try to retrofit quality

5: Don't try to retrofit quality What? No! DO TRY! I mean... Do or do not, there is no try... But YES - Retrofit quality into the legacy code. OK... now I'll move past the principle into the blurb... "Quality cannot be retrofit into software" ... SIGH... just... fucking.…

Pizza Shop Training - MidRange

Oh YEAH! I'm BACK! ... Sorry for that. Anyway; the second set of requirements! Which... I call mid range. Because... Well... it adds the middle pizza. Mid Range New Pizza Size: Medium for $12 Family changed to Large Description format: "{Pizza Size} Pizza with {Toppings}" Toppings need to be…

4: High-Quality Software /is/ possible

... Before I even read the blurb in the book... NO SHIT. And the example is the Space Shuttle... for $1000/loc. Oooo, include the customer... What a concept. (It's apparently Principle 8). There's requirement verification (another principle) which... Not really. I'm very emergent design-y. I'm not gonna list the other…

3: Productivity and Quality are Inseparable

Hmmmm.... I don't agree with this one. It might have been true in 1981 when the source paper was written (Programming Productivity - A life Cycle Concept)... Now; I can't agree with it. What the book (and I assume paper) says is Productivity and Quality are inversely related. If you…

2: Quality is in the Beholder's Eye

Quality is in the of the beholder Principle #2. While it's true that code quality allows us to go fast, code quality isn't what anyone else sees. The code is only for the developers. High quality code is habitable code; but it does means nothing for the user. I'm sure…

1: Quality is #1

I bought a bunch of books recently. One of them is 201 Principles of Software Development. It's got... well... 201 principles for software development. Across a spectrum of things. Including management side. I haven't sat down and read them. It's not really a book I'll do that with. It's a…

Encapsulate what can vary

One of the big things with Object Oriented Programming is to "Encapsulate what Varies". If it's something that can change between objects, we want to encapsulate that into a new object and use composition. This is part of what I think drives MicroObjects. It's "pre?"-encapsulation…