Deployed 6feecb7 with MkDocs version: 1.6.1

Author: jeromehardaway

index.html

@@ -45,11 +45,9 @@
     <ul class="current">
     <li class="toctree-l2"><a class="reference internal" href="#why-have-sops">Why Have SOPs</a>
     </li>
-    <li class="toctree-l2"><a class="reference internal" href="#collection-i-core-fundamentals">Collection I: Core Fundamentals</a>
-        <ul>
-    <li class="toctree-l3"><a class="reference internal" href="#core-training-modules">Core Training Modules</a>
+    <li class="toctree-l2"><a class="reference internal" href="#core-values-our-guiding-principles">Core Values: Our Guiding Principles 🇺🇸</a>
     </li>
-        </ul>
+    <li class="toctree-l2"><a class="reference internal" href="#general-guidance-your-tech-boot-camp-field-manual">General Guidance: Your Tech Boot Camp Field Manual 🇺🇸</a>
     </li>
     </ul>
                 </li>
@@ -77,42 +75,88 @@
           <div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
             <div class="section" itemprop="articleBody">
 
-                <h1 id="vets-who-code-engineering-standard-operating-procedures-sops">Vets Who Code Engineering Standard Operating Procedures (SOPs)</h1>
+                <h1 id="vets-who-code-engineering-standard-operating-procedures-sops">Vets Who Code Engineering Standard Operating Procedures (SOPs) 🇺🇸</h1>
 <p>A veteran transitioning into software engineering through Vets Who Code...</p>
 <ul>
 <li>Has responsibilities to their unit – mentor, coach, and lead.</li>
 <li>Knows their <strong>SOPs</strong>. Follows their SOPs. Improves their SOPs if they are inefficient. If they find better SOPs, they incorporate them. If somebody could use their SOPs, they share them.</li>
 <li>Leads by example. Models the behaviors we desire both interpersonally and technically.</li>
 <li>Strives to understand how their work fits into a broader context and ensures mission success.</li>
 </ul>
-<p>These are our Standard Operating Procedures for Software Engineering Core Fundamentals. All contributions are welcome! Please feel free to submit a pull request to get involved.</p>
+<p>These are our Standard Operating Procedures for Software Engineering as a Vets Who Code Troop. All contributions are welcome! Please feel free to submit a pull request to get involved.</p>
 <h2 id="why-have-sops">Why Have SOPs</h2>
 <ul>
 <li>To increase overall efficiency for the entire Vets Who Code community.</li>
 <li>To reduce the number of errors and avoid common pitfalls in the transition of becoming software engineers.</li>
 <li>To strive to be better engineers and learn from shared experiences so we can flatten each others growth curve.</li>
 <li>To establish a consistent, high-quality approach to software development tasks.</li>
 </ul>
-<p>If you do nothing else, follow the Engineering Fundamentals Checklist! (Link to be added)</p>
-<h2 id="collection-i-core-fundamentals">Collection I: Core Fundamentals</h2>
-<p>This collection of units and modules covers essential topics for software development. It equips you with the necessary skills and knowledge to build a strong foundation in coding, applicable across various programming domains. We're starting with the most fundamental modules, with more to come as we build out our curriculum.</p>
-<h3 id="core-training-modules">Core Training Modules</h3>
+<h2 id="core-values-our-guiding-principles">Core Values: Our Guiding Principles 🇺🇸</h2>
+<p>In the military, we focus on Integrity, Service, and Excellence - in that order. These core values are just as crucial in our mission to become outstanding software engineers:</p>
 <ol>
-<li><a href="command-line-bash/intro.md">Command Center: Mastering Command Line and Bash</a></li>
-<li>Master your primary interface for commanding computer operations</li>
-<li>Learn to navigate file systems, manipulate data, and automate tasks efficiently</li>
-<li>Understand the power of text-based computer interaction</li>
+<li><strong>Integrity First</strong>: In code as in combat, honesty is our bedrock. </li>
+<li>Write clean, readable code that tells the truth about its function.</li>
+<li>Admit to mistakes and learn from them. Debug with determination and transparency.</li>
 <li>
-<p>Harness the full potential of Bash scripting for task automation and system management</p>
+<p>Give credit where it's due in your commits and collaborations.</p>
 </li>
 <li>
-<p><a href="git-github/intro.md">Mission Control: Git and GitHub</a></p>
+<p><strong>Service Before Self</strong>: Your code serves your team, your users, and the larger mission.</p>
 </li>
-<li>Understand version control concepts and their importance in modern software development</li>
-<li>Learn to track changes, collaborate with others, and manage your codebase effectively</li>
-<li>Master the art of branching, merging, and resolving conflicts</li>
-<li>Utilize GitHub for project management, collaboration, and showcasing your work</li>
+<li>Prioritize maintainable, scalable solutions over quick personal wins.</li>
+<li>Contribute to open-source projects and support your fellow coders.</li>
+<li>
+<p>Always consider the end-user experience in your development decisions.</p>
+</li>
+<li>
+<p><strong>Excellence In All We Do</strong>: Strive for continuous improvement in your coding skills.</p>
+</li>
+<li>Regularly refactor and optimize your code. Good enough is never enough.</li>
+<li>Stay updated with the latest technologies and best practices in our field.</li>
+<li>Share your knowledge. Teaching others reinforces your own excellence.</li>
 </ol>
+<p>Remember, troop: these values are your compass in the ever-changing terrain of technology. Let them guide every line of code you write and every pull request you review.</p>
+<h2 id="general-guidance-your-tech-boot-camp-field-manual">General Guidance: Your Tech Boot Camp Field Manual 🇺🇸</h2>
+<ul>
+<li>
+<p>Maintain high standards in your code, soldier! Use GitHub's code review system like a buddy check before a jump – it ensures your code is mission-ready.</p>
+</li>
+<li>
+<p>Quality over speed, trooper. A well-planned assault beats a hasty advance. Craft your code with precision.</p>
+</li>
+<li>
+<p>Focus on one objective at a time. Use GitHub Projects like a mission board to prioritize your targets.</p>
+</li>
+<li>
+<p>Communication is key in our distributed unit. Use GitHub's wiki as your field manual, discussions for intel sharing, and issues to log mission objectives.</p>
+</li>
+<li>
+<p>K.I.S.S. - Keep It Simple, Soldier! Deploy basic, working solutions first. Use branches like you'd use different formations – test new maneuvers before integrating them into the main force.</p>
+</li>
+<li>
+<p>Stick to the mission parameters. If new intel comes in, create a new GitHub issue instead of changing the current mission objectives.</p>
+</li>
+<li>
+<p>Advance in small, tactical moves. Use GitHub releases to deploy frequent, incremental updates. Remember, inch by inch, anything's a cinch!</p>
+</li>
+<li>
+<p>Keep your squad informed. Update GitHub issues and pull requests like you'd update your team on the field. Clear intel keeps the unit aligned.</p>
+</li>
+<li>
+<p>Report bugs like you'd call in artillery – use GitHub issues with clear coordinates (steps to reproduce) and terrain details (code snippets or screenshots).</p>
+</li>
+<li>
+<p>We're all in this together, soldiers. The entire codebase is our base camp – we all have a duty to maintain and improve it.</p>
+</li>
+<li>
+<p>Use GitHub Actions like your automated supply line – it ensures your code is always ready for deployment.</p>
+</li>
+<li>
+<p>Standardize your approach with GitHub's templates. They're like field-tested battle plans – use them to make everyone's mission easier.</p>
+</li>
+</ul>
+<p>Remember, troops: these tools are your high-tech gear. They turn our distributed unit into a lean, mean, coding machine. Master them, and you'll be debugging like a pro and deploying code like a seasoned cyber warrior in no time.</p>
+<p>Stay frosty, keep coding, and let's show them what Vets Who Code can do! HUA! 🇺🇸</p>
 
             </div>
           </div><footer>
@@ -156,5 +200,5 @@ <h3 id="core-training-modules">Core Training Modules</h3>
 
 <!--
 MkDocs version : 1.6.1
-Build Date UTC : 2024-10-11 23:36:50.898903+00:00
+Build Date UTC : 2024-10-11 23:46:14.277255+00:00
 -->