Technological God of the Society
Essentially, someone to keep the Tech side of things secure and running smoothly
(Currently split between Chair and TO, because Chair has high aspirations…)
Core Responsibilities
- Managing the technical platforms for the society
- e.g. Discord server, CTF-hosting platforms, (app?)
- Committee Tech Support
- Not the sole tech support for the members, but the primary one :}
Desired Attributes
- To be technically competent when it comes to the tools used by the society
- Discord knowledge for mainaining the main Discord Server
- Knowledge of CTF-hosting platforms for when internal CTF events roll around
- Knowledge regarding exactly how the app works (if we get an app? :D)
- Technical competence when it comes to general full-stack development things
- Will be a useful arsenal to have when it comes to designing and debugging systems for the society
- Low-key, to have the patience to be Tech Support for the Committee :}
- Responsibility to the Members is shared by the whole committee, so TO should ensure that the Committee Members know the basics
- As this will also lighten the load for the TO down-the-line
Committee Connections
Academic Chair: For help with the technical aspects of workshops or talks
CTF Chair: For help with the technical aspects of CTF events
For larger events, the CTF branch of the society comes together to all work on the technical aspects, together, not just the TO by themselves, of course
Puzzlemaster: Some of the PMs puzzles will likely require a technical element to them, it would be nice if the TO could help verify and facilitate the smooth running of these puzzles
Chair: The TO is one of the committee positions directly supervised by the Chair, because TO is an important position to the smooth running of this society (particularly this society)
But also this year (2024-25), the Chair is sharing some of the TO’s work, as the full infrastructure for the Committee and Society have not yet been set up, which needs doing :p
Other: Any CMs are allowed to suggest/write changes for technical platforms that the TO manages, it’s the TOs responsibility to verify them before deploying, however
Notes
- Workload is a lot more variable and just depends on how much technical help is required by the other members of the society
- Ultimately, the forethought and planning for technical queries and requests is the responsibility of the requesting party
- e.g. if the AC requests that the TO produce a test environment for a workshop in 2 days time, the AC can… go away
- However, it is the TOs responsibility to accurately gauge their own abilities and required time
- e.g. if the TO predicts that a job will take x time, but they’ve realised that a bit of CW may take longer than expected, it is the TO’s responsibility to inform the AC, so that appropriate help can be provided to the TO
- Likewise, blowing off jobs cos the TO cba is unnacceptable without good reason
- Such matters should be mediated by the Chair
- If the society’s technical infrastructure is ever to become very complicated, TO may need to be expanded into a Technical Team (worried this may even be necessary in 2024-25, but we’ll see)
- It is the obligation of the previous TO to be there for their successor (in good spirit), so that they aren’t overwhelmed by the sheer scale of things on the first day, and to show them the ropes