A brief introduction - why self-organising teams of programmers still need rules.

1. Rules & discussions
Finding the balance
Author: Tamas Rev
Blog: https://tamasrev.wordpress.com/
Twitter: @tamasrev

2. Humans are good at following rules - 1

3. Humans are good at following rules - 2

4. Humans don’t like to follow rules - 1

5. Humans don’t like to follow rules - 2

6. Programmers are especially good at following rules

7. Rules & self-organisation
● Self-organising teams set their own rules
● Discuss only the exceptions
● Make new rules based on exceptions
● Retire old rules when they make no sense anymore

8. How rules hinder us
● It is mentally taxing to keep the rules in mind
● Lack of autonomy can be demotivating
● Rules lead to suboptimal solutions

9. How rules help us
● We know what to expect from a coworkers commit
● Rules are an antidote to micromanagement
○ “This request can go to the next sprint”
○ “Need to do some more analysis, then we’ll see what we can do”
● Rules, like code conventions let us focus on more on business logic
● We’ll have less discussions, but they’ll be more meaningful

10. Some linters
● Java
○ Checkstyle
○ pmd
○ findbugs
● JavaScript
○ JSLint
○ ESLint
● Ruby
○ RuboCop
● C#
○ FxCop
○ ClockSharp
https://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis

11. Sources of images
● Chess - https://www.pexels.com/hu-hu/foto/feny-fekete-jatek-verseny-
6689070/
● Traffic - https://www.pexels.com/hu-hu/foto/varos-madartavlat-ut-forgalom-
186537/
● School - https://www.pexels.com/hu-hu/foto/emberek-no-asztal-iras-4019754/
● Army - https://www.pexels.com/hu-hu/foto/egyenruha-emberek-ferfi-ferfiak-
280002/