We’re nearing the end of the line. Only a handful of weeks left, but it feels like there’s still so much to do. It’s interesting that this last section of the Capstone project is only 2 credits, because with all the testing that needs to be done, it feels like there should be more time allocated to it. I’m not complaining, really – just saying.
One of the interesting things that I’ve noticed with the project is that I’ve gotten kind of get attached to the outcome more than others. Everyone’s different of course, but I find myself wanting to keep adding and adding to it, while some team members are okay with where it’s at. I don’t think there’s a better or worse way to look at it, and we all have our own perspectives on what this project means.
One other part of doing a Capstone project that I’m curious is how it goes with other teams is how many want to actually make their project a real app/product. I’ve heard that it’s happened, but I wonder what percentage of school projects – not just at OSU, but all university projects – get made into actual products. We hear the big success stories, of course, but I wonder if there’s a bunch of software out there that people don’t realize was started as a student project.
Leave a Reply