Clean code and the clean coders

CLEAN CODE
and the clean coders

Breves apuntes realizados por Luis
(programania DevTeam)

¿Qué es?
dos libros

resumen una
escuela de
pensamiento
(software
craftmanship)

¿Qué es?
dos libros

resumen una
escuela de
pensamiento
(software
craftmanship)

obviedades (a
veces humillantes)

¿Quién?

Uncle Bob (Robert C. Martin)

¿Quién?


40 años como PROGRAMADOR

¿Quién?


40 años como PROGRAMADOR

Escuchemos a nuestros
mayores

http://twitter.com/#!/thecleancoders

http://twitter.com/#!/unclebobmartin
http://www.cleancoders.com/

http://www.objectmentor.com/

clean coders
repaso a toda una escuela de programación
(XP, agile, craftmanship)

clean coders
apprenticeship patterns

clean coders

pragmatic programmer

clean coders


clean code

clean coders


clean code

agile software
development: princpiles,
patterns and practices

clean coders


clean code

agile software

TestDriven Development
at IBM

clean coders


clean code

agile software

at IBM

Test driven
development: an initial
investigationon the
industry

clean coders
Realizing quality
improvements through
pragmatic programmer test driven
development
clean code

agile software

at IBM

Test driven
investigationon the
industry

clean coders
Realizing quality
development
clean code
the c programming
agile software language

at IBM

Test driven
investigationon the
industry

clean coders
Realizing quality
development
clean code
the c programming
patterns and practices Succeding with agile
(uncle bob series)
at IBM

Test driven
investigationon the
industry

clean coders
Realizing quality
development
clean code
the c programming
(uncle bob series)
at IBM Software estimation:
demytiﬁed
Test driven
investigationon the
industry

clean coders
Realizing quality
development
clean code
the c programming
(uncle bob series)
demytiﬁed
Test driven
development: an initial Software engineerin
investigationon the economics
industry

clean coders
Realizing quality
development
clean code
the c programming Planning poker or how
agile software language to avoid analysis
development: princpiles, paralysis while realase
patterns and practices planning
Succeding with agile
(uncle bob series)
demytiﬁed
Test driven
industry

clean coders
Realizing quality
development
clean code
the c programming Planning poker or how
agile software language to avoid analysis
development: princpiles, paralysis while realase
patterns and practices planning
Succeding with agile
(uncle bob series)
TestDriven Development Agile Estimating and
at IBM Planning (uncle bob)
Software estimation:
demytiﬁed
Test driven
industry

Repaso superﬁcial a
prácticas

prácticas
TDD

prácticas
TDD

test as
documentation

prácticas
TDD

test as
documentation

dojos, katas, open
source

prácticas
TDD

test as
documentation

dojos, katas, open
source

deﬁnition of done

prácticas
TDD

test as
documentation

dojos, katas, open
source

deﬁnition of done

meetings:
necessary, huge
time of wasting

prácticas
stand-up
TDD meetings,
iteration planing,
test as etc.
documentation

dojos, katas, open
source

deﬁnition of done

meetings:
necessary, huge
time of wasting

prácticas
stand-up
TDD meetings,
iteration planing,
test as etc.
documentation
focus: sleep,
dojos, katas, open cafeine, time
source boxing, tomatoes

deﬁnition of done

meetings:
necessary, huge
time of wasting

prácticas
stand-up
TDD meetings,
iteration planing,
test as etc.
documentation
focus: sleep,

deﬁnition of done poker planning

meetings:
necessary, huge
time of wasting

prácticas
stand-up
TDD meetings,
iteration planing,
test as etc.
documentation
focus: sleep,


meetings: collective code
necessary, huge ownership
time of wasting

prácticas
stand-up
TDD meetings,
iteration planing,
test as etc.
documentation
focus: sleep,


time of wasting
project velocity

prácticas
stand-up
TDD meetings,
iteration planing,
test as etc.
documentation
focus: sleep,
mentoring,
apprenticeship
and
craftsmanship

time of wasting
project velocity

LEARNED

El tiempo de debugging es tiempo de programación. Muchos
programadores no lo ven así.

LEARNED


El desarrollo de software es un marathon, no un sprint.

LEARNED



Being late: a todos nos pasa. El truco está en detectarlo pronto y
ser transparente. Estima, y reestima continuamente, y presenta los
datos a la gente implicada en el proyecto constantemente

LEARNED




Teams are harder to build than projects

LEARNED




Teams are harder to build than projects

IDE: vi es el pasado. los grandes IDE´s son lo más por el refactoring

Responsabilidad y ética
be carefull what you ask for


work ethic


work ethic

¿sólo 40 horas a tu profesión?
Distinguir profesión de trabajo.
(katayunos, the melee, leer un libro...)


work ethic


programar 18 horas seguidas hasta las
4 de la mañana no es responsable.


work ethic



programar es extenuante y requiere
grandes dosis de concentración,
aprende a gestionarla (avoid The
Zone, pomodoro, pair programming).

Eres responsable de tu carrera, de tu
work ethic formación, etc.





¿sólo 40 horas a tu profesión? QA should ﬁnd nothing




(katayunos, the melee, leer un libro...) false delivery: gran ejercicio de
irresponsabilidad.



irresponsabilidad.
4 de la mañana no es responsable. pide ayuda, nunca digas no cuando te
piden ayuda.


irresponsabilidad.
4 de la mañana no es responsable. pide ayuda, nunca digas no cuando te
piden ayuda.
grandes dosis de concentración, practice ethics --> practice on your
aprende a gestionarla (avoid The own time, not at your employers time

Aprender a decir no
hazlo o no lo hagas, pero no “lo intentes”

Aprender a decir no

Falta de ética: cada vez que dices que “lo
intentarás” sabiendo que es imposible, huyes de la
confrontación.

Aprender a decir no

confrontación.

De la confrontación nacen mejores soluciones

Aprender a decir no

confrontación.


arguments/disagreements --> any argument that cant
´b e settled in ﬁve minutes can´t be settled by
arguing

Aprender a decir no

confrontación.


arguments/disagreements --> any argument that cant
´b e settled in ﬁve minutes can´t be settled by
arguing

Las estimaciones son eso: estimaciones

Dí sí
Un buen profesional debe comprometerse.

Dí sí

“es que las estimaciones son estimaciones” -
el gran cáncer del agilismo.

Dí sí


Creando un lenguaje para el compromiso:

Dí sí


I need to lose weight, Some should make that happend

Dí sí



I hope to get this done by tomorrow, I wish i had time fo rthat

Dí sí



I hope to get this done by tomorrow, I wish i had time fo rthat

Let´s meet sometime. Let´s ﬁnish this thing

Trabajo bajo presión
stay clean: professionals do not sucums to
the temptation to create a mess ir order to
move quickly. Quick and dirty is an
oxymoron. Dirty always means slow!

Trabajo bajo presión
stay clean: professionals do not sucums to
the temptation to create a mess ir order to
move quickly. Quick and dirty is an
oxymoron. Dirty always means slow!

no abandonar tus principios en momentos de
presión, sino hacerte más fuerte en ellos.
Guarrear, o dormir menos, te hace menos
productivo, no más.

DETAILS

Communication about details is hard. It´s to easy
for each party to wave their handas and assume
that the other party understand.

DETAILS

Communication about details is hard. It´s to easy
for each party to wave their handas and assume
that the other party understand.

uml/MDA --> mda assumes that the problem is
code. but code is not the problem. it has never
been the problem. the problem is detail.

THERE WILL BE CODE
We will never be rid of code, because code represents the details
of the requirements. At some level those details cannot be ignored
or abstracted.

THERE WILL BE CODE
or abstracted.

The level of abstraction of our languages will continue to
incresase. But it will not elimnate code. All the speciﬁcations written
in these higher level and domain-speciﬁc languege will be code!

THERE WILL BE CODE
or abstracted.

The level of abstraction of our languages will continue to
incresase. But it will not elimnate code. All the specifications written
in these higher level and domain-specific languege will be code!

if you have beenn a programmer for more than two or three years,
you have probable been significantly slowed down by someone
elseñs messy code.

the boy scout rule
leave the campground cleaner than you found it.

You are reading this book for two reasons.
First, you are a programmer. Second, you
want to be a better programmer. Good. We
need better programmers...

You are reading this book for two reasons.
First, you are a programmer. Second, you
want to be a better programmer. Good. We
need better programmers...

is a prequel of Agile Software Development:
Principles, Patterns, and Practices...

EXHAUSTIVO

@arturoherrero:
http://www.slideshare.net/arturoherrero/clean-
code-8036914

MEANINGFULL NAMES

int d; / elapsed time in days
/
int elapsedTimeInDays;

FUNCTIONS
/ mejor función es la que tiene cero argumentos
/la
Functions that take three arguments are signiﬁcantly harder to
understand than dyads. The issues of ordering, pausing, and ignoring
are more than doubled. I suggest you think very carefully before
creating a triad.

FUNCTIONS
/ mejor función es la que tiene cero argumentos
/la
Functions that take three arguments are signiﬁcantly harder to
understand than dyads. The issues of ordering, pausing, and ignoring
are more than doubled. I suggest you think very carefully before
creating a triad.

//mal...
function activarSistema(boolean activar);
//bien!
function activarSistema();
function desactivarSistema();

ERROR HANDLING
Functions should do one thing. Error handing is one thing

ERROR HANDLING
Functions should do one thing. Error handing is one thing

public void delete(Page page) {
try {
deletePageAndAllReferences(page);
} catch (Exception e) {
logError(e);
}
private void deletePageAndAllReferences(Page page) throws Exception {
deletePage(page);
registry.deleteReference(page.name);
conﬁgKeys.deleteKey(page.name.makeKey());
}
private void logError(Exception e) {
logger.log(e.getMessage());
}

COMMENTS
The proper use of comments is to compensate for our
failure to express ourself in code

COMMENTS

Every time you write a comment, you should grimace and
feel the failure of your ability of expression.

COMMENTS


/ Check to see if the employee is eligible for full benefits
/
if ((employee.flags & HOURLY_FLAG) &&
(employee.age > 65))

if (employee.isEligibleForFullBenefits())

COMMENTS


/ Check to see if the employee is eligible for full benefits
/
if ((employee.flags & HOURLY_FLAG) &&
(employee.age > 65))

if (employee.isEligibleForFullBenefits())

//bien!
/ Returns an instance of the Responder being tested.
/
protected abstract Responder responderInstance();

FORMATTING
//mal! máximo un nivel de tabulación!
if (this.is){
String cocotero = “tralari”;
for (i=0;i<10;i++){
pepo = coco[i];
while (pepo > coco){
cacaﬂush();
}
}
}

FORMATTING
//mal! máximo un nivel de tabulación!
if (this.is){
String cocotero = “tralari”;
for (i=0;i<10;i++){
pepo = coco[i];
while (pepo > coco){
cacaﬂush();
}
}
}

//bien! sin braquets, no hay otra...
if (page != null)
pageData = page.getData();

while ((line = br.readLine()) != null)
measureLine(line);

CLASES

“Methods with no more than 5 lines of code,
classes with no more than 3 public methods
(average)”

carlos ble

escribir código limpio te fuerza a
seguir patrones, y prácticas, tras los
cuales hay una serie de principios.

Clean code and the clean coders

Recomendados

Recomendados

Más contenido relacionado

Destacado

Destacado (20)

Similar a Clean code and the clean coders

Similar a Clean code and the clean coders (20)

Último

Último (15)

Clean code and the clean coders

Notas del editor