Vets Who Code Engineering SOPs and Field Manual ποΈ
"Proper Planning and Preparation Prevents Poor Performance" - Military Leadership Principle
Core Values: Our Guiding Principles πΊπΈ
Our military service instilled values that continue to guide us as software engineers:
1. Integrity First
- Write clear, maintainable code that reflects its intended purpose
- Own your mistakes and learn from them
- Practice radical transparency in your work
- Give credit where credit is due
- Document truthfully and thoroughly
2. Service Before Self
- Your code impacts the entire team and community
- Build solutions that benefit the whole organization
- Support the developer community through open-source contributions
- Put user needs at the forefront of development decisions
- Mentor and support your fellow veterans
3. Excellence In All We Do
- Commit to continuous improvement
- Regularly evaluate and enhance your code
- Stay current with industry best practices
- Share knowledge to elevate the entire team
- Maintain high standards in all deliverables
Goal
To provide a comprehensive field manual that:
- Guides veterans through their software engineering journey
- Standardizes project documentation and processes
- Serves as a quick-reference technical guide
- Maintains operational readiness through best practices
- Fosters a culture of collaboration and knowledge sharing
- Upholds the core values of Integrity, Service, and Excellence
- Empowers veterans to succeed in the tech industry
- Supports the Vets Who Code community
- Encourages contributions and feedback from all members
General Guidance: Professional Development Guidelines πΊπΈ
- Maintain high standards through thorough code reviews and testing
- Prioritize quality over speed - careful planning prevents future issues
- Focus on one task at a time using GitHub Projects for organization
- Practice clear communication:
- Use wikis for documentation
- Engage in discussions for knowledge sharing
- Create detailed issues for tracking work
- Start with simple, effective solutions before adding complexity
- Respect project scope - create new issues for additional features
- Deploy updates incrementally and document changes clearly
- Keep your team informed through regular updates
- Report problems thoroughly with clear reproduction steps
- Take ownership of the codebase - everyone is responsible for quality
- Leverage automation through GitHub Actions to ensure consistency
- Use standardized templates to streamline processes
Battle Cry
"Code with Honor, Deploy with Pride! ποΈ"
Remember: Our core values of Integrity, Service, and Excellence guide everything we do. From writing our first line of code to deploying enterprise solutions, we maintain the high standards that defined our military service.
This is a Living Document
These SOPs are maintained and improved by the Vets Who Code community. All contributions are welcome!
How to Contribute
- Submit Pull Requests
- Improve existing documentation
- Add new sections based on experience
- Update technical references
-
Fix errors or clarify instructions
-
Report Issues
- Identify areas needing clarification
- Suggest new topics to cover
- Report outdated information
-
Request additional examples
-
Share Knowledge
- Document lessons learned
- Add field notes from your experience
- Contribute code examples
- Suggest process improvements
Contribution Guidelines
- Follow the Format
- Maintain military terminology
- Include clear examples
- Provide practical context
-
Keep documentation actionable
-
Maintain Standards
- Ensure technical accuracy
- Follow markdown formatting
- Include relevant references
-
Test any code examples
-
Review Process
- All changes undergo peer review
- Technical accuracy verification
- Style guide compliance check
- Community feedback integration
Remember: This document evolves with our community. Your experience transitioning from military service to software engineering is valuable - share it to help others succeed.
Together, we maintain excellence in our code and our conduct. πΊπΈ