I don't think these points are very relevant. Here are mine (better of course) : - prefer simple solutions - makes sure his code will break gracefully - neve

I don't think these points are very relevant. Here are mine (better of course) : - prefer simple solutions - makes sure his code will break gracefully - never prematurely optimizes - don't reinvent the wheel (i.e. : knows his ecosystem) - sanitizes inputs - looks for edge cases - builds a working solution first, iterate afterwards. - asks for review - refactors as needed - writes sensible tests