#cleancoder software-book

[denizengin]

Re-Reading Clean Coder: Appendix A Tooling

Bug Counts

When issue-tracking tools are forced to track thousands of issues, then the word "tracking" loses meaning. They become "issue dumps"

Continuous Build

The team must simply keep the build working at all times. If the build fails, it should be a "stop presses" event and the team should meet to quickly resolve the issue. Under no circumstances should the failure be allowed to persist for a day or more.

The Details

In the 70s as teletypes behand to fade from use, operating systems like UNIX shortened the end-of-line sequence to simply '\n' . However operating systems like DOS, continued to use the '\r\n\' convention.

[denizengin]

Re-reading Clean Coder: Chapter 14 - Mentoring, Apprenticeship, and Craftsmanship

CRAFTSMANSHIP

A craftsman is someone who works quickly, but without rushing, who provides reasonable estimates and meets commitments. A craftsman knows when to say no, but tries hard to say yes. Craftsmanship is the mindset held by the craftsment. Craftsmenship is a meme that contains valies, disciplines, techniques, attitudes, and answers.

The craftsmanship meme is handed from one person to another. It is exchanged between peers.

CRAFTSMANSIP - CONVINCING PEOPLE

You can't convince people to be craftsmen. You make the meme observable, you act as a role model. Then just let the meme do the rest of the work.

[denizengin]

Re-reading Clean Coder: Chapter 6 - Practicing

It's not always wise to go that fast. Often it is better to slow down and just think

CODE KATAS

...speed depends on practice.We choose a repertoire of problem/solution pairs and execute them over and over again until we know them cold

...a programmer should know several different kata and practice them regularly so that they don't fade away from memory.

The Bowling Game

Prime Factors

Word Wrap

WASA

The two partners choose a kata, or a simple problem. If the partners choose a standard kata, then the outcome is known and the programmers are practicing and critiquing each other's keyboarding and mousing techniques, and how well they've memorized the kata.

RANDORI

With the screen projected on the wall, one person writes a test and then sits down. The next person makes the test pass and then writes the next test.

[denizengin]

Re-reading Clean Coder: Chapter 4 - Coding

Writer's Block

Sometimes the code just doesn't come...there is a very simple solution...Find a pair partner

Creative Input

I read a lot, and I read all kinds of material. I read material on software, politics, biology, astronomy, physics, chemistry, mathematics and much more...The hours I spend away from my usual problems, while being actively stimulated by challenging and creative ideas, results in an almost irresistivle pressire to create something myself.

Define Done

You avoid the problem of false delivery by creating an idenpendent definition of done. The best way to do this is to have your business analyst and testers create automated acceptance tests that must pass before you can say that you are done...The tests should be understandable by the stakeholders and business people, and should be run frequently.

Help & Helping Others

Programming is so hard, in fact, it is beyond the capability of one person to do it well. No matter how skilled you are, you will certainly benefit from another programmer's thoughts and ideas.

Your work is not so important that you cannot lend some of your time to help others...a fresh perspective can be a profound catalyst for solving problems.

[denizengin]

Re-reading Clean Coder: Chapter 1 - Professionalism

I first read The Clean Coder by Robert C. Martin 5 years ago. I've decided to re-read The Clean Coder after 5 years, firstly as I think it is a classic and secondly because I've recommended it as a nice read to my team and I'd like to compare thoughts on each chapter.

Chapter 1 Professionalism

Taking Responsibility: take responsibility and tell that tests aren't completed and you are not prepared to ship software on time

QA Should find nothing

Automated QA Automated tests are a must to be able to change code without being afraid.

'Professional developers are so certain of their code and tests that they are maddeningly casual about making random, opportunistic changes'

Know your field: - Nassi Schneiderman chart - Tramp data - Conascence

'Our field is progressing quickly, yet if and while statements are the same as they were 50 years ago. Much has changed, much hasn't.'

List of things every software professional should be conversant with: - Design Patterns: 24 patterns in GOF book, working knowledge in POSA books. - Design principles: SOLID principles, component principles - Methods: XP, Scrum, Lean, Kanban, Waterfall, Structured Analysis, Structured design - Disciplines: TDD, Object-Oriented design, Structured Programming, Continuous Integration, Pair programming - Artifacts: How to use various diagrams and flow charts

Continuous Learning and Practice

Code katas

Mentoring

Nothing will drive facts and values into your head faster and harder than having to communicate them to people you are responsible for.

Know your domain - Know enough about your domain to recognize and challenge specification errors.

Humility

A professional will not demean another for making a mistake, because he knows he may be the next to fail