He was on to something, of course. But I'd already known that I march to the beat of my own drum.
He was on to something, of course. But I'd already known that I march to the beat of my own drum.
I hit that same crisis my sophomore-junior years of college, but powered through it and finally learned the skill of hard work (which most other students had already mastered by high school).
I am going through the same thing, except I was in a hard high school program but ended up in a university with an easy Comp Sci program. I am a senior, and the graduate class I am taking this semester is the first time I have been mentally challenged by the Comp Sci department. Because of this, I tend to "give up" easily in other things that I am interested in but are harder (mathematics), or I am not motivated to build apps for fun and portfolio, even though the ideas and the languages come easy to me.
Some of my best successes have come from that, and from seeking out other areas in the company where people were doing that. HR was laboriously manually retyping and reformatting job listings although they were using a system with an RSS feed that could pull them in automatically. A half hour (or less) of coding permanently eliminated one of their daily drudge tasks so that they could focus on other things. No one asked me to do it because no one ever even thought of it, but they loved it.
Sometimes it's not worth automating or simplifying something, but it's usually worth considering or trying. Degreed people seem to have a 'this is the way I was taught' or 'this is the way it's always been done' mentality. That's not the way to innovation and big victories.
Degreed coworkers are great for quality control though - meticulous code reviews. And they seem to be usually better at organizing/planning (although not always as good at dealing with unplanned events).
Best is a mix of people that work well together despite their differences.