For the past 4 years the CSSS has been a source of friendship and wisdom for me, and thanks to the efforts of past presidents we've flourished into a strong and successful community. It would be my honour to continue those efforts, and if elected here are some plans I have for the coming year.
Hack time failed: let's think about why and do something better. I want to reach out to you to get your take, but this is my tentative idea. I see two problems with hack time as it was implemented. First, it was unstructured, so the benefits were restricted to camaraderie, silence and hardware access. Second, it was at specific times and places without marketing. As a result, basically everybody who showed up was from the common room which means they probably don't have demand for camaraderie or silence. Since it's at specific times, they have very limited time with hardware. Finally, the lack of structure just bores a lot of people.
What I propose is to have a hardware checkout system so you can play with the hardware whenever you like, and structured technical workshops. Classes don't teach a lot of important skills for the software development roles most CS students are after:
- git, CI/CD
- Linux/server administration
The thing is that a lot of students may not even know they need to know these things. We've had git and Linux workshops in the past, so this is doable.
Speaking of jobs, we never have networking events! The earlier students can engage with the jobs available in the lower mainland, the better they'll be able to prepare themselves for the market. Nothing sucks more than looking for co-op and realizing you don't have what businesses are looking for. I have some industry connections, and I plan on making more, so I can hopefully organize tours of offices and socials at SFU.
Finally, I also want to explore ways of documenting the knowledge and advice that floats around the common room so that CS students can refer to it. The CSSS site is underutilized, and that's a shame.
Thanks for your consideration!