37
37
</ header >
38
38
< div class ="body ">
39
39
< h1 > FRC 3512 Software Team</ h1 >
40
- < div class ="Who_we_are_sec ">
40
+ < div class ="Info ">
41
41
< h2 id ="Who_we_are "> Who We Are</ h2 >
42
42
< p > We are the software subteam of < a href =
43
43
"https://www.spartatroniks.com/ "> FRC Team 3512</ a > located in Orcutt,
@@ -47,79 +47,83 @@ <h2 id="Who_we_are">Who We Are</h2>
47
47
< p > This website is a collection of student and mentor knowledge and a
48
48
teaching aid.</ p >
49
49
</ div >
50
- < div class ="Our_vision_sec ">
51
- < h2 id ="Our_vision "> Our vision </ h2 >
50
+ < div class ="Info ">
51
+ < h2 id ="Our_vision "> Our Vision </ h2 >
52
52
< p > Produce competent software engineers who:</ p >
53
53
< ol >
54
54
< li > Understand the tradeoff between maintainability and performance.</ li >
55
55
< li > Can recognize when a given programming language or feature is the
56
56
right fit for a problem.</ li >
57
57
</ ol >
58
58
</ div >
59
- < div class ="What_students_will_learn_sec ">
60
- < h2 id ="What_students_will_learn "> What students will learn </ h2 >
59
+ < div class ="Info ">
60
+ < h2 id ="What_students_will_learn "> What Students Learn </ h2 >
61
61
< p > The software subteam programs the robot to make it move and automate
62
62
parts of its functionality. Our goal is to expose you to the software
63
63
engineering process in a low-risk, collaborative learning environment so
64
64
that if you eventually move on to computer science in college or in
65
65
industry, you'll have all the tools you need to succeed.</ p >
66
- < p > You will learn the following throughout your tenure as a software
67
- subteam member:</ p >
68
- < ol >
69
- < li > The mindset software engineers use to break down and solve problems
70
- (how to think like a programmer).
71
- < ul >
72
- < li > What tools programming languages offer, and when/how to apply
73
- them solve problems in a manner that is effective, efficient, and
74
- promotes the long-term maintainability of the software project.</ li >
75
- </ ul >
76
- </ li >
77
- < li > The tools and methodologies software engineers use to collaborate
78
- with each other and manage the complexity of a software project.</ li >
79
- < li > Software engineering principles for real-time and embedded
80
- systems.</ li >
81
- < li > Control theory, which lets us do two things:
82
- < ul >
83
- < li > Model our robots mathematically so we can test our software's
84
- correctness before the hardware is completed.</ li >
85
- < li > Design and test controllers for those models that ensure actions
86
- like "move the elevator to this position" will work with minimal
87
- trial-and-error on the real hardware.</ li >
88
- </ ul >
89
- </ li >
90
- < li > How to write automated tests that ensure our software continues to
91
- work as we add features and perform cleanups.</ li >
92
- </ ol >
66
+ < button type ="button " class ="collapsible ">
67
+ What to expect our students to learn:
68
+ </ button >
69
+ < div class ="content ">
70
+ < ol >
71
+ < li > The mindset software engineers use to break down and solve problems
72
+ (how to think like a programmer).
73
+ < ul >
74
+ < li > What tools programming languages offer, and when/how to apply
75
+ them solve problems in a manner that is effective, efficient, and
76
+ promotes the long-term maintainability of the software project.</ li >
77
+ </ ul >
78
+ </ li >
79
+ < li > The tools and methodologies software engineers use to collaborate
80
+ with each other and manage the complexity of a software project.</ li >
81
+ < li > Software engineering principles for real-time and embedded
82
+ systems.</ li >
83
+ < li > Control theory, which lets us do two things:
84
+ < ul >
85
+ < li > Model our robots mathematically so we can test our software's
86
+ correctness before the hardware is completed.</ li >
87
+ < li > Design and test controllers for those models that ensure actions
88
+ like "move the elevator to this position" will work with minimal
89
+ trial-and-error on the real hardware.</ li >
90
+ </ ul >
91
+ </ li >
92
+ < li > How to write automated tests that ensure our software continues to
93
+ work as we add features and perform cleanups.</ li >
94
+ </ ol >
93
95
</ div >
94
- < div class ="Admin_sec ">
96
+ </ div >
97
+ < script src ="Collapse.js "> </ script >
98
+ < div class ="Direct_links ">
95
99
< h2 id ="Administration "> < a href ="admin/ "> Administration</ a > </ h2 >
96
100
< p > Describes the software team's goals, its organization, and how it's
97
101
run.</ p >
98
102
</ div >
99
- < div class ="Dev_bootstraps-sec ">
103
+ < div class ="Direct_links ">
100
104
< h2 id ="Developer_bootstrap "> < a href ="bootstrap/ "> Developer
101
105
bootstrap</ a > </ h2 >
102
106
< p > Provides the necessary tools to begin programming in C++.</ p >
103
107
</ div >
104
- < div class ="VPN_setup_sec ">
108
+ < div class ="Direct_links ">
105
109
< h2 id ="VPN_setup "> < a href ="vpn/ "> VPN setup</ a > </ h2 >
106
110
< p > Instructions for connecting to our robot VPN.</ p >
107
111
</ div >
108
- < div class ="Curriculum_sec ">
112
+ < div class ="Direct_links ">
109
113
< h2 id ="Curriculum_and_instruction "> < a href ="ci/ "> Curriculum and
110
114
instruction</ a > </ h2 >
111
115
< p > Contains the software team teaching materials.</ p >
112
116
</ div >
113
- < div class ="Github_sec ">
117
+ < div class ="Direct_links ">
114
118
< h2 id ="GitHub "> < a href ="https://github.com/frc3512/ "> GitHub</ a > </ h2 >
115
119
< p > The software team's GitHub organization, which contains mirrors of our
116
120
Git repositories.</ p >
117
121
</ div >
118
- < div class ="FLL_sec ">
122
+ < div class ="Direct_links ">
119
123
< h2 id ="FLL "> < a href ="fll/ "> FLL</ a > </ h2 >
120
124
< p > FLL-related stuff the software team deals with on an annual basis.</ p >
121
125
</ div >
122
- < div class ="Archives_sec ">
126
+ < div class ="Direct_links ">
123
127
< h2 id ="Archives "> < a href ="archives/ "> Archives</ a > </ h2 >
124
128
< p > Contains legacy projects and resources from throughout the team's
125
129
history.</ p >
0 commit comments