Post ATKy2zmnB1EdMsveFc by douginamug@mastodon.xyz
 (DIR) More posts by douginamug@mastodon.xyz
 (DIR) Post #ATKy2zmnB1EdMsveFc by douginamug@mastodon.xyz
       2023-03-06T09:26:10Z
       
       0 likes, 0 repeats
       
       Say you wanted to get some software written for you, but you wanted to be sure that it was made in a way that another team could develop from later on: clean, documented, commented, etc.Is there a best practice for this?
       
 (DIR) Post #ATKy39AWIAYwT56Dz6 by amerika@noagendasocial.com
       2023-03-06T11:20:42Z
       
       0 likes, 0 repeats
       
       @douginamug Reams have been written about this.1. Code consistently (have a spec)2. Do not use fancy syntax; abstract anything weird into functions shared by the codebase3. Have a documentation spec for comments4. Partner programming to review the above