The document discusses good engineering practices, including focusing on delivering value to customers, building trust with stakeholders, taking the project context into account, writing code for readability, matching technology to problems, and avoiding doing evil. It provides statistics on project success rates for traditional vs modern approaches. It also lists recommendations for practices like solving problems instead of just writing code, iterating incrementally, avoiding too much alignment, ensuring code quality, being responsible, considering trade-offs, and more.

1. Wrzesień 2020
Wrocław Jug
Good engineering –
between business focus
and technical excellence

2. You must be the
change you wish
to see in the
world
Jacek Bilski
Senior consultant
@ innoQ Deutschland GmbH
He has over 15 years of experience work-
ing in Java, mostly with backend systems
but was also working on topics like fron-
tend, automation or testing. Every now
and then he publishes something on Twit-
ter, INNOQ blog or his own one

3. Project success rates – traditional
2011 2012 2013 2014 2015
Successful 39% 37% 41% 36% 36%
Challenged 39% 46% 40% 47% 45%
Failed 22% 17% 19% 17% 19%
https://www.standishgroup.com/sample_research_files/CHAOSReport2015-Final.pdf

4. Project success rates – modern
2011 2012 2013 2014 2015
Successful 29% 27% 31% 28% 29%
Challenged 49% 56% 50% 55% 52%
Failed 22% 17% 19% 17% 19%
https://www.standishgroup.com/sample_research_files/CHAOSReport2015-Final.pdf

7. 1. Focus on delivering value
https://unsplash.com/photos/OApHds2yEGQ

8. Solve problems, don’t write code
https://unsplash.com/photos/3y1zF4hIPCg

9. Iterate and increment
https://www.jpattonassociates.com/dont_know_what_i_want/

10. Avoid alignment trap
https://www.praqma.com/stories/agile-alignment-trap/

11. https://itrevolution.com/book/accelerate/

12. 2. Build trust
https://unsplash.com/photos/xRi4o9QVNBg

13. Code quality – our problem
https://www.monkeyuser.com/2019/code-entropy/

14. Take responsibility
https://unsplash.com/photos/s76S64umXpo

15. We’re making trade-offs
https://www.pexels.com/photo/gray-wooden-pedestal-signage-near-road-1638830/

16. Do regular engine checks
https://unsplash.com/photos/V37iTrYZz2E

17. 3. Take context into account
https://openclipart.org/detail/307712/isometric-arrows-pointing-to-center

18. Time
https://unsplash.com/photos/BXOXnQ26B7o

19. Size
https://unsplash.com/photos/7HuTGlUfQSo

20. Target audience
https://unsplash.com/photos/E0bIdzi8zoQ

21. The team
https://unsplash.com/photos/dWYU3i-mqEo

22. Quality requirements
https://unsplash.com/photos/LPurJnihmQI

23. All stakeholders
https://www.pexels.com/photo/group-of-people-holding-message-boards-1059116/

24. Don’t be afraid of ”good enough”
https://chucks-fun.blogspot.com/2014/03/trust-me-im-engineer.html?m=1

25. 4. Code for readability
https://unsplash.com/photos/aVvZJC0ynBQ

27. Use common language
https://www.pexels.com/photo/soldier-giving-red-fruit-on-2-children-during-daytime-36785/

28. ”Documentation is a love letter
that you write to your future
self”
Damian Conway

29. Befriend your tests
https://pixabay.com/photos/woman-person-desktop-work-aerial-3187087/

30. KISS
https://odditymall.com/giant-swiss-army-knife

31. https://www.infoq.com/presentations/Simple-Made-Easy

32. Learn from old masters
https://pixabay.com/photos/namaste-indian-master-mountain-1935938/

33. Teach others
Photo by Yannis A on Unsplash

34. Don’t reinvent the wheel
https://www.jaxtyres.com.au/blog/?p=14497

35. ”Always code as if the guy who
ends up maintaining your code
will be a violent psychopath who
knows where you live”
John F. Woods

36. 5. Match technology to the problem
https://www.pexels.com/photo/building-metal-house-architecture-101808/

37. Don’t use only known tools
https://unsplash.com/photos/vS7LVkPyXJU

38. https://twitter.com/codepitbull/status/784691906005635072

39. Don’t jump on new technologies
https://pixabay.com/photos/base-jump-jump-base-jumper-leaping-1600668/

41. Don’t solve all problems with software
https://unsplash.com/photos/YpLN4HacUS4

42. 6. Don’t do evil
https://unsplash.com/photos/XO9uCZZaipE

43. Long story short…
1. Focus on delivering value
2. Build trust
3. Take context into account
4. Code for readability
5. Match technology to the problem
6. Don’t do evil

44. Thank you! Questions?
Jacek Bilski
jacek.bilski@innoq.com
 @jacek_bilski
www.innoq.com
innoQ Deutschland GmbH
Krischerstr. 100
40789 Monheim a. Rh.
Germany
+49 2173 3366-0
Ohlauer Str. 43
10999 Berlin
Germany
Ludwigstr. 180E
63067 Offenbach
Germany
Kreuzstr. 16
80331 München
Germany
c/o WeWork
Hermannstrasse 13
20095 Hamburg
Germany
innoQ Schweiz GmbH
Gewerbestr. 11
CH-6330 Cham
Switzerland
+41 41 743 01 11
Albulastr. 55
8048 Zürich
Switzerland