(public).sospep.subjects ~ view article ~ after-12-years-heres-what-ive-learned-about-software-development

<h1 id="title" style="text-align: center;">What I&rsquo;ve learned so far about software development</h1>
<h2>[WHAT]</h2>
<ol>
<li>]&nbsp;by Landon Noss - @medium.com - s/w developer opines on important lessons learned in software development</li>
</ol>
<h2>[WHY]</h2>
<ol>
<li>]&nbsp;Code doesn&rsquo;t change. It mutates.</li>
<li>] You need to have a functional vocabulary.</li>
<li>] Documentation is the encyclopedia of your mutations.</li>
<li>] Automation is essential.</li>
<li>] Gravity is my secret weapon.</li>
<li>] Your peers are your students. Your code is your syllabus.</li>
<li>] Egotism and Defects are interdependent</li>
<li>] conclusions - Never assume your code is finished. Remember; code mutates. Mutation happens with or without direct influence. Document it, and make the mutations simple as you can, but no simpler. Don&rsquo;t be a dick. Try to teach others about your decisions for each mutation. Your peers require your respect, your attention, and your effort. You are the best person to set the example.</li>
</ol>
<h2>[WHERE]</h2>
<ol>
<li>] <a href="https://medium.com/@landongn/12-years-later-what-i-ve-learned-about-being-a-software-engineer-d6e334d6e8a3" target="_blank">https://medium.com/@landongn/12-years-later-what-i-ve-learned-about-being-a-software-engineer-d6e334d6e8a3</a></li>
</ol>
<h2>[WHEN]</h2>
<ol>
<li>] 2015-03-13</li>
</ol>
<h2>[EXAMPLE -&nbsp;auto summary by smmry.com]</h2>
<ol>
<li>] When you feel like you have to retrace your steps when working with a file, that's a sign that your code is getting too complex, and you should think about refactoring, time permitting.</li>
<li>] People have argued with me, at length, that their code is readable.</li>
<li>] Readable code therefore is elegant enough for any common developer to read and understand how it is used, and in which context it is used.</li>
<li>] Review code as though you've never seen the system it exists in.</li>
<li>] &lt;/remarks&gt;/** You may think you know what the following code does.</li>
<li>] Take every opportunity you can to educate your peers about what your code does.</li>
<li>] There's no budget, there's no flexibility in the features for launch and you certainly wouldn't want to spend a day sitting in a conference room when there's code to be written.</li>
</ol>
<h2>[HOW-TO]</h2>
<ol>
<li>]</li>
</ol>
<h2>[REFERENCE]</h2>
<ol>
<li>]</li>
</ol>
<h1 style="text-align: center;">&nbsp;</h1>

~ view article ~ Chapter] index FROM [ Book] analysis-software-developer IN [ libraries] technology-developer-software