This was the fifth event conducted by Pune Software Craftsmanship (Jim Joseph, Hemant Pande, and Dattatray Kale)

1. PuneSoftware
Craftsmanship
Promoting professionalism and
craftsmanship among software
professionals

2. Software craftsmanship & you: A strong foundation
in your team
USE RESEARCH SPREAD AWARENESS ECONOMIC IMPACT
OF BAD CODE
QUANTIFY &
VISUALIZE
CODING PRACTICE GUEST SPEAKER:
BHARTI FROM
NILKINDA
SUSTAINABLE PACE

3. About us
A non-profit group
Former colleagues drawn
together by the shared
belief in software
craftsmanship
3

4. Impactofbad
software
Therac-25 to Boeing 737 Max
Lost lives, money, reputation,
dreams, and more
4

5. Boeing 737
Max
5Source

6. Boeing 737
Max
6Source

7. Boeing 737
Max
7Source

8. Therac-25
8Source

9. Therac-25
9Source

10. Ariane 5
10Source

11. Ariane 5
11Source

12. The
economic
impact of
bad code
Source

13. Annual economic impact of bad code
Source

14. The fight
against bad
software
Software craftsmanship
Professionalism & Code of
ethics*

15. The
Manifesto

16. Professionalism
What does it mean for software
“professionals”?
How often do we discuss it?
Are we held accountable for it?
16

17. Code of
Ethics
17https://www.computer.org/web/education/code-of-ethics

18. Code of
Ethics
18https://www.computer.org/web/education/code-of-ethics

19. Our world
needs
software
craftsmen
19
Efficient – Build and deliver great solutions
when they are needed within budget
Reliable – great quality all the time!
Integrity – protect the users and
customers, do the right thing!
Knowledgeable – capable of building cutting-
edge solutions that give a competitive edge to
employers and customers

20. Afew
goodpractices
20

21. Leave the
code better
than how
you found it
21

22. Maintain your
surroundings
22

23. Always
maintain
the code!
23
http://wiki.c2.com/?FixBrokenWindows

24. Make it easy to
do the right
thing and hard
to do the
wrong thing!
https://twitter.com/GoLeanSixSigma/status/952328692386025472

25. Good code is subjective!
Ever heard this before?
What do YOU think? 25

26. Cyclomatic
complexity
26
• Developed by Thomas J. McCabe, Sr. in
1976
• A metric used to indicate the complexity
of a program
• A measure of the number of linearly
independent paths through a program
• The simple way to calculate cyclomatic
complexity for a method
• Count of branches (IF, WHILE, DO, ) +
count of CASE statements + 1
• As a thumb rule, favor low over high
complexity
• Easier to understand
• Easier to test
• Easier to maintain

27. Calculate the complexity
27

28. Calculate the complexity
28

29. Calculate the
complexity
29

30. GoodcodeisNOTsubjective!
30

31. A commitment
to ourselves, to
make this a
better world:
31
I will understand customer needs and problems so that I build the
right solutions
I will learn and improve my knowledge continuously so that I can do
my work better
I will spread awareness about the impact of bad software and
promote software craftsmanship in my immediate team &
organization
I will spread awareness, practice, and promote Boy Scout rule in my
project/product
I will spread awareness on broken window theory, prevent broken
windows, and do all I can to systematically eliminate broken windows
in my project/product

32. It’s time to code.
Let’s :-
1. Form groups
2. Get familiar the code sample, along
with a cup of tea.
32
https://github.com/hemantpande/PuneCraftsmanshipCommunity
(Folder name is - “Fifth-meetup”

33. What does it look
like?
33
It’s the famous “Movie Rental Kata”
from Martin Fowler’s book on
“Refactoring”

34. 34
So what is our activity today
Objective: Our objective is to :-
a. Identify the code smells with it’s name
b. Apply the corresponding refactoring
It is the series of such refactoring, which will make the code a
lot simple to reason about.

35. 35
But before we proceed…
Any change in the system can be done in 2 ways :-
a. Cover and modify
b. Edit and pray

36. 36
How many tests?
How many tests, do you think are sufficient, to feel
confident about making any change?

37. 37
Characterization tests
Their sole purpose is :-
1. To give confidence by giving maximum test coverage.
2. Is not to understand the system, and they are therefore not like
unit tests. Understanding will come with refactoring.
3. They are supposed to be temporary in nature (not a hard rule).

38. 38
Let’s start the activity
Remember :-
1. Identify the code smell first.
2. Apply the refactoring to remove the code smell
3. Any new code (methods or classes) you create, should
have unit tests.

39. Ourvision
Build a rock-solid group of
motivated software craftsmen
who will raise the bar
continuously for our
profession!
39

40. Our mission
40
Learn & practice
Professionalism for
software professionals
Software craftsmanship
Technical excellence
Develop change agents
Knowing what is good is
one thing; convincing
others is a totally
game!
Capability to drive
improvements based on
data
• Cost of maintainability
(lack of)
• Measurement of
maintainability
• Agility (responding to
change, automated
Support adoption
Facilitate awareness and
Q&A sessions for
organizations and teams
Define and establish
reusable awareness and
training material
Facilitate large-scale
events, conferences, &
competitions
Inspirational talks, code
retreats, meetup for
student and
(example – what
Technogise does)

41. 41
Future community themes

42. ThankYou
Do the right thing and do it
right!
- PuneSoftwareCraftsmanship