Loved James' talk, it provided clear detail on the right way to code to ensure improved testability, reliability and ease of adding new features / services in future.
The mandrill example was perfect and helped make the whole talk easier to connect with.
That combined with the humour in regards to recent 'mandrillgeddon' and the 'that class' example made it an all round great talk for me.
Biggest takeaway for me was around the honesty in that yes coding this way will take longer to begin with, but the benefits in regards to future time saving (not to mention code readability) make it worth while.
Comments
Comments are closed.
Loved James' talk, it provided clear detail on the right way to code to ensure improved testability, reliability and ease of adding new features / services in future.
The mandrill example was perfect and helped make the whole talk easier to connect with.
That combined with the humour in regards to recent 'mandrillgeddon' and the 'that class' example made it an all round great talk for me.
Biggest takeaway for me was around the honesty in that yes coding this way will take longer to begin with, but the benefits in regards to future time saving (not to mention code readability) make it worth while.