diff options
| -rw-r--r-- | reflection | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/reflection b/reflection new file mode 100644 index 0000000..c62c5c4 --- /dev/null +++ b/reflection @@ -0,0 +1,15 @@ +When I started this project, I wasn't exactly sure where I wanted to take it, I knew I wanted to work on something related to free software During my initial research I was focusing on looking at specific licenses such as MIT, GPL, and BSD; however I found that there wasn't very much to compare to on the proprietary side of things, as there is no set non-free license, most non-free programs have a license specific to it. Due to this I decided to swing the research I had done towards something with a wider scope, which was why is free software preferred in specific fields, I hadn't decided on which at the time. After more research I thought to link it to the things that I personally are passion in, as this would be easier to keep motivation. It is through this that I came to the title of, why is free software preferred in the privacy and development spaces. + +Throughout the project I tried to look at things objectively, if i felt a section didn't work I removed it, and rewrote it, I didn't want to get stuck in a loop of trying to fix something that was never very good to begin with. I think at points this effected me negatively as I cut work that could have been kept, but overall I believe it saved me time, and thus allowed me to focus on what mattered in my project. + +During this project, I decided to pick up new software skills to help me manage my time and work. This was by far the most helpful thing I did, as without it, my project would have never been finished. Some of the tools I used, I had tried before, however never on something so large, this really pushed me to learn them well. The main tools I used were git, org mode and latex. Git acted as a diary via its log feature and to keep backups of my project via its ability to store multiple copies of something remotely. I found it to be very helpful overall as I was already using it to manage programing projects, I felt familiar enough for it not to be confusing; It removed my need to worry about having a version at home, and another in class, and updating my git log is already a activity engraved in my mind a s a software developer. I also used Emacs' org mode to manage my research and other important information, this is a note taking format that allows for easy to manage and search through notes. I used it to store all my research and any notes from my supervisor. And finally I used latex to write my essay and create my presentation slides, it was by far the most helpful of the tools I used. I found it kept my writing focused on the content and not the formatting and citations, as it handled all of that for me. + +If I were to do a project like this again, I'd like to have a wider topic field, I really enjoyed researching new areas in a field I enjoy, and I'd love to expand that even further. I'd keep most of my management skills the same however as generally I thought they all worked well, as I was consistently ahead of my timetable. + +As previously mentioned, I really enjoyed learning about sections of free software that I didn't already know about. I spend so much time learning about and making free software, but I often realised I didn't know about the history and foundation of its existence. For me this project was a way to expand my knowledge outside of practical usage and into history, reasoning, and ethical factors. + +If I were to give advice to someone undergoing a similar project, my best take away is sectioning work. Breaking problems down into small manageable chunks made everything possible for me. I work on a very tight schedule due to a number of factors and often only have free time in small 20-30 minute blocks, so breaking problems down into things I could complete in this time, made everything leaps and bounds easier. I decided to make my timetable based on the sections in my project, this helped me keep an end in site for my project, as I could see exactly when it would be done, and how much work was needed. + +A final point I'd make if I did this again, would be to ensure counter arguments are made. An argument without a counter point, isn't a very good argument. I didn't fully realise this towards the end of the project, which meant I needed to go back and add counter points, which pushed me close to the word limit. + +Overall however, I am very happy with what I have produced, I think it has proven my ability to manage and create like projects. |