If I could compare the capstone project my group has been working on with anything else it would be computer science programs in general. There are moments of feeling incapable followed by breakthroughs, the feeling of being able to conquer any assignment, inevitably leading to more humbling experiences and confusion. Management teams in some fields often strive to create an environment where employees are brought up and knocked back down on repeat to bolster productivity in an otherwise stagnant trade. That technique feels implemented here without the presence of such strict management.
That last line of introduction may have felt like something negative, but that’s not the case here. Throughout this project, we’ve encountered several speedbumps that–following the same lingo–really let the air out of our tires. These issues have proven crucial to understanding a typical project’s ups and downs and helped us find a good direction for our work. Stagnation brought on productivity, ambitious feature creep required simplicity, and unfamiliar problems introduced a new understanding of problem-solving as a team.
The most important takeaway since my last post has been remaining humble and making sacrifices to complete a working program. We’re finally nearing the finish line as our work comes together to form a (mostly) completed project. While we may not have added every ideal feature from our original plan, we undoubtedly will have something useful.
There exists, for the future, something that can be modified to add features we missed out on before. It serves as an excellent example of what can be accomplished as a team and individually for public display with projects helping to catch the eye of a potential employer. Finally, it’s a proven system of experience showing each of us is capable of working in this group setting and coming out the other end with something that works after three quarters together.
Leave a Reply