working on wrap-up

_drafts/2021-12-31-Year-wrapup.md

@@ -0,0 +1,53 @@
+---
+layout: page
+title:  "2020 Wrap-Up"
+description: "I wrote a lot of code this year. This post looks back on it all"
+date:   2020-12-31 10:00:00 
+written: 2020-12-09
+tags: writeup review projects
+excerpt: >-
+    2020 has been my most productive year so far in terms of software development. This post looks back at the year
+redirect_from: 
+ - /post/g494l5j3/
+ - /g494l5j3/
+---
+
+*So, whats up with 2020?*. For readers who do not know me personally, here is a quick overview:
+
+ - I made over 6000 commits to over 100 open source projects
+ - I passed both 300 and 400 GitHub repositories (and am on track to pass 500 any second)
+ - I lead software development at [Raider Robotics](https://github.com/frc5024) for my third year
+ - I published my largest open source project
+ - I got to do a summer internship at [Industrial Brothers](), working on pipeline software
+ - This website now gets around 300 readers per month (wow!)
+
+## Robotics
+
+This year, I packed a lot of robotics work into a small amount of time. Starting in the first week of January, through the beginning of March, I worked with close to 100 other highschool students at *Raider Robotics* to develop our most successful robot of recent time: [Darth Raider](https://www.thebluealliance.com/team/5024/2020). 
+
+<div class="center" markdown="1">
+<iframe width="443" height="249" 
+src="https://www.youtube.com/embed/iF-p-rTo8Xk" frameborder="0" 
+allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen>
+</iframe>
+
+*The full source code and tooling for this robot is [public](https://github.com/frc5024/InfiniteRecharge)*
+</div>
+
+This robot brought us all the way to the finals of our only competition this year (before the world got shut down). It was only in the finals that we finally lost our winning streak (and strong #1 place) due to some questionable scoring and a broken component on one of our teammate's robots.
+
+On the software side of this machine, [I pushed to switch the core development language over to Java](/blog/2019/06/24/languagehunt2), which went very well, and the team seems to be on track to stay with this new language and toolset for the forseeable future. This year, we pushed very hard towards our goal of letting software handle as much of the "hard work" of operation as possible. In previous years, our robots mainly acted as stupidly expensive RC cars with custom controls, but this year, we wanted to offload tasks prone to human error to computers. 
+
+We were able to design a fully autonomous shooting system using high-speed computer vision, real-time path planning, and ball trajectory models to allow our operators to make the robot score game pieces by pressing and holding a single button. On top of this scoring system, *Darth Raider* featured fully autonomous and real-time-error-correcting spatial navigation, allowing us to input a list of goal coordinates for the robot to navigate to efficiently. The final large autonomously controlled system of this robot was known as the "hopper"; a long tunnel for storing and stacking balls. This system was 100% software controlled, and made use of an amazing predictive sorting system developed by @rsninja722 that would perfectly align balls as they were fed in to the robot. Below is a clip taken from semi-finals where we wrote an experimental system that allowed us to essentially use two completely separate robots as one, effectively doubling our gamepiece storage capacity from our max 4 balls to 7. (Big thanks to the [Falcons](https://www.thebluealliance.com/team/5032) for letting us subject them to this experiment.)
+
+<div class="center" markdown="1">
+![Two-robot autonomous scoring system](/assets/images/buddy-auto.gif)
+</div>
+
+
+For a few months after we finished competing, I went on to publish my largest open source project to date: [Lib5K](https://github.com/frc5024/Lib5k). 
+
+> Lib5K is the software library that powers the Raider Robotics control system. It originally started as a summer project by @ewpratten back in the 2018 offseason. [...] Lib5K development really picked up during summer 2019, where the library (and all of Raider Robotics development) switched from C++ to Java Native. This switch also brought a lot of the core features to Lib5K, and the whole team got involved in development during the 2020 season. \[source: [Lib5K Wiki](https://cs.5024.ca/lib5k/)]
+
+My goal with Lib5K was to design a way for myself to pass along my knowledge and learnings to future team members in an easy-to-digest way. According to internal team productivity metrics, I have made around 650,000 edits to this library, making it my most contributed-to project ever.
+

_posts/2019-06-24-LanguageHunt2.md

@@ -6,7 +6,7 @@ date:   2019-06-24 21:36:00
 tags: frc
 ---
 
-This is a very short post, just to explain the result of [The language Hunt](/frc/2019/04/30/FRC-Languages.html).
+This is a very short post, just to explain the result of [The language Hunt](/blog/2019/04/30/frc-languages).
 
 ## Our choice
 For our upcoming 2020 season and for the forseeable future, we have chosen Java as our programming language for direct hardware interfacing, and Python for networking, vision, and other smaller tasks.

_sass/site/page.scss

@@ -125,4 +125,24 @@ table,
     .maybe-date {
         display: none;
     }
+}
+
+blockquote {
+    // background: #f9f9f9;
+    border-left: 10px solid rgb(77, 77, 77);
+    margin: 1.5em 10px;
+    padding: 0.5em 10px;
+}
+
+blockquote:before {
+    color: #ccc;
+    font-size: 4em;
+    line-height: 0.1em;
+    margin-right: 0.25em;
+    vertical-align: -0.4em;
+}
+
+blockquote p {
+    display: inline;
+    font-style: italic;
 }