top of page
Mateo Cajiao
PERSONAL PROJECT
Process Taking Action
Steps
From a basic research question to a fully fledged product, I've come a long way with the Personal Project. At first, I had to do all the research regarding my project, which was quite tumultuous, as there was lots to cover. After this, I had to cite my sources (remember to always use MLA8) and then conduct OPVLs on all of them. Once I finished Criteria A, I had to then plan out the criteria/specifications, so that I had a rubric to basically 'grade' myself against, once my product was done. Then came the programming of the bot itself, which was relatively straightforward, since I had already done all the necessary research. Once I was done with it, all I had to do was hand it in and then begin to conduct research (again), but this time, into the effectiveness of my product, whether it met my specs, and how others viewed it; this is all for Criteria D.
Materials
The materials were very straightforward, as coding, from a materialistic perspective, is quite simple; you need a code editor (Visual Studio Code), a CLI (Command Line Interface - included with VS Code), Discord's API (Application Programming Interface) which allows me to access Discord through my bot, as well as send and receive packet requests, and lastly, all the previous knowledge and research from Criteria A.
Obstacles
During the creation of my product, I encountered a few small inconveniences, all being bugs. Bugs can have many causes, but in my case, it was because I either committed errors within my lines of code or because I overlooked certain things, such as the communication parameters between my bot and Discord (through their API). Fixing errors can be extremely frustrating and time-consuming, which is why the more you practice, the better you will get at troubleshooting. The outcome of all the bug squashing was that I became more proficient with my JavaScript skills (Discord.js specifically).
Adjustments
There were a few changes I had to make to my project through its course, such as eliminating some of the exaggerated aspects of it such as how I initially intended to create an external database, storing thousands of common, weak passwords; by doing this, I'd be able to solve the issue explained in the homepage, like 'pA55w0rD'. Therefore, I'd have both a password strength checker based off an algorithm, as well as a plethora of common passwords for my bot to detect and flag as weak. The reason I didn't include this in the final product was that it was far too difficult and time consuming, and was something that would require too much effort for the time frame given (especially during MYP5, a busy year).
bottom of page