"There was a time when working part time over the summer would be enough to pay ALL college expenses"
I only started college in 1981, so maybe it was before my time. But that sure wasn't the case then.
College is essentially a full-time job for 9 months a year in the US. If there was ever a time when a part time job for 3 months a year covered a full time existence for 9 months, well, I sure missed out on that era. Perhaps that was part of the mythical 1950's that everyone seems to pine for, even though if you were 15 in 1955 you'd probably be 71 now - meaning the vast majority of the population wasn't around in the "good old days" of being terrified of nuclear war, the Communist Menace, etc.
I wonder if
I'd say you nudge him out of delivering code if you can, if your team can handle the load, by suggesting you can take that project on, in order to free him up for more strategic work - like vendor evaluation, training/skills development, a standards/process review, or whatever. Praise him when possible for anything he does that's NOT coding. Send notes to him and copy his boss that his standards review was excellent and you really appreciate his taking the managerial approach to making things better. Build a pattern of rewards for non-coding efforts. If that's not possible, or he won't give it up, then either rewrite his code before it hits production, (you will eventually anyway), or switch teams. That one's rough!
"In order to make an apple pie from scratch, you must first create the universe." -- Carl Sagan, Cosmos