From 69865e43a7af85d6f6eccaf57fc2069b3aca4221 Mon Sep 17 00:00:00 2001 From: Evan Pratten Date: Fri, 21 Jun 2019 16:12:23 -0400 Subject: [PATCH] FRC programming --- _includes/footer.html | 12 +- _includes/head.html | 16 +- _posts/2019-06-21-Robot-Experiences.md | 51 +++++ _site/404.html | 27 ++- _site/DeepSpace.html | 27 ++- _site/all_posts.html | 107 ++++++++-- _site/css/2019/06/12/Styiling-GitHub.html | 27 ++- _site/devrant/2018/06/27/BecomeRanter.html | 27 ++- _site/feed.xml | 62 +++++- _site/frc/2019/04/30/FRC-Languages.html | 27 ++- .../05/27/Building-Safe-Vision-Comms.html | 27 ++- _site/frc/2019/06/16/Graphing-w2a.html | 27 ++- _site/frc/2019/06/21/Robot-Experiences.html | 190 ++++++++++++++++++ _site/index.html | 75 ++++--- _site/music/2019/06/17/AMM2M1-release.html | 27 ++- _site/random/2019/06/18/Blogs-I-Read.html | 146 ++++++++++++++ 16 files changed, 696 insertions(+), 179 deletions(-) create mode 100644 _posts/2019-06-21-Robot-Experiences.md create mode 100644 _site/frc/2019/06/21/Robot-Experiences.html create mode 100644 _site/random/2019/06/18/Blogs-I-Read.html diff --git a/_includes/footer.html b/_includes/footer.html index 8770bd3..a5a3b58 100644 --- a/_includes/footer.html +++ b/_includes/footer.html @@ -37,13 +37,13 @@ - - - - - + + + + + - + diff --git a/_includes/head.html b/_includes/head.html index 1355dd7..d93c463 100644 --- a/_includes/head.html +++ b/_includes/head.html @@ -1,9 +1,9 @@ - {{ site.title }} - - - - - - - + {{ site.title }} + + + + + + + \ No newline at end of file diff --git a/_posts/2019-06-21-Robot-Experiences.md b/_posts/2019-06-21-Robot-Experiences.md new file mode 100644 index 0000000..8dbeceb --- /dev/null +++ b/_posts/2019-06-21-Robot-Experiences.md @@ -0,0 +1,51 @@ +--- +layout: post +title: "What I have learned from 2 years of FRC programming" +description: "Robots are pretty cool" +date: 2019-06-21 15:14:00 +categories: frc +--- + +Over the past two years (2018 / 2019), I have been a member of my school's [FRC](https://www.firstinspires.org/robotics/frc) team, [Raider Robotics](frc5024.github.io). Specifically, a programmer. + +## My roles +In my first year, I joined the team as a programmer and had a fun time learning about embedded programming and development with hardware. Then, in my second year, I was promoted to programming co-lead along with [@slownie](https://github.com/slownie). I much preferred my second season because I had a better understanding of the technology I was working with, and we got to play with some cool tools throughout the season. + +## What I have learned +Starting with our 2018 season, PowerUP. We learned early on that there is a practical limit to the number of programmers that 5024 can handle. That year, we had too many, and our situation was not helped by the fact that some members preferred scrolling through Instagram over writing code. This issue was almost entirely fixed by the introduction of a mandatory skill exam at the start of the season. Sam and I did not really care about the scores of the exam because, from reading the results, we could see who was actually motivated to join the team. Thanks to the test, we entered the season with seven excited programmers. + +During the PowerUP season, I also learned the importance of student involvement. Most of the code from the season was written by mentors with the students just watching on a projecter. After talking with other team members, I learned that none of them through this was a good method of teaching, and many felt powerless. In the 2019 season, I completely reversed this. All students worked together on the codebase, and the mentors worked on other projects and provided input where needed. + +### Version Control +During the 2018 season, code was shared around by USB. This lead to crazy conflicts, confusion over what was running on the robot, and general frustration during competitions. In 2019, I moved the team over to a [GitHub](https://github.com) organization account and sent an email to support to get us unlimited private repos (thanks GitHub!). For the team members that where not comfortable in the terminal, I set them up with [GitKracken PRO](https://www.gitkraken.com/) accounts, and they enjoyed using the program. The rest of us stuck with GIT cli, or various plugins for VSCode. + +### Alpha test +I got our team on board with the 2019 toolchain alpha test the week it was released in order to get everyone used to the new tools before the season (and help find bugs for the WPILib team). The new buildsystem, Gradle, worked great and I could even run it on the chromebook I was using for development at the time! To further assist the team, I set up a CI pipeline for automatic testing and code reviews of Pull Requests, and a doxygen + GitHub pages CD pipeline for our new documentation webpage. + +### Webdocs +A significant amount of my time was spent answering repetitive questions from the team. I enjoy helping people out, but explaining the same things over and over was starting to frustrate me. This was caused by a lack of documentation or bits of documentation spread over multiple websites. To solve this problem, I started the [Webdocs Page](https://frc5024.github.io/webdocs/#/). This website is designed to house a mix of team-specific notes, guides, low-level documentation, and documentation from all FRC vendors. This site was published after the season, so I will find out how usefull it really is during the 2020 season. + +### Command base +"Command based programming is great. But..." is probably the best way to describe my suggested changes for 2020. + +I have been learning from other teams, and from mentors about better ways to control our robot. During the offseason, I am playing with new ways to write robot code. Here are some of my changes: + - Use a custom replacement for WPILib's [Subsystem](https://first.wpi.edu/FRC/roborio/release/docs/java/edu/wpi/first/wpilibj/command/Subsystem.html) that buffers it's inputs and outputs + - This reduces load on our CAN and Ethernet networks + - Offload all camera and vision work to a Raspberry PI + - Every subsystem must push telemetry data to NetworkTables for easy debugging and detailed logs + - Use a custom logging system that buffers writes to stdout. This reduces network strain + +I am working on many other changes over on the [MiniBot](https://github.com/frc5024/MiniBot) codebase. + +## My plans for 2020 +I have been re-selected to be the sole lead of the 5024 programming team for 2020. Here are my goals: + - Switch the team from C++ to Java + - Easier for prototyping + - Better memory management for high-level programmers + - Better documentation from vendors + - It is taught in our school's compsci classes + - Remove the skills exam in favour of weekly homework for the first 8 weeks + - Provide writeups of lessons + - Have mentors do "guest presentations" + - Dedicate a day to robot driving lessons + - Use a custom library with wrappers and tools built by me to provide easy interfaces for new programmers \ No newline at end of file diff --git a/_site/404.html b/_site/404.html index 6140b50..ffdb22b 100644 --- a/_site/404.html +++ b/_site/404.html @@ -7,16 +7,15 @@ - Evan Pratten - - - - - - + Evan Pratten + + + + + + - @@ -113,13 +112,13 @@ - - - - - + + + + + - + diff --git a/_site/DeepSpace.html b/_site/DeepSpace.html index ce30ec8..4e27a49 100644 --- a/_site/DeepSpace.html +++ b/_site/DeepSpace.html @@ -7,16 +7,15 @@ - Evan Pratten - - - - - - + Evan Pratten + + + + + + - @@ -113,13 +112,13 @@ - - - - - + + + + + - + diff --git a/_site/all_posts.html b/_site/all_posts.html index b6ee598..ed4abc2 100644 --- a/_site/all_posts.html +++ b/_site/all_posts.html @@ -7,16 +7,15 @@ - Evan Pratten - - - - - - + Evan Pratten + + + + + + - @@ -79,6 +78,86 @@
+
+

What I have learned from 2 years of FRC programming

+
+ +

2019-06-21 11:14:00 -0400

+

Over the past two years (2018 / 2019), I have been a member of my school’s FRC team, Raider Robotics. Specifically, a programmer.

+ +

My roles

+

In my first year, I joined the team as a programmer and had a fun time learning about embedded programming and development with hardware. Then, in my second year, I was promoted to programming co-lead along with @slownie. I much preferred my second season because I had a better understanding of the technology I was working with, and we got to play with some cool tools throughout the season.

+ +

What I have learned

+

Starting with our 2018 season, PowerUP. We learned early on that there is a practical limit to the number of programmers that 5024 can handle. That year, we had too many, and our situation was not helped by the fact that some members preferred scrolling through Instagram over writing code. This issue was almost entirely fixed by the introduction of a mandatory skill exam at the start of the season. Sam and I did not really care about the scores of the exam because, from reading the results, we could see who was actually motivated to join the team. Thanks to the test, we entered the season with seven excited programmers.

+ +

During the PowerUP season, I also learned the importance of student involvement. Most of the code from the season was written by mentors with the students just watching on a projecter. After talking with other team members, I learned that none of them through this was a good method of teaching, and many felt powerless. In the 2019 season, I completely reversed this. All students worked together on the codebase, and the mentors worked on other projects and provided input where needed.

+ +

Version Control

+

During the 2018 season, code was shared around by USB. This lead to crazy conflicts, confusion over what was running on the robot, and general frustration during competitions. In 2019, I moved the team over to a GitHub organization account and sent an email to support to get us unlimited private repos (thanks GitHub!). For the team members that where not comfortable in the terminal, I set them up with GitKracken PRO accounts, and they enjoyed using the program. The rest of us stuck with GIT cli, or various plugins for VSCode.

+ +

Alpha test

+

I got our team on board with the 2019 toolchain alpha test the week it was released in order to get everyone used to the new tools before the season (and help find bugs for the WPILib team). The new buildsystem, Gradle, worked great and I could even run it on the chromebook I was using for development at the time! To further assist the team, I set up a CI pipeline for automatic testing and code reviews of Pull Requests, and a doxygen + GitHub pages CD pipeline for our new documentation webpage.

+ +

Webdocs

+

A significant amount of my time was spent answering repetitive questions from the team. I enjoy helping people out, but explaining the same things over and over was starting to frustrate me. This was caused by a lack of documentation or bits of documentation spread over multiple websites. To solve this problem, I started the Webdocs Page. This website is designed to house a mix of team-specific notes, guides, low-level documentation, and documentation from all FRC vendors. This site was published after the season, so I will find out how usefull it really is during the 2020 season.

+ +

Command base

+

“Command based programming is great. But…” is probably the best way to describe my suggested changes for 2020.

+ +

I have been learning from other teams, and from mentors about better ways to control our robot. During the offseason, I am playing with new ways to write robot code. Here are some of my changes:

+ + +

I am working on many other changes over on the MiniBot codebase.

+ +

My plans for 2020

+

I have been re-selected to be the sole lead of the 5024 programming team for 2020. Here are my goals:

+ +

+ + + +
+

Blogs I Read

+
+ +

2019-06-18 09:18:00 -0400

+

This is a copy-pastable list of rss feeds I subscribe to:

+ +
https://www.firstinspires.org/robotics/frc/blog-rss
+https://lukesmith.xyz/rss.xml
+https://daniellockyer.com/feed.xml
+http://www.windytan.com/rss.xml
+http://psy-lob-saw.blogspot.com/rss.xml
+https://retrylife.ca/feed.xml
+
+

+ + +

I made a new song!

@@ -360,13 +439,13 @@ pip3 install tensorflow-gpu #for gpu processing
- - - - - + + + + + - + diff --git a/_site/css/2019/06/12/Styiling-GitHub.html b/_site/css/2019/06/12/Styiling-GitHub.html index 85a0669..f14c096 100644 --- a/_site/css/2019/06/12/Styiling-GitHub.html +++ b/_site/css/2019/06/12/Styiling-GitHub.html @@ -7,16 +7,15 @@ - Evan Pratten - - - - - - + Evan Pratten + + + + + + - @@ -151,13 +150,13 @@ - - - - - + + + + + - + diff --git a/_site/devrant/2018/06/27/BecomeRanter.html b/_site/devrant/2018/06/27/BecomeRanter.html index 0ae70e7..4a61546 100644 --- a/_site/devrant/2018/06/27/BecomeRanter.html +++ b/_site/devrant/2018/06/27/BecomeRanter.html @@ -7,16 +7,15 @@ - Evan Pratten - - - - - - + Evan Pratten + + + + + + - @@ -163,13 +162,13 @@ pip3 install tensorflow-gpu #for gpu processing - - - - - + + + + + - + diff --git a/_site/feed.xml b/_site/feed.xml index 44d1e01..e591c42 100644 --- a/_site/feed.xml +++ b/_site/feed.xml @@ -1,4 +1,64 @@ -Jekyll2019-06-17T22:09:49-04:00http://localhost:4000/feed.xmlEvan PrattenComputer wizard, student, <a href="https://github.com/frc5024">@frc5024</a> programming team lead, and radio enthusiast.I made a new song!2019-06-17T06:20:00-04:002019-06-17T06:20:00-04:00http://localhost:4000/music/2019/06/17/AMM2M1-release<p>I am currently taking a class in school called <a href="https://www.facebook.com/studio225beal/">Music and computers (AMM2M)</a>, where as part of the class, whe get together into bands, and produce a song. After taking a break from music production for over a year, we have released our song for the class (we do two songs, but the second is not finished yet).</p> +Jekyll2019-06-21T16:12:12-04:00http://localhost:4000/feed.xmlEvan PrattenComputer wizard, student, <a href="https://github.com/frc5024">@frc5024</a> programming team lead, and radio enthusiast.What I have learned from 2 years of FRC programming2019-06-21T11:14:00-04:002019-06-21T11:14:00-04:00http://localhost:4000/frc/2019/06/21/Robot-Experiences<p>Over the past two years (2018 / 2019), I have been a member of my school’s <a href="https://www.firstinspires.org/robotics/frc">FRC</a> team, <a href="frc5024.github.io">Raider Robotics</a>. Specifically, a programmer.</p> + +<h2 id="my-roles">My roles</h2> +<p>In my first year, I joined the team as a programmer and had a fun time learning about embedded programming and development with hardware. Then, in my second year, I was promoted to programming co-lead along with <a href="https://github.com/slownie">@slownie</a>. I much preferred my second season because I had a better understanding of the technology I was working with, and we got to play with some cool tools throughout the season.</p> + +<h2 id="what-i-have-learned">What I have learned</h2> +<p>Starting with our 2018 season, PowerUP. We learned early on that there is a practical limit to the number of programmers that 5024 can handle. That year, we had too many, and our situation was not helped by the fact that some members preferred scrolling through Instagram over writing code. This issue was almost entirely fixed by the introduction of a mandatory skill exam at the start of the season. Sam and I did not really care about the scores of the exam because, from reading the results, we could see who was actually motivated to join the team. Thanks to the test, we entered the season with seven excited programmers.</p> + +<p>During the PowerUP season, I also learned the importance of student involvement. Most of the code from the season was written by mentors with the students just watching on a projecter. After talking with other team members, I learned that none of them through this was a good method of teaching, and many felt powerless. In the 2019 season, I completely reversed this. All students worked together on the codebase, and the mentors worked on other projects and provided input where needed.</p> + +<h3 id="version-control">Version Control</h3> +<p>During the 2018 season, code was shared around by USB. This lead to crazy conflicts, confusion over what was running on the robot, and general frustration during competitions. In 2019, I moved the team over to a <a href="https://github.com">GitHub</a> organization account and sent an email to support to get us unlimited private repos (thanks GitHub!). For the team members that where not comfortable in the terminal, I set them up with <a href="https://www.gitkraken.com/">GitKracken PRO</a> accounts, and they enjoyed using the program. The rest of us stuck with GIT cli, or various plugins for VSCode.</p> + +<h3 id="alpha-test">Alpha test</h3> +<p>I got our team on board with the 2019 toolchain alpha test the week it was released in order to get everyone used to the new tools before the season (and help find bugs for the WPILib team). The new buildsystem, Gradle, worked great and I could even run it on the chromebook I was using for development at the time! To further assist the team, I set up a CI pipeline for automatic testing and code reviews of Pull Requests, and a doxygen + GitHub pages CD pipeline for our new documentation webpage.</p> + +<h3 id="webdocs">Webdocs</h3> +<p>A significant amount of my time was spent answering repetitive questions from the team. I enjoy helping people out, but explaining the same things over and over was starting to frustrate me. This was caused by a lack of documentation or bits of documentation spread over multiple websites. To solve this problem, I started the <a href="https://frc5024.github.io/webdocs/#/">Webdocs Page</a>. This website is designed to house a mix of team-specific notes, guides, low-level documentation, and documentation from all FRC vendors. This site was published after the season, so I will find out how usefull it really is during the 2020 season.</p> + +<h3 id="command-base">Command base</h3> +<p>“Command based programming is great. But…” is probably the best way to describe my suggested changes for 2020.</p> + +<p>I have been learning from other teams, and from mentors about better ways to control our robot. During the offseason, I am playing with new ways to write robot code. Here are some of my changes:</p> +<ul> + <li>Use a custom replacement for WPILib’s <a href="https://first.wpi.edu/FRC/roborio/release/docs/java/edu/wpi/first/wpilibj/command/Subsystem.html">Subsystem</a> that buffers it’s inputs and outputs + <ul> + <li>This reduces load on our CAN and Ethernet networks</li> + </ul> + </li> + <li>Offload all camera and vision work to a Raspberry PI</li> + <li>Every subsystem must push telemetry data to NetworkTables for easy debugging and detailed logs</li> + <li>Use a custom logging system that buffers writes to stdout. This reduces network strain</li> +</ul> + +<p>I am working on many other changes over on the <a href="https://github.com/frc5024/MiniBot">MiniBot</a> codebase.</p> + +<h2 id="my-plans-for-2020">My plans for 2020</h2> +<p>I have been re-selected to be the sole lead of the 5024 programming team for 2020. Here are my goals:</p> +<ul> + <li>Switch the team from C++ to Java + <ul> + <li>Easier for prototyping</li> + <li>Better memory management for high-level programmers</li> + <li>Better documentation from vendors</li> + <li>It is taught in our school’s compsci classes</li> + </ul> + </li> + <li>Remove the skills exam in favour of weekly homework for the first 8 weeks</li> + <li>Provide writeups of lessons</li> + <li>Have mentors do “guest presentations”</li> + <li>Dedicate a day to robot driving lessons</li> + <li>Use a custom library with wrappers and tools built by me to provide easy interfaces for new programmers</li> +</ul>Over the past two years (2018 / 2019), I have been a member of my school’s FRC team, Raider Robotics. Specifically, a programmer.Blogs I Read2019-06-18T09:18:00-04:002019-06-18T09:18:00-04:00http://localhost:4000/random/2019/06/18/Blogs-I-Read<p>This is a copy-pastable list of rss feeds I subscribe to:</p> + +<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>https://www.firstinspires.org/robotics/frc/blog-rss +https://lukesmith.xyz/rss.xml +https://daniellockyer.com/feed.xml +http://www.windytan.com/rss.xml +http://psy-lob-saw.blogspot.com/rss.xml +https://retrylife.ca/feed.xml +</code></pre></div></div>This is a copy-pastable list of rss feeds I subscribe to:I made a new song!2019-06-17T06:20:00-04:002019-06-17T06:20:00-04:00http://localhost:4000/music/2019/06/17/AMM2M1-release<p>I am currently taking a class in school called <a href="https://www.facebook.com/studio225beal/">Music and computers (AMM2M)</a>, where as part of the class, whe get together into bands, and produce a song. After taking a break from music production for over a year, we have released our song for the class (we do two songs, but the second is not finished yet).</p> <h2 id="my-contribution">My contribution</h2> <p>My main contribution to the project was a mix of live drumming, and most of the song’s MIDI work. The song is far from perfect, but pretty good for the time we had to produce it.</p> diff --git a/_site/frc/2019/04/30/FRC-Languages.html b/_site/frc/2019/04/30/FRC-Languages.html index 9922b51..6841408 100644 --- a/_site/frc/2019/04/30/FRC-Languages.html +++ b/_site/frc/2019/04/30/FRC-Languages.html @@ -7,16 +7,15 @@ - Evan Pratten - - - - - - + Evan Pratten + + + + + + - @@ -127,13 +126,13 @@ - - - - - + + + + + - + diff --git a/_site/frc/2019/05/27/Building-Safe-Vision-Comms.html b/_site/frc/2019/05/27/Building-Safe-Vision-Comms.html index 69010a7..8c736f3 100644 --- a/_site/frc/2019/05/27/Building-Safe-Vision-Comms.html +++ b/_site/frc/2019/05/27/Building-Safe-Vision-Comms.html @@ -7,16 +7,15 @@ - Evan Pratten - - - - - - + Evan Pratten + + + + + + - @@ -140,13 +139,13 @@ - - - - - + + + + + - + diff --git a/_site/frc/2019/06/16/Graphing-w2a.html b/_site/frc/2019/06/16/Graphing-w2a.html index 191a259..776e60b 100644 --- a/_site/frc/2019/06/16/Graphing-w2a.html +++ b/_site/frc/2019/06/16/Graphing-w2a.html @@ -7,16 +7,15 @@ - Evan Pratten - - - - - - + Evan Pratten + + + + + + - @@ -165,13 +164,13 @@ - - - - - + + + + + - + diff --git a/_site/frc/2019/06/21/Robot-Experiences.html b/_site/frc/2019/06/21/Robot-Experiences.html new file mode 100644 index 0000000..65f1080 --- /dev/null +++ b/_site/frc/2019/06/21/Robot-Experiences.html @@ -0,0 +1,190 @@ + + + + + + Evan Pratten + + + + + + + + + + + +
+ + + + + + + + + +
+ + +
+
+
+

What I have learned from 2 years of FRC programming

+
+ +

Over the past two years (2018 / 2019), I have been a member of my school’s FRC team, Raider Robotics. Specifically, a programmer.

+ +

My roles

+

In my first year, I joined the team as a programmer and had a fun time learning about embedded programming and development with hardware. Then, in my second year, I was promoted to programming co-lead along with @slownie. I much preferred my second season because I had a better understanding of the technology I was working with, and we got to play with some cool tools throughout the season.

+ +

What I have learned

+

Starting with our 2018 season, PowerUP. We learned early on that there is a practical limit to the number of programmers that 5024 can handle. That year, we had too many, and our situation was not helped by the fact that some members preferred scrolling through Instagram over writing code. This issue was almost entirely fixed by the introduction of a mandatory skill exam at the start of the season. Sam and I did not really care about the scores of the exam because, from reading the results, we could see who was actually motivated to join the team. Thanks to the test, we entered the season with seven excited programmers.

+ +

During the PowerUP season, I also learned the importance of student involvement. Most of the code from the season was written by mentors with the students just watching on a projecter. After talking with other team members, I learned that none of them through this was a good method of teaching, and many felt powerless. In the 2019 season, I completely reversed this. All students worked together on the codebase, and the mentors worked on other projects and provided input where needed.

+ +

Version Control

+

During the 2018 season, code was shared around by USB. This lead to crazy conflicts, confusion over what was running on the robot, and general frustration during competitions. In 2019, I moved the team over to a GitHub organization account and sent an email to support to get us unlimited private repos (thanks GitHub!). For the team members that where not comfortable in the terminal, I set them up with GitKracken PRO accounts, and they enjoyed using the program. The rest of us stuck with GIT cli, or various plugins for VSCode.

+ +

Alpha test

+

I got our team on board with the 2019 toolchain alpha test the week it was released in order to get everyone used to the new tools before the season (and help find bugs for the WPILib team). The new buildsystem, Gradle, worked great and I could even run it on the chromebook I was using for development at the time! To further assist the team, I set up a CI pipeline for automatic testing and code reviews of Pull Requests, and a doxygen + GitHub pages CD pipeline for our new documentation webpage.

+ +

Webdocs

+

A significant amount of my time was spent answering repetitive questions from the team. I enjoy helping people out, but explaining the same things over and over was starting to frustrate me. This was caused by a lack of documentation or bits of documentation spread over multiple websites. To solve this problem, I started the Webdocs Page. This website is designed to house a mix of team-specific notes, guides, low-level documentation, and documentation from all FRC vendors. This site was published after the season, so I will find out how usefull it really is during the 2020 season.

+ +

Command base

+

“Command based programming is great. But…” is probably the best way to describe my suggested changes for 2020.

+ +

I have been learning from other teams, and from mentors about better ways to control our robot. During the offseason, I am playing with new ways to write robot code. Here are some of my changes:

+
    +
  • Use a custom replacement for WPILib’s Subsystem that buffers it’s inputs and outputs +
      +
    • This reduces load on our CAN and Ethernet networks
      • +
    +
    • +
  • Offload all camera and vision work to a Raspberry PI
    • +
  • Every subsystem must push telemetry data to NetworkTables for easy debugging and detailed logs
    • +
  • Use a custom logging system that buffers writes to stdout. This reduces network strain
    • +
+ +

I am working on many other changes over on the MiniBot codebase.

+ +

My plans for 2020

+

I have been re-selected to be the sole lead of the 5024 programming team for 2020. Here are my goals:

+
    +
  • Switch the team from C++ to Java +
      +
    • Easier for prototyping
      • +
    • Better memory management for high-level programmers
      • +
    • Better documentation from vendors
      • +
    • It is taught in our school’s compsci classes
      • +
    +
    • +
  • Remove the skills exam in favour of weekly homework for the first 8 weeks
    • +
  • Provide writeups of lessons
    • +
  • Have mentors do “guest presentations”
    • +
  • Dedicate a day to robot driving lessons
    • +
  • Use a custom library with wrappers and tools built by me to provide easy interfaces for new programmers
    • +
+

+
+
+ +
+ + + + +
+ + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/_site/index.html b/_site/index.html index 5c6d708..bae85f0 100644 --- a/_site/index.html +++ b/_site/index.html @@ -7,16 +7,15 @@ - Evan Pratten - - - - - - + Evan Pratten + + + + + + - @@ -121,6 +120,30 @@
+ + + + + + + +
@@ -169,30 +192,6 @@ - - - - - - - - @@ -249,13 +248,13 @@ - - - - - + + + + + - + diff --git a/_site/music/2019/06/17/AMM2M1-release.html b/_site/music/2019/06/17/AMM2M1-release.html index 5415e68..cad14c8 100644 --- a/_site/music/2019/06/17/AMM2M1-release.html +++ b/_site/music/2019/06/17/AMM2M1-release.html @@ -7,16 +7,15 @@ - Evan Pratten - - - - - - + Evan Pratten + + + + + + - @@ -124,13 +123,13 @@ Your browser does not support audio players - - - - - + + + + + - + diff --git a/_site/random/2019/06/18/Blogs-I-Read.html b/_site/random/2019/06/18/Blogs-I-Read.html new file mode 100644 index 0000000..a8c1c26 --- /dev/null +++ b/_site/random/2019/06/18/Blogs-I-Read.html @@ -0,0 +1,146 @@ + + + + + + Evan Pratten + + + + + + + + + + + +
+ + + + + + + + + +
+ + +
+
+
+

Blogs I Read

+
+ +

This is a copy-pastable list of rss feeds I subscribe to:

+ +
https://www.firstinspires.org/robotics/frc/blog-rss
+https://lukesmith.xyz/rss.xml
+https://daniellockyer.com/feed.xml
+http://www.windytan.com/rss.xml
+http://psy-lob-saw.blogspot.com/rss.xml
+https://retrylife.ca/feed.xml
+
+

+
+
+ +
+ + + + +
+ + + + + + + + + + + + + + + + + \ No newline at end of file