Senior Engineers Reduce Risk

Re:Senior Engineers Reduce Risk by liquidise on Monday July 18, 2016 @02:10PM (#12116967)

Agreed, but small critique: i hesitate telling more junior devs things that sound like "less code is better". It is a message that can easily be misunderstood as "if i write this in a more clever way the code gets shorter" instead of the intended lesson.

[ Parent | on HN ]

Re:Senior Engineers Reduce Risk by ferentchak on Monday July 18, 2016 @02:17PM (#12117018)

I always tell my team a good metric is "the least amount of brainpower it takes someone else to use to understand your code."

[ Parent | on HN ]

Re:Senior Engineers Reduce Risk by makr17 on Monday July 18, 2016 @04:25PM (#12117851)

I've found that for me, "code so that I can comprehend it six months from now at 2:00am after several drinks" is a good motivator for "least brainpower".

[ Parent | on HN ]

Re:Senior Engineers Reduce Risk by metaphorm on Monday July 18, 2016 @02:22PM (#12117049)

I usually tell them this: "the only code you can be 100% certain has no bugs is no code".

[ Parent | on HN ]

Re:Senior Engineers Reduce Risk by patrickmay on Monday July 18, 2016 @02:26PM (#12117083)

"The fastest transaction is the one you don't execute."

[ Parent | on HN ]