/
Term 1 Week 3

Term 1 Week 3

Retro

Reflect on the previous time period

 

Notes

Actionables

 

Notes

Actionables

What was completed?

 Sam:

  • Learnt about Discord.js

  • Built a simple onboarding bot, which included subcommands. The bot can pick from a variety of responses if you run certain commands (for example if you run ‘hello' it might respond with ‘hi’ or ‘hello’ or ‘yo’. This even resulted in the bot responding to itself).

 

Riz:

  • Working on understanding the codebase and javascript discord library.

  • Building a simple bot to get familiar with bot implementation and adding to testing server. Specifically built upon the command implementation to collect a joke from a database and display a random one when called with the slash command.

Yuvi:

  • Looking at current codebase and features

  • Added first testing bot on the testing server

  • Going through Discord JS documentation

 

Emily:

  • Built a simple bot with various features including a cat pic generator, inspiration quote generator and a command that checks if you know your own username

  • Got more familiar with discord.js module and the CSESoc discord-bot codebase

Jane:

  • Became more familiar with the discord.js documentation

  • Had a simple bot and attempting to implement new commands

  • Learned basic html, css and React, working on a mini project with other trainees

 

Jason:

  • Learned some React, ExpressJS

  • Assigned tasks in trainee-1, building todo list app

Harry

  • Got used to the codebase, looked at some of the resources for Discord.js

  • Made a simple command to play a dodgy guessing game

 

 

 

What was done well?

Sam:

  • Found the discord bot relatively simple to set up

 

Riz:

  • Was able to understand the core methods and implementation of a discord bot and its interactions with the discord interface.

  • Template provided assisted in the familiarisation of codebase and file structure.

Yuvi:

  • Environment setup was straightforward enough to start building on features soon

Jane:

  • Setting up the bot was simple

  • The crash course videos were relatively easy to follow

Jason:

  • Following crashcourse was easy

Emily:

  • The environment was setup and a simple bot was not too difficult to build.

Harry:

  • There was good documentation on how to get the environment and bot started up

 

What could have been done better?

Sam:

  • My first test bot wasn’t built using the template, so I ended up building a second one with the template.

Riz:

  • Similarly I went a little to forward in the instruction video for setting up a discord bot and failed to used the template provided but rather started from scratch for initial implementation. Had to again implement using the template.

Harry:

  • Me too^

Yuvi:

  • Discord dev portal doesn’t open for my account on desktop for some reason, known discord bug. Looking into solutions.

Emily:

  • Could have created a more complex bot rather than commands that retrieve something from an API

Jane:

  • Having a deeper understanding of the react task tracker project so that I can apply the knowledge to the mini project for trainees

  • Didn’t use the template at first

 

Planning

Update plans for the future

 

Notes

Actionables

 

Notes

Actionables

Short term goals

(achieve by next retro)

  • Test individual features

Carrot Board - @Samuel Schreyer

Role Feature - @Harry Zhang

Anonymous Message - @Riz Manter

Code Execution - @Yuvraj Singh

Schedule Msg - @Emily Lu @Jane Wang

Medium term goals

(review at next retro)

  • JS-Logging

  • Quiz

  • Games (Takes a long time)

  • Meme of the day/ Meme generation

 

Timeline

(ETA until release, etc)

 Deploy the bot in the testing server by week 6

 @Sanyam Jain

Misc

Random stuff

 

 

 

 

 

 

Related content

UNSW CSESoc