4

A service should read like a story. Even a semi code literate product manager should be able to identify how the code runs alongside their user stories expectations. Abstractions should be elegant enough to still maintain the key points from a single point of narration and too many comments indicate a lack of narration in the code/structure. Code shouldn't require equal parts documentation. Code should document itself. So many developers get it functioning and call it a day. Half of being a developer is making it work. The other half is art. I always thought this was common knowledge and then last week I had to argue with our principle dev over the opinion that code should not be easily distinguished. I call that shitty craftsmanship for a sense of job security.

Comments
Add Comment