Status Updates From The Clean Coder: A Code of ...

"Verdadeiros profissionais praticam e trabalham firme para manter suas habilidades afiadas e prontas. Não é o bastante simplesmente fazer suas tarefas diárias e chamar isso de prática. Realizar seu trabalho diário é performance, e não prática. Prática é quando você especificamente exercita as habilidades fora do seu ambiente de trabalho com o único propósito de potencializá-las."

Teams and projects. Teams are harder to build than projects.

A good example of providing good estimates of software development with PERT. The difference between committing and estimating. The importance of being disciplined with an without pressure.

The chapter on testing strategies has definitions of unit tests, integration tests, etc.

Loving it!

Must read for professional programmers.

Useful guidelines for professionalism in software production. Although a lot of this wisdom is based on experiences from the author’s decades-old career chapters, much of what Martin teachers be telling is highly applicable to todays professional. Newcomers to the trade will find many tasty nuggets.

The responsibility of the software community to mentor.
and how to put together effective teams.

Collaboration :
- when *not* to pair

Choose disciplines that you feel comfortable following in a crisis, Then follow them all the time. Following these disciplines is the best way to avoid getting into a crisis.

Acceptance Testing
- avoid premature precision
- think of them as spec documentation

TDD, and Katas

Get help, help others, TDD, don't let the business hope.

I am finding this very insightful and with some great advice. Thinking of recommending to my colleagues after i finish it.

Gostei.

É um começo muito bem estruturado, os temas são coesos e condiz com a realidade de um programador nos dias atuais.

Like it. Useful thoughts on how any engineer.

Craftsmanship

Team work

Estimations. ;)

Practice Katas

TDD

"Professionals know their limits. They know how much overtime they can effectively apply, and they know what the cost will be."

If you can't make your commitment, the most important thing is to raise a red flag as soon as possible to whoever you commited to.

"You're taking full responsibility for something, in front of an audience of at least one person. It's not just you standing in front of the mirror, or the computer screen. It's you, facing another human being, and saying you'll do it. That's the start of commitmeny. Putting yourself in the situation that forces you to do something."

But, as we've seen ,sometimes the only way to get to the right yes is to be unafraid to say no.

"slaves are not allowed to ssy no.laborers may be hesitant to say no. Buy professionals are expected to say No.

Cringey chapter, but only because I hate any form of conflict. There was a character clearly in the wrong and the other character was just trying to do the right thing for the job and IDK how they could’ve made it better.

2/3 of my current nonfic reads are for career reasons and that sits strangely with me.

Pressure
Don't change principals when under pressure. You only trust those work principals that you always use.
Collaboration
Learn how to talk to people and keep practicing.
Teams and Projects
Let teams work on projects and don't try to form teams for projects. Team building takes time and once you have a good performing team keep it together. Don't split an individuals time to several projects.

Estimation Methods mentioned:
- Wideband Delphi
- Planning Poker
- Flying Fingers
- Affinity Estimation
- Trivariate Estimate