Software Craftsmanship Tips from Kev McCabe at ColdFusion Summit 2014

Software
Craftsmanship
Kev
McCabe
ColdFusion
Summit
2014
Thursday
16th
October
http://bigmadkev.com/resources

About
Me
Software
Craftsmanship
Mentor
@
General
Electric
• ColdFusion
since
1996
(v2)
• London
CFML
&
Web
Community
Leader
• Scrum
Master
• Kanban
Practitioner
• Agile
Coach
T:
@bigmadkev
W:
BigMadKev.com
3

My
Inspiration

Agile
Software
Development
Individuals and interactions over
processes and tools
!
Working software over
comprehensive documentation
!
Customer collaboration over
contract negotiation
!
Responding to change over
following a plan

We
adopted
Agile
and
now
things
will
be
OK
!
!
…
and
the
Agile
Transformation
Era
began.

&
then
we
spend
10
year
focusing
on...
…
people,
interactions,
team
building,
the
ecosystem
!
Process
and
Interactions
became
more
important
than
technical
practices

The
Agile
Hangover
Many
Agile
projects
are
now,
steadily
and
iteratively,
producing
shit
crap
mediocre
software.

䡧We
want
to
get
things
done...
!
䡧 …
but
we
are
under
pressure

䡧But
what
is
to
be
Agile
anyway?

Agile Software Development
!
We are uncovering better ways of developing software by doing it
and helping others do it. Through this work we have come to
value:
!
Individuals and interactions over processes and
tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
!
That is, while there is value in the items on
the right, we value the items on the left more.

The
invisible
threat
Code
quality
Time per feature

http://bigmadkev.com/resources Manifesto for Software Craftsmanship
raising the bar
As aspiring Software Craftsmen we are raising the bar of professional
software development by practising it and helping others learn the craft.
Through this work we have come to value:
Not only working software,
but also well-crafted software
Not only responding to change,
but also steadily adding value
Not only individuals and interactions,
but also a community of professionals
Not only customer collaboration,
but also productive partnerships

What
is
Software
Craftsmanship?
Software
Craftsmanship
is
all
about
putting
responsibility,
professionalism,
pragmatism
and
pride
back
into
software
development

!
䡧How
do
we
know
we
are
building
the
right
thing?
!
䡧How
do
we
know
we
are
building
the
thing
right?

Adding
value
through
practice
●
Automated
testing
●
Test
first
●
Test-‐Driven
Development
●
Pair-‐programming
●
Continuous
Integration

Mob
Programming

䡧Mastering
the
practices
is
hard
…
!
䡧 …
and
that's
why
we
practice

䡧Perfect
practice
䡧(narrowing
the
gap)

䡧Software
Craftsmanship
is
a
long
journey
to
mastery

Software
Craftsmanship
Attitude
-‐
Owning
your
career
-‐
Not
a
9
to
5
profession
-‐
Practice
-‐
Boy
Scout
rule
-‐
Expecting
promotions

Keep
Learning
䡧Learn
stuff
all
the
time
!
䡧Small
and
often
!
䡧You
don’t
want
to
be
out
of
work
and
having
a
large
learn
curve
!
䡧Learning
is
remembering
what
is
important

Big
Learning
Curve

Small
and
Often

䡧Seniority
is
subjective
and
transient

People
Liquidity
䡧Assign
your
less
experienced
people
first
!
䡧Don’t
be
an
i
!
䡧be
a
T
!
䡧or
even
better
a
M
27

䡧The
attitude
towards
legacy
code

䡧Why
would
we
want
to
be
better
developers?

Software
Craftsmanship
is
not...
…
a
church,
trying
to
convert
all
developers
It's
about
leading
by
example
and
showing
how
we
can
be
better
…
about
beautiful
code
It's
about
continuously
delivering
value
not
writing
crap
code

!
䡧Raising
the
Bar

䡧Stop...
!
▪ …
being
miserable
and
negative
▪ …
spreading
your
frustrations

䡧The
only
way
to
have
people
buying
into
what
you
believe
is
if
they
see
you
happy.

䡧Craftsmanship
is
not
enough
to
guarantee
the
success
of
a
project
but
the
lack
of
it
can
be
the
main
cause
of
its
failure

䡧Agile
and
Craftsmanship
complement
each
other
and
both
are
necessary.
!
䡧Agile
processes
assume
technical
excellence
and
a
professional
attitude.
!
䡧Software
Craftsmanship
takes
technical
excellence
and
professionalism
to
a
whole
new
level.

Clean
Code
䡧Meaningful
Names
䡧Short
Functions
▪ Single
Responsibility
Principal
▪ Minimal
Arguments
䡧Show
intent
▪ No
need
for
comments
䡧Formatting
䡧Unit
Testing

Unit
Testing

Code
Reviews

Code
Layout
Matters
䡧 Easy
to
scan
䡧 Expressive
layout
䡧 Compact
format
䡧 Code
is
written
once
and
Read
∞

http://bigmadkev.com/resources The
Elements
of
Programming
Style
䡧 1st
edition
1974
䡧 2nd
edition
1978
!
䡧 56
lessons
䡧 Most
of
which
are
still
valid
today
!
䡧 Book
costs
$150+

Some
of
the
rules
valid
today
1. Write
clearly
-‐-‐
don't
be
too
clever.
2. Say
what
you
mean,
simply
and
directly.
3. Write
clearly
-‐-‐
don't
sacrifice
clarity
for
efficiency.
4. Replace
repetitive
expressions
by
calls
to
common
functions.
5. Parenthesize
to
avoid
ambiguity.
6. Choose
variable
names
that
won't
be
confused.
7. Write
first
in
easy-‐to-‐understand
pseudo
language;
then
translate
into
whatever
language
you
have
to
use.
8. Modularize.
Use
procedures
and
functions.
9. Don't
patch
bad
code
-‐-‐
rewrite
it.
10. Write
and
test
a
big
program
in
small
pieces.
11. Check
some
answers
by
hand
11. Make
it
right
before
you
make
it
faster.
12. Make
it
fail-‐safe
before
you
make
it
faster.
13. Make
it
clear
before
you
make
it
faster.
14. Don't
sacrifice
clarity
for
small
gains
in
efficiency.
15. Don't
strain
to
re-‐use
code;
reorganize
instead.
16. Make
sure
special
cases
are
truly
special.
17. Keep
it
simple
to
make
it
faster.
18. Don't
just
echo
the
code
with
comments
-‐-‐
make
every
comment
count.
19. Don't
comment
bad
code
-‐-‐
rewrite
it.
20. Use
variable
names
that
mean
something.
21. Format
a
program
to
help
the
reader
understand
it.
22. Don't
over-‐comment.

INTUITIVE
䡧 SOLID
principles
䡧 Coupling
and
cohesion
䡧 Abstractions
in
code;
Details
in
data
䡧 Design
patterns
䡧 Presenter-‐
or
Controller-‐
first
Design
MECHANICAL
䡧 Four
Elements
of
Simple
Design
䡧 Test-‐Driven
Development
䡧 No
integrated
tests
for
basic
correctness
䡧 Check
one
thing
at
a
time
䡧 Start
with
what
you
want
to
check
䡧 Inject
dependencies
through
the
constructor
http://www.jbrains.ca/permalink/the-‐four-‐elements-‐of-‐simple-‐design
J.
B.
Rainsberger

Four
Elements
of
Simple
Design
▪ Passes
its
tests
!
▪ Minimizes
duplication
!
▪ Maximizes
clarity
!
▪ Has
fewer
elements

BDD
&
TDD
with
Lego
䡧My
workshop
session
tomorrow
!
䡧2:45
pm
-‐
3:45
pm
!
䡧Room:
Bristlecone
9
!
䡧No
experience
needed,
open
for
non
devs!
46

Did
I
mention
Lego?
47

Books
䡧Written
By
Sandro
!
䡧Part
of
the
Robert
C.
Martin
Series
(Uncle
Bob)
!
䡧Out
Just
before
Christmas
!
䡧ISBN-‐10:
0134052501

䡧 Clean
Code
!
䡧 Robert
“Uncle
Bob”
Martin
!
䡧 Changes
your
thought
process
!
䡧 +
Videos
!
䡧 Also
Clean
Coders
–
More
about
your
career

䡧 Extreme
Programming
Explained:
Embrace
Change
!
䡧 Kent
Back
!
䡧 Good
Technical
Practices

䡧Working
Effectively
with
Legacy
Code
!
䡧 Michael
Feathers

CFML
Software
Craftsmanship
䡧Google
group
!
䡧http://cfml-‐craftsmanship.com
!
䡧Come
Join
Talk
Craftsmanship
!
䡧2
Online
Video
discussions
a
month
䡧2nd
Thursday:
US
Centric
-‐
3pm
PST
6pm
EST
11pm
UK
䡧4th
Thursday:
Euro
Centric
-‐
9am
PDT
12pm
EST
5pm
UK

Questions

Your
Career
䡧You
own
It!
!
䡧You
got
to
work
for
it
!
䡧You
can
never
stop

Contact
Me
Happy
to
work
with
people
over
Google
hangout
/
Skype
/
Saros
After
5pm
UK
(12pm
EST
/
9am
PST)
FREE
/
Amazon
Wish
list
☺
T:
@bigmadkev
S:
bigmadkev
W:
BigMadKev.com

Survey
Don’t
forget
to
fill
in
your
survey
on
the
mobile
application.
!
Only
if
you
liked
me
session
though
:)

Software Craftsmanship Tips from Kev McCabe at ColdFusion Summit 2014

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (11)

Destaque

Destaque (20)

Semelhante a Software Craftsmanship Tips from Kev McCabe at ColdFusion Summit 2014

Semelhante a Software Craftsmanship Tips from Kev McCabe at ColdFusion Summit 2014 (20)

Mais de ColdFusionConference

Mais de ColdFusionConference (20)

Último

Último (20)

Software Craftsmanship Tips from Kev McCabe at ColdFusion Summit 2014