#Order2Chaos

slides.com/scottconnerly - more talks
 

Bringing Order to Chaos

Hi.
I’m Scott.
[Hi Scott]
And I’ve written chaos code.
Lots of it.

 

@scottconnerly

CRAP1(m) = comp(m)^2 * (1 – cov(m)/100)^3 + comp(m)

If CRAP1(m) > 30, we consider the method to be CRAPpy.

Python, Ruby, & JS too, but no logos

Software is limited not by the amount of resources put into building it…

 

but by how complex it can get before it breaks down.

 

-Li Hongyi @GovTechSG

  • Baby step everything
  • Get team buy-in
  • Get a testing foothold
  • Use many test types
  • Chaos has its place
  • Manage tech debt
  • Play the infinite game
  • Identify code smells
  • Identify CRAPpy code
  • Simplify business rules
  • Architect your team
  • Over-communicate

12 Step Plan to Bring Order to Chaos

@duretti
@kirkaracha
@ ModernizingPHP
@JamesClear
@likeOMGitsFEDAY
@cpojer
@mikewcohn
@jleu1656
@davidneedham
@pbpk

 

@martinfowler
@riotgames
@DocOnDev
@rlyerichiggins
@simonsinek
@codinghorror
@RefactoringGuru
@Roedyg
@Pretotyping
@GovTechSG
@faustodelatog

Thanks to:

Made with Slides.com