5 ms·
My last semester of college, our capstone course saw me at the head of a team of 5 CS students building a video game. Some of the other teams frequently pulled
by bjhoops1 14y ago
My last semester of college, our capstone course saw me at the head of a team of 5 CS students building a video game. Some of the other teams frequently pulled all-nighters trying to meet the course's ambitious deadline, but the whole semester my team and I never did need to work through the night. We ended up doing better than most teams, too. In fact, the team that "won" spent even fewer hours working than we did.
Anecdotal, to be sure, but I found the inverse relationship between hours worked and quality of product quite interesting.
- tomsthumb 14y agoIntensity is certainly important and you can lose that if you push too much for too long. This entirely anecdotal, but I probably wouldn't have graduated with if it weren't for the solutions i 'worked out' during naps. Maybe there's also something to be said for working while not working, not to be too round about.
- bjhoops1 14y agoAnd don't forget in the shower! If I hadn't taken a break during which it occurred to me that I was doing it all wrong, there are problems I'd still be working on!
- robryan 14y agoIt might also have been that some groups were coming from further behind. They might have to first learn how to do something in their game then hack up an average first go which works but will need to be refactored later. Another team with more experience might be able to do the same thing straight away and write it in an extensible way.