We want to be able to look our customer (and our mom) in the eye and state that we are proud of the software we have delivered. Because it is a high quality and lasting product. But can we really? Let’s discuss how to bring our profession to the next level.How to be a Professional Software Professional Abstract As programmers, our main goal is to make IT work. To translate functional specification into executable code. And sure, that is the least we can do. But we have more responsibility than this. We have to produce software that is robust and will reliably handle expected and unexpected cases. Software that is scalable and can handle expected and somewhat unexpected load gracefully. With minimal operating costs and in the greenest way possible. Software that is observable and manageable and that can be evolved with changing and new functional requirements and with changing technology. Software that will be legacy in the original, positive meaning of the word. That does not depend on the one big brain in our team or on the guy that has been around for three decades. Software that we know is good and can comfortably be modified in a controlled and productive way. This session talks about what it takes to create our code with honor. It discusses automation at every level in the build, rollout and monitoring of infrastructure (as code), platform and application, using CI/CD pipelines and DevOps procedures and tool. The session talks about testing – before and during development as well as after each change anywhere in the system and for both functional and non-functional aspects. Test driven development, regression testing and smoke testing are among the concepts discussed. The term ‘clean code’ refers to code that is readable, testable and maintainable. Through code analysis and peer reviews and by performing refactoring we constantly refine our software to be collectively adaptable. As software developers, we have an obligation to society, to our peers and to ourselves to not only write software that does the job, but to create code that is good. Ours is a great and meaningful line of work, especially if we raise our game professionally to code with honor. Benefits: * feel the responsibility we IT professionals have * understand how and why we frequently fail in the responsibility * learn about the key aspects to apply to find the road to redemption

1. rmoug.org
Code with Honor
on the importance and beauty
of software programming
Lucas Jellema – AMIS | Conclusion

2. Lucas Jellema
CTO for AMIS | Conclusion
Cloud Solution Architect
RMOUG Training Days 2021 | Code with Honor
lucas.jellema@amis.nl | technology.amis.nl | @lucasjellema | lucas-jellema
2
8 hours

3. RMOUG Training Days 2021 | Code with Honor 3

4. Quiz time
RMOUG Training Days 2021 | Code with Honor 4

7. 1202

8. RMOUG Training Days 2021 | Code with Honor 8

9. RMOUG Training Days 2021 | Code with Honor 9

11. PR
PRofessionalPRide

12. PR
PRofessionalPRide
Public Relations
Public Responsibility
PRoof Periodic Review
Pull Request
Peer Review
Production Ready
oPeRate
Put to Re
PuRpose
PR oductive
Push-button Release

13. PRofessional

14. RMOUG Training Days 2021 | Code with Honor 14

15. RMOUG Training Days 2021 | Code with Honor 15

16. We are Proud Craftsmen
RMOUG Training Days 2021 | Code with Honor 16

17. RMOUG Training Days 2021 | Code with Honor
The Business
17

18. RMOUG Training Days 2021 | Code with Honor
Development
Production
scale,
performance,
security,
stability,
recoverability,
monitoring
18

19. 0
1
2
3
4
5
6
7
3 months 2 months 1 month 0 months minus 1 month minus 2
months
Value of Software vs Production Date
Cost Value
MVP and incremental value delivery
RMOUG Training Days 2021 | Code with Honor
go
live
no value!
19

20. Lifetime of a software application
RMOUG Training Days 2021 | Code with Honor

21. Paid Lip Service
• Testing
• QA
• CI/CD
• Automation
• Scalability
• Production-like testing environments
• Security
• Architecture | Design Patterns
RMOUG Training Days 2021 | Code with Honor 21

22. RMOUG Training Days 2021 | Code with Honor
The Brake System is
powered by Software
The quality of the brake
software is similar to the
code that you (or your team)
committed last week
Your mother-in-law is
about to get into the car
Your mother-in-law is
about to get into the car
Your kids are about to
get into the car
22

23. RMOUG Training Days 2021 | Code with Honor
why not?
what is your software good enough for?
for a demo, a PoC or a strictly controlled
prototype?
good enough to go to ACC (and let them find the
bugs)?
how do you know?
how do you know for sure what your
software does and how it deals with real
life?
23

24. Quiz time
RMOUG Training Days 2021 | Code with Honor 24

25. What would you prefer:
 We have no failing tests
 We have some failing tests
RMOUG Training Days 2021 | Code with Honor

26. What would you prefer:
 We have no failing tests
 We have some failing tests
RMOUG Training Days 2021 | Code with Honor

27. What would you prefer:
 We have 10% failing tests
 We have 17.61 % failing tests
RMOUG Training Days 2021 | Code with Honor

28. About me
RMOUG Training Days 2021 | Code with Honor 28

29. • About you as well?
• A software professional who wants to
be proud
of the professional software
that you craft
take responsibility
towards society
RMOUG Training Days 2021 | Code with Honor 29

30. source: https://www.futuristgerd.com/2016/05/my-presentation-at-innotown-2016-in-alesund-the-next-5-years-in-technology-and-innovation/

31. My Central Heating Guy
• Functioning system: heating and shower get water with requested
temperature (fast enough and in sufficient volume)
• Within reasonable boundary conditions (-20° to 30° outside
temperature)
• Safe & According to regulations
• Limited noise production, limited gas
• Lasts a while (10-20 years) – robust, limited wear & tear
• Not often failures, after failure system can be started again
quickly
• Can be adapted to (small) changes in circumstances
such as renovation of the house
• Maintenance: not too often and not too expensive
• CV technicians that can work with the system are widely
available, as well as spare parts: the system is not very outlandish
RMOUG Training Days 2021 | Code with Honor 32

32. My Central Heating Guy
• Functioning system: heating and shower get water with
requested temperature (fast enough and in sufficient volume)
• Within reasonable boundary conditions (-20° to 30° outside
temperature)
• Safe & According to regulations
• Limited noise production, limited gas
• Lasts a while (10-20 years) – robust, limited wear & tear
• Not often failures, after failure system can be started again
quickly
• Can be adapted to (small) changes in circumstances
such as renovation of the house
• Maintenance: not too often and not too expensive
• CV technicians that can work with the system are widely
available, as well as spare parts: system is not very outlandish
RMOUG Training Days 2021 | Code with Honor
*) We expect a professional to offer
suggestions and bring up relevant items
that I am unaware off as a layman
33

33. My Software Guy
• Functioning system: proof of working according to
specifications – under all foreseeable conditions
• Satisfies non-functional requirements
(performance, availability, recovery of data & service)
• Safe & According to regulations
• Known and reasonable TCO
• Lasts a while (10-20 years) – robust, limited wear & tear
• with regular technical maintenance at normal costs
• Can be adapted to changes in functional and non-functional
requirements (scale, availability, performance, security, …)
• Maintenance: not too often and not too expensive
• Software can be operated and maintained by regular IT staff
• no rare super specialists need to be flow in
• support and upgrades are easily available
RMOUG Training Days 2021 | Code with Honor
*) We expect a professional to offer
suggestions and bring up relevant items
that I am unaware off as a layman
34

34. Do most systems live up to these
expectations?
Does your software?
Does mine?
RMOUG Training Days 2021 | Code with Honor 35

35. Code with Honor
• Be proud
• Take responsibility
• Hone skills and craftmanship
• Focus on longevity
• Be honest
• Be productive
• Realize value
• Team up
• Step up
• No concessions to my professionalism
RMOUG Training Days 2021 | Code with Honor 36

36. Code with Honor
• Be proud
• Take responsibility
• Hone skills and craftmanship
• Focus on longevity
• Be honest
• Be productive
• Realize value
• Team up
• Step up
• No concessions to my professionalism
RMOUG Training Days 2021 | Code with Honor 37

37. Productivity as function of time and code quality
RMOUG Training Days 2021 | Code with Honor 38

38. Productivity as function of time and code quality
RMOUG Training Days 2021 | Code with Honor
source: https://martinfowler.com/articles/is-quality-worth-cost.html
39

39. RMOUG Training Days 2021 | Code with Honor 41

40. Working Software
• What work does it do?
• How can you tell?
Working Software
RMOUG Training Days 2021 | Code with Honor 42

41. Small step for mankind…
RMOUG Training Days 2021 | Code with Honor
FROM WORKING
SOFTWARE
TO PROFESSIONAL
SOFTWARE
43

42. Professional Software is ABLE Software
• Verifi
• Test
• Oper
• Read
• Evolv
• Maintain
• Observ
• Scal
• Recover
• Prov
• Afford
• Deploy
• Audit
• Impenetra
RMOUG Training Days 2021 | Code with Honor
ABLE
44

43. What is software?
RMOUG Training Days 2021 | Code with Honor 45

44. What is software?
Any instruction executed by a machine!
RMOUG Training Days 2021 | Code with Honor 46

45. Not all code is created equal
• Demo in presentation or workshop
• Explorative / R&D / Doodles
• Assignment in study or training
• Snippet in a blog-article
• Proof of Concept
• Prototype
• MVP
• Alert Condition evaluation
• Product with a very short time to live (several weeks, not any longer)
• Contribution to open source project
• (internal) Reusable Library
• Operating system for guided nuclear missile/ SpaceX vehicle
• Unit-test for code component
• Healthcheck/smoketest
(potentially) Production : Professional Quality Software
Not Production Ready: not (necessarily) Professional Quality Software
RMOUG Training Days 2021 | Code with Honor 48

46. Case in point
RMOUG Training Days 2021 | Code with Honor
old
not modern
legacy
business critical
custom software
50

47. Case in point
RMOUG Training Days 2021 | Code with Honor
end of scale
low on expertise
fragile
no tests, no specs, no docs
expensive TCO
high technical debt
no evolution
51

48. high incident rate
not modern
legacy
business critical
custom software
end of scale
little expertise left
on applications and tech stack
fragile
no tests, no specs, no docs
expensive: high TCO
high technical debt
no evolution
monolith
unattractive technology stack
for young talent
unsupported
inflexible
security-challenged
modern
longevity
business critical
buy before build
scalable
full command
of applications and technology
resilient
automation everywhere
pay per use, business value for money
controlled technical debt,
moving to technical solvency
continuous everything
agile architecture
appealing technology stack
for young talent and experienced staff
supported technology (N or N-1)
agile
as secure as needed
business  IT gap
productivity
robust
old
cloud
well aligned business & IT
RMOUG Training Days 2021 | Code with Honor 52

49. RMOUG Training Days 2021 | Code with Honor 53

50. Working Software
Working Software
RMOUG Training Days 2021 | Code with Honor 54

51. Working => Professional Software
Working
Software
Professional
Software
RMOUG Training Days 2021 | Code with Honor 55

52. https://www.youtube.com/watch?v=5p8wTOr8AbU
RMOUG Training Days 2021 | Code with Honor

53. Working => Professional Software
Working
Software
Professional
Software
RMOUG Training Days 2021 | Code with Honor 57

54. Stages in Software Lifecyle
Functional Specification
Behavior & Unit test
Working Software
Professional Code
Built Software
Deployable Software =
DONE
Professional &
ABLE:
Live Software
(under Ops)
Developer
Team
Production
Preparation
Team
DoR
DoaD
DoD
RMOUG Training Days 2021 | Code with Honor
PRoof
Pull Request
Peer Review
Production Ready
oPeRate
Put to Rest
58

55. Working
• according to functional specifications and technical interfaces
• proven
RMOUG Training Days 2021 | Code with Honor
Working Software
59

56. Behavior Test
• The required
behavior as
experienced from
the outside
• specify
• document
• verify
RMOUG Training Days 2021 | Code with Honor
Functional Specification
Behavior test
Working Software
Team
DoR
60

57. RMOUG Training Days 2021 | Code with Honor
Unit Test
• Verify behavior of
• APIs & Interfaces
• Reusable elements
• Algorithms
• Aspects
• Functionality
• Non Functionality
• Happy & Non-Happy
• not: dependencies
61

58. Test is many things
RMOUG Training Days 2021 | Code with Honor
Functional contract (specification and documentation)
Quick (REPL) feedback cycle for developer
Proof of “working”
Insulator that allows
refactoring and code optimizations
technical upgrades
Regression detector
for things changed
and things unchanged but impacted by changes
Health indicator & Smoke detector
Reference for (re)using code
62

59. • Who creates the test?
• and at what time?
• Who (or what?) executes the test
• at what moment | trigger?
• what is the outcome
• Who checks on the tests?
• specification coverage
• code coverage
• [real world] condition coverage
• timely execution of test and handling of
result
RMOUG Training Days 2021 | Code with Honor 63

60. Definition
• functional specifications
clear, unambiguous and understood
• boundary conditions, non happy
cases and exceptional situations are
covered in specifications
• non-functional requirements are clear
• business value of feature is defined
• TCO budget
RMOUG Training Days 2021 | Code with Honor 64

61. Test Trophy
RMOUG Training Days 2021 | Code with Honor
Live
65

62. Application Architecture
Business Logic
API/
Public
Interface
Frontend
(web, chat,
public REST)
Persistence
(of state) – pluggable
persistence providers
External
Systems
External
Systems
External
Systems
RMOUG Training Days 2021 | Code with Honor 69

63. Application Architecture
Business Logic
API/
Public
Interface
Frontend
(web, chat,
public REST)
Persistence
(of state) – pluggable
persistence providers
External
Systems
mock
mock
mock
External
Systems
External
Systems
RMOUG Training Days 2021 | Code with Honor 70

64. QA: Static Code Analysis
• According to coding standards
• Consistent
• Readable (naming, formatting, length, …)
• Maintainable (Code Smells)
• Limited complexity
• Code Coverage (of tests)
• Vulnerabilities (in dependencies)
• Automatic improvements
RMOUG Training Days 2021 | Code with Honor 71

65. RMOUG Training Days 2021 | Code with Honor
Refactoring
73

66. Refactoring towards Clean Professional Code
• Compliance with
coding standards
• Reducing complexity
• Increasing readability
• Testable & test coverage
• Operable
• logging
• metrics
• configuration settings
• Life cycle management of technology stack &
technical debt
• Needed: Local build pipeline and runtime environment to quickly and frequently do
code analysis, pull & merge from master, build & automated test
RMOUG Training Days 2021 | Code with Honor
Working Software
Professional Code Developer
DoaD
Unit tests & QA
(Behavior Tests)
Refactoring
74

67. RMOUG Training Days 2021 | Code with Honor
private void calculatePayroll (SpecialList<Employee> employeeGroup) {
while (employeeGroup.HasMore()) {
Employee employee = employeeGroup.getNext(true) ;
employee.updateSalary() ;
Payroll.distributeCheck(employee) ;
}
}
private void process (SpecialList
g) { while (g.
HasMore()) { e =
g.getNext(true) ; e.
updSal
() ; /* discard check for temp workers */ Prl.
disChk(e) ; }
}
75

68. RMOUG Training Days 2021 | Code with Honor
Clean
Code
Guidelines
76

69. Team
• That story is in Janet’s area
• Sorry, Tom is on leave so we cannot work on X
right now
• Our tester is working on running all automated
tests
• Ellen is the only one on our team who can work on
the Python components
• Thomas knows how the CI/CD pipelines work
• I am not sure what business feature Sophie is
working on this sprint
• Bob built it, he knows how to demo it
• This [one year] old code is hard to maintain
because the person who built it has left the team
RMOUG Training Days 2021 | Code with Honor 78

70. RMOUG Training Days 2021 | Code with Honor
Metamorphosis – the miracle of the PR
79

71. PR
Pull Request
Peer Review
Production
Ready
Metamorphosis – the miracle of the PR
RMOUG Training Days 2021 | Code with Honor 80

72. Pull Request == Please Review ?!
RMOUG Training Days 2021 | Code with Honor
Professional Code Developer
Team
DoaD
Appreciate my work
and learn from it
Help me improve it
and become a better developer
Take co-ownership of this code
81

73. Peer Review completes the Pull Request
• Peer Review completes (only) when
• Code is ABLE
• and beautiful
• the code is merged from the branch to the trunk
• and the tram may roll in
• because the peer considers the code their own
• Give priority to Peer Review!
• respond ASAP to Pull Request
• a proper Peer Review takes
real commitment and substantial time
(proportional to the complexity of the story)
RMOUG Training Days 2021 | Code with Honor
Professional Code Developer
Team
82

74. Definition of Almost Done
• Code on trunk
• ABLE
• Compiles | Can be Built
• Satisfies
• QA
• Test (behavior & code)
• Non-functional characteristics (absolute & trend)
• Vulnerability
• Guidelines and Standards
• Automated CI/CD pipeline
• (covered by) Smoketest
• Technical Debt management
RMOUG Training Days 2021 | Code with Honor
Professional Code
Built Software
83

75. Deployable == Done (as far as team is concerned)
• Deployable – but not yet deployed
• deploy decision is up to business
• CI/Continuous Delivery =
fully process up to deployability
• Continuous Deployment: automatic roll
out when DONE
RMOUG Training Days 2021 | Code with Honor
Professional Code
Built Software
Deployable Software =
DONE
DoD
84

76. Deploy
• Business decision
• Automated – no touch
• Smoketest post deployment
(and periodically to check on health)
• Operations activated
RMOUG Training Days 2021 | Code with Honor
Built Software
Deployable Software =
DONE
Professional &
ABLE:
Live Software
(under Ops)
Production
Preparation
85

77. RMOUG Training Days 2021 | Code with Honor
Canary
87

78. Observe the canary
RMOUG Training Days 2021 | Code with Honor 88

79. Professional Software – Generating Value for the Business
RMOUG Training Days 2021 | Code with Honor 90

80. RMOUG Training Days 2021 | Code with Honor 91

81. Software Wears Down
RMOUG Training Days 2021 | Code with Honor 92

82. Life Cycle Management – Technical Maintenance
• Ensure the up-date-ness of
the application and all its dependencies
RMOUG Training Days 2021 | Code with Honor
Periodic Review
93

83. Life Cycle Management – Technical Maintenance
• A CEV vulnerability (CVE database https://www.cvedetails.com/)
• Release (or patch) of 3rd party library/framework
• New or deprecated (feature in) PaaS Service
• Custom pricing in used or unused service
• New specification from the business
• New non-functional requirement
• Incident/bug – functional or non-functional
• Technical debt assessment
• New version of platform component:
• e.g. Docker, Kubernetes, Java, Node
• New/custom architecture
choice/guideline
• New/custom coding standard
• New tool, new version of tool
• Law & Regulation, Ethical Insights
• Mere Progression of Time
Triggers for technical change – proactively monitored by the DevOps Team
RMOUG Training Days 2021 | Code with Honor
Periodic Review
94

84. What Time can Do…
RMOUG Training Days 2021 | Code with Honor

85. PR
PRofessional
PRide
Public Relations
Public Responsibility
PRoof Periodic Review
Pull Request
Peer Review
Production Ready
oPeRate
Put to Re
PuRpose
PR oductive
Push-button Release
RMOUG Training Days 2021 | Code with Honor 96

86. Thank you
for your attention
I hope
this was
useful
RMOUG Training Days 2021 | Code with Honor
lucas.jellema@amis.nl | technology.amis.nl | @lucasjellema | lucas-jellema
97