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.

1. Code with Honor
on the
importance
and beauty
of software
programming
DOAG 2020, November 2020
Lucas Jellema, CTO & Architect AMIS | Conclusion

2. Lucas Jellema
CTO for AMIS | Conclusion
Cloud Solution Architect
DOAG 2020 | Code with Honor
lucas.jellema@amis.nl | technology.amis.nl | @lucasjellema | lucas-jellema

5. 1202

6. DOAG 2020 | Code with Honor

9. PR
PRofessionalPRide

10. 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

11. PRofessional

12. DOAG 2020 | Code with Honor

13. DOAG 2020 | Code with Honor

14. We are Proud Craftsmen
DOAG 2020 | Code with Honor

15. DOAG 2020 | Code with Honor
The Business

16. DOAG 2020 | Code with Honor
Development
Production
scale,
performance,
security,
stability,
recoverability,
monitoring

17. 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
DOAG 2020 | Code with Honor
golive
no value!

18. Lifetime of a software application
DOAG 2020 | How and why GraalVM is quickly becoming relevant for you

19. Paid Lip Service
• Testing
• QA
• CI/CD
• Automation
• Scalability
• Production-like testing environments
• Security
• Architecture | Design Patterns
DOAG 2020 | Code with Honor

20. DOAG 2020 | 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

21. DOAG 2020 | Code with Honor
why not?
what is your software good enough for?
for a demo, a PoC or a striclty 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?

22. About me
DOAG 2020 | Code with Honor

23. • About you as well?
• A software professional who wants to
be proud
of the professional software
that you craft
take responsibility
towards society
DOAG 2020 | Code with Honor

24. DOAG 2020 | Code with Honorsource: https://www.futuristgerd.com/2016/05/my-presentation-at-innotown-2016-in-alesund-the-next-5-years-in-technology-and-innovation/

25. 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
DOAG 2020 | Code with Honor

26. 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
DOAG 2020 | Code with Honor
*) We expect a professional to offer
suggestions and bring up relevant items
that I am unaware off as a layman

27. 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
DOAG 2020 | Code with Honor
*) We expect a professional to offer
suggestions and bring up relevant items
that I am unaware off as a layman

28. Do most systems live up to these
expectations?
Does your software?
Does mine?
DOAG 2020 | Code with Honor

29. 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
DOAG 2020 | Code with Honor

30. 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
DOAG 2020 | Code with Honor

31. Productivity as function of time and code quality
DOAG 2020 | Code with Honor
source: https://martinfowler.com/articles/is-quality-worth-cost.html
Productivity

32. Productivity as function of % Defects Removed
source: The Economics of Software Quality - https://dev.to/bosepchuk/the-one-chart-every-developer-must-understand-2db9.
DOAG 2020 | Code with Honor

33. DOAG 2020 | Code with Honor

34. Working Software
• What work does it do?
• How can you tell?
Working Software
DOAG 2020 | Code with Honor

35. Small step for mankind…
DOAG 2020 | Code with Honor
FROM WORKING
SOFTWARE
TO PROFESSIONAL
SOFTWARE

36. Professional Software is ABLE Software
• Verifi
• Test
• Oper
• Read
• Evolv
• Maintain
• Observ
• Scal
• Recover
• Prov
• Afford
• Deploy
• Audit
• Impenetra
DOAG 2020 | Code with Honor
ABLE

37. Case in point
DOAG 2020 | Code with Honor
old
not modern
legacy
business critical
custom software

38. Case in point
DOAG 2020 | Code with Honor
end of scale
low on expertise
fragile
no tests, no specs, no docs
expensive TCO
high technical debt
no evolution

39. DOAG 2020 | Code with Honor

40. Working Software
Working Software
DOAG 2020 | Code with Honor

41. Working => Professional Software
Working
Software
Professional
Software
DOAG 2020 | Code with Honor

42. 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
DOAG 2020 | Code with Honor
PRoof
Pull Request
Peer Review
Production Ready
oPeRate
Put to Rest

43. Working
• according to functional specifications and technical interfaces
• proven
DOAG 2020 | Code with Honor
Working Software

44. Behavior Test
• The required
behavior as
experienced from
the outside
• specify
• document
• verify
DOAG 2020 | Code with Honor
Functional Specification
Behavior test
Working Software
Team
DoR

45. DOAG 2020 | Code with Honor
Unit Test
• Verify behavior of
• APIs & Interfaces
• Reusable elements
• Algorithms
• Aspects
• Functionality
• Non Functionality
• Happy & Non-Happy
• not: dependencies

46. Test is many things
DOAG 2020 | 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

47. Test Trophy
DOAG 2020 | Code with Honor
Live

48. QA: Static Code Analysis
• According to coding standards
• Consistent
• Readable
• Maintainable (Code Smells)
• Limited complexity
• Code Coverage (of tests)
• Vulnerabilities (in dependencies)
• Automatic improvements
DOAG 2020 | Code with Honor

49. DOAG 2020 | Code with Honor
Refactoring

50. 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
DOAG 2020 | Code with Honor
Working Software
Professional Code Developer
DoaD
Unit tests & QA
(Behavior Tests)
Refactoring

51. DOAG 2020 | 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) ; }
}

52. DOAG 2020 | Code with Honor
Clean
Code
Guidelines

53. 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
DOAG 2020 | Code with Honor

54. DOAG 2020 | Code with Honor
Metamorphosis – the miracle of the PR

55. PR
Pull Request
Peer Review
Production
Ready
Metamorphosis – the miracle of the PR
DOAG 2020 | Code with Honor

56. Pull Request == Please Review ?!
DOAG 2020 | Code with Honor
Professional Code Developer
Team
DoaD
Appreciate my work
Help me improve it
and become a better developer
Take co-ownership of this code

57. 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!
DOAG 2020 | Code with Honor
Professional Code Developer
Team

58. 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
DOAG 2020 | Code with Honor
Professional Code
Built Software

59. 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
DOAG 2020 | Code with Honor
Professional Code
Built Software
Deployable Software =
DONEDoD

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

61. DOAG 2020 | Code with Honor
Canary

62. Observe the canary
DOAG 2020 | Code with Honor

63. Professional Software – Generating Value for the Business
DOAG 2020 | Code with Honor

64. DOAG 2020 | Code with Honor

65. Life Cycle Management – Technical Maintenance
• Ensure the up-date-ness of
the application and all its dependencies
DOAG 2020 | Code with Honor
Periodic Review

66. 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
DOAG 2020 | Code with Honor
Periodic Review

67. 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

68. Thank you
for your attention
I hope
this was
useful
DOAG 2020 | Code with Honor
lucas.jellema@amis.nl | technology.amis.nl | @lucasjellema | lucas-jellema
Slides: github.com/lucasjellema/presentations