# 67400A is ramping up

currently @ a Robotics Club meeting & our team is getting ready for the new VEX season dropping tomorrow -- drafting up drivetrains, vacuuming the field, clearing off the builders' desk, etc. i get the easy job of typing a blurb for today into a terminal & people think that I am doing a Lot Of Work. yay manual labor

can't tear apart our High Stakes bot yet b/c we're gonna show it off on the 14th, but after that it's free game -- brain & motors will be stripped for the new robot

it looks like we're either settling on an H or X drive -- *super* excited to write code for that (NOT!)

also, we are gonna need a better engineering notebook for this season and a git repository to store our code in. the last engineering notebook was severely lacking in hardware+software design choices -- emphasis on software -- and the last ""repository"" was downright horrid. i'm hoping the district will just give us Github and VSCode, i have a few issues that need to be addressed by IT:
* ssh doesn't work @ STPSB -- port 22 is blocked
	literally typing this from a web terminal @ cockpit.hackclub.app
	websocat would work fine though, but i'd have to write a ~/.ssh/config...
* github is blocked via DNS rules
	really annoying. people love to see a commit history and who doesn't want to put "Programmer of 67400A" on their resume? it teaches kids how to write pull requests maybe!

i can run goodies @ \*.hackclub.app though -- there's webmail at roundcube.hackclub.app, git at git.hackclub.app, a terminal at cockpit.hackclub.app, etc

worst case, i will just onboard everybody onto Nest/hackclub.app & run a git repository for 67400A @ git.hackclub.app -- maybe write a powershell script to install PortableGit, websocat, pwsh dotfiles, etc onto windows PCs

TODO: look at purdue's VEX engineering notebook

RIP Class of 2025