|
| 1 | +<!DOCTYPE html> |
| 2 | +<html lang="en"> |
| 3 | +<head> |
| 4 | + <meta charset="UTF-8"> |
| 5 | + <meta name="description" content="FRC team 3512 software team goals"> |
| 6 | + <meta name="viewport" content="width=device-width, initial-scale=1"> |
| 7 | + <title>Goals - FRC Team 3512</title> |
| 8 | + <link rel="stylesheet" type="text/css" href="../../main.css"> |
| 9 | + <link rel="shortcut icon" type="image/ico" href="../../favicon.png"> |
| 10 | +</head> |
| 11 | +<body> |
| 12 | + <input type="checkbox" id="ham-menu"> |
| 13 | + <label for="ham-menu"> |
| 14 | + <div class="hide-des"> |
| 15 | + <span class="menu-line"></span> |
| 16 | + <span class="menu-line"></span> |
| 17 | + <span class="menu-line"></span> |
| 18 | + <span class="menu-line"></span> |
| 19 | + <span class="menu-line"></span> |
| 20 | + <span class="menu-line"></span> |
| 21 | + </div> |
| 22 | + |
| 23 | + </label> |
| 24 | + <div class="full-page-blue"></div> |
| 25 | + <div class="ham-menu"> |
| 26 | + <ul class="centre-text bold-text"> |
| 27 | + <li> |
| 28 | + <a href="../">Home</a> |
| 29 | + </li> |
| 30 | + <li> |
| 31 | + <a href="/index.html">Admin</a> |
| 32 | + </li> |
| 33 | + <li> |
| 34 | + <a href="../bootstrap/index.html">Developer Bootstraps</a> |
| 35 | + </li> |
| 36 | + <li> |
| 37 | + <a href="../vpn/index.html">VPN Setup</a> |
| 38 | + </li> |
| 39 | + <li> |
| 40 | + <a href="../ci/index.html">Curriculum</a> |
| 41 | + </li> |
| 42 | + <li> |
| 43 | + <a href="../fll/index.html">FLL</a> |
| 44 | + </li> |
| 45 | + <li> |
| 46 | + <a href="../archives/index.html">Archives</a> |
| 47 | + </li> |
| 48 | + </ul> |
| 49 | + </div> |
| 50 | + <div class="body"> |
| 51 | + <div class="Content"> |
| 52 | + <h1>Goals</h1> |
| 53 | + <div class="Information_Box"> |
| 54 | + <p><b>Prepare students for Computer Science at university</b></p> |
| 55 | + <p>The focus should be on "Design before build". That is, developing a specification for behavior |
| 56 | + before implementing it. Teach common development practices like Git and code review.</p> |
| 57 | + <p><b>Teach an introduction to control theory for those interested</b></p> |
| 58 | + <p>This is also needed for a reliable / maximally efficient robot and includes state machines, |
| 59 | + motion profiles, filters, and feedback/feedforward controllers.</p> |
| 60 | + <p><b>Use graphical tools to gain insight</b></p> |
| 61 | + <p>Basically, a picture or movie is worth a thousand words. The following are good examples of visualization tools.</p> |
| 62 | + <p><b>Use industry standard tools to handle auxiliary tasks</b></p> |
| 63 | + <p>Students should be able to leverage existing tools to make their jobs as software developers easier. Labs are encouraged to use |
| 64 | + tooling if it doesn't automate what the student is intended to learn through practice.</p> |
| 65 | + </div> |
| 66 | + <button type="button" class="collapsible"> |
| 67 | + The following is a list of goals the software team tries to meet each year. |
| 68 | + They inform decisions regarding our curriculum design and operating procedures. |
| 69 | + </button> |
| 70 | + <div class="content"> |
| 71 | + <ul> |
| 72 | + <li>Produce an effective product</li> |
| 73 | + <li>Employ industry best practices</li> |
| 74 | + <li>Expand our knowledge and capabilities</li> |
| 75 | + <li>Involve less experienced team members</li> |
| 76 | + <li>Find tasks requiring less experience</li> |
| 77 | + <li>Create an autonomous software team / encourage learning</li> |
| 78 | + <li>Provide access to resources for motivated students</li> |
| 79 | + <li>Teach incoming members enough C++ to be useful</li> |
| 80 | + <li>Integrate modern C++ development paradigms, tools, and practices</li> |
| 81 | + </ul> |
| 82 | + </div> |
| 83 | + </div> |
| 84 | + </div> |
| 85 | + <script src="../../Collapse.js"></script> |
| 86 | +</body> |
| 87 | +</html> |
0 commit comments