Quality

Writing code you won’t hate tomorrow

• October 28, 2018

As developers we write code everyday, only to frown at it a week after that. Why do we have such a hard time with code written by others and ourselves, this raging desire to rewrite everything we see? Writing code that survives the test of time and self judgment is a matter of clarity and simplicity. Let’s talk about growing, learning and improving our code with calisthenics, readability and good design.

Writing code that lasts

• October 23, 2016

As developers we write code everyday, only to frown at it a week after that. Why do we have such a hard time with code written by others and ourselves, this raging desire to rewrite everything we see? Writing code that survives the test of time and self judgment is a matter of clarity and simplicity. Let’s talk about growing, learning and improving our code with calisthenics, readability and good design.

“Writing code that lasts” … or writing code you won’t hate tomorrow.

• May 28, 2016

As developers we write code everyday, only to frown at it a week after that. Why do we have such a hard time with code written by others and ourselves, this raging desire to rewrite everything we see? Writing code that survives the test of time and self judgment is a matter of clarity and simplicity. Let’s talk about growing, learning and improving our code with calisthenics, readability and good design.

Code Reviews - Not just a quality tool

• May 17, 2016

• Development

I’m a big fan of Code Reviews, or Peer Reviews, within the work flow of a team. But many times when talking about them people refer to them mostly as a tool to avoid bugs, improve quality or the overlooking of details. While these things do surely come out of having a review process, I do not believe they are the real reason why they are a good thing for teams.

“Writing code that lasts” … or writing code you won’t hate tomorrow.

• October 6, 2015

As developers we write code everyday, only to frown at it a week after that. Why do we have such a hard time with code written by others and ourselves, this raging desire to rewrite everything we see? Writing code that survives the test of time and self judgment is a matter of clarity and simplicity. Let’s talk about growing, learning and improving our code with calisthenics, readability and good design.

Writing code you won't hate tomorrow

• November 12, 2014

As developers we write code everyday, only to frown at it a week after that. Why do we have such a hard time with code written by others and ourselves, this raging desire to rewrite everything we see? Writing code that survives the test of time and self judgment is a matter of clarity and simplicity. Let’s talk about growing, learning and improving our code with calisthenics, readability and good design.

Writing code you won't hate tomorrow

• November 8, 2014

As developers we write code everyday, only to frown at it a week after that. Why do we have such a hard time with code written by others and ourselves, this raging desire to rewrite everything we see? Writing code that survives the test of time and self judgment is a matter of clarity and simplicity. Let’s talk about growing, learning and improving our code with calisthenics, readability and good design.

Writing code you won't hate tomorrow

• August 23, 2014

As developers we write code everyday, only to frown at it a week after that. Why do we have such a hard time with code written by others and ourselves, this raging desire to rewrite everything we see? Writing code that survives the test of time and self judgment is a matter of clarity and simplicity. Let’s talk about growing, learning and improving our code with calisthenics, readability and good design.

Your code sucks, let's fix it

• November 2, 2012

Performance and testing are just one aspect of code, to really be successful your code needs to be readable, maintainable and generally easier to comprehend and work with. This talk draws from my own experience in applying the techniques of object calisthenics and code readability, within an existing team. It will help you identify trouble areas, learn how to refactor them and train you to write better code in future projects avoiding common pitfalls.

Your code sucks, let's fix it

• September 2, 2012

How do you measure the quality of your code? Performance and testing are just one aspect of code, in order to meet deadlines and make maintenance quicker you also need your code to be readable, decoupled and generally easier to comprehend and work with. This talk will go over tips and exercises to help you identify trouble areas, refactor them and train you to write better code in future projects. Come make your code look and function better.