[Themaintainers] How to Build for the Handoff

[Andrew Russell]

Thanks Camille - yes, relevant and fascinating. 

Apart from the merits of this approach as a good business practice, and sound/sane technical practice, the word that came to mind as I was reading was *courteous*.  How cool would it be if "courtesy" became a coding/business buzzword? (One can dream, right?)

Andy

> On Jul 27, 2017, at 11:47 AM, Camille E. Acey <connect at camilleacey.com> wrote:
> 
> "Write and review code for maintainability, readability and extensibility (versus terseness or cleverness). Code that engineers can’t understand is code that engineers can’t build on, and it’s code engineers will want to throw out and rewrite. When we’re writing code to hand off, we stay wary of anything that is so clever it is opaque, where function and variable names aren’t readable, expressive, and clear, where the code structure makes it difficult to find what you need. Documentation should accompany most changes, and standard code style should be enforced throughout. "
> 
> https://trackchanges.postlight.com/how-to-build-for-the-handoff-a2af3421be11
> 
> I thought this was a relevant read! 
> 
> -- 
> Camille E. Acey
> http://camilleacey.com
>  
> "Caring for myself is not self-indulgence, it is self-preservation, and that is an act of political warfare." - Audre Lorde
> _______________________________________________
> Themaintainers mailing list
> Themaintainers at lists.stevens.edu
> https://lists.stevens.edu/mailman/listinfo/themaintainers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.stevens.edu/mailman/private/themaintainers/attachments/20170727/b751acd2/attachment.html>