Video: Implementing Programmer Anarchy - Fred George
Implementing Programmer Anarchy - Fred George (https://www.youtube.com/watch?v=tIxHmsWCd7g)
story tyranny
requirements hierarchy
story level
“Interact with customer on story level”
- Kent beck
- scrum ppl
micromanage: task level
standups: who is doing which task
feature level: much more efficient
what do you want to accomplish?
ok, get out of our way
I know how to get this thing done
I will come ask questions when I need more information
Agile roles
- iteration manager: invented by thoughtworks to place their own project manager without stepping on the toes of the existing person filling that role
Anarchy roles
Fate of roles: QA
old days:
- click stuff
- “manual regression testing”
- people who aren’t good enough to be programmers
now:
- tools -> write code
- understand architecture
==> “what’t the difference between you and a programmer” “but they need to think differently”
- meh, not strong enough
acceptance testing: “one time shot” continuous deployment:
- monitoring
- constantly tested in production (chaos engineering)
Fate of roles: Business Analyst
Fate of roles: Manager
clerk: keep track of stories
leader: natural leader of the group?
ambassador: talk to other people, negotiate, not responsible for making decisions on behalf of the team
coach/mentor: usually not manager
concierge: get’s things you need
power-hungry boss
Anarchy roles vs agile roles
forward’s website
success examples
business school: “try one new tech, maybe 2 if you’re feeling bold”
they did entire new stack, worked great!
clojure could handle the entire load on 1 VM
GoogleAds penalises latency in adds
Agile Best Practices - not used
we care about results blame game:
- who you work with
- iteration plan
- did you deliver code
microservices killed:
- unit test
- acceptance test
- refactoring
- patterns
=> processes used to maintain balls of mud
mistakes
mistakes
Yes mistakes will happen sometimes but not having all the overhead of other people, you’re still ahead financially
mail online
article lead time: 20 minutes
article max 6h front page
poly-skilled workers
experts float around
desks -> tables
mail-online: mastery
mail-online: people focus
key skills we care about
important for mail online
10-12
db: sql, nosql ruby -> clojure cloud
mail-online: career
systems dev: poly
same pay as senior
extremely valuable to the organisation
they didn’t have any masters
maybe now they do
mail-online: training
optional:
- new codebase requires training
mail-online: flexible project approach
mail-online: scorecard
Outpace - startup in california
startup in california
recruitment is easy