The term "gweep" (a nerd's nerd) originated at my undergraduate university to describe computer science majors.
When I was an EE major at WPI, the computer science (CS) majors were called "gweeps." At that time, the school had VT100 terminals in either the computer lab or in a few other places. One of those places was in a corner next to the mail boxes. The gweeps were the people at the terminals on Saturday nights,even when we were not in exam perods. People in other departments would walk by the terminals and yell "GWEEEEEEP" with their pitch rising during the Es.
A DEC VT100 terminal.
Did you learn to program on one of these?
As engineers, we've all been called "nerds" or "geeks," but gweeps (or gweepers) are a special breed, kind of people that those who are called nerds think of as nerds. During my undergraduate career, WPI was experimenting with a radically new engineering curriculum where the requirements for graduation were based on projects and one huge engineering exam, not necessarily on academic credits. At the time, you could take any courses you wanted and if you could complete the projects, you could graduate. That's changed. Here's why.
Some students, often CS majors, would take all or nearly all of their technical courses in programming. (We were required to take five related humanities courses and complete a project in that area, a requirement that's still in place.) So, these gweeps knew all about programming, but were so narrow that they often were clueless about how to use their skills to solve problems. It was pretty much programming for programming's sake.
Real gweeps don't smoke. It distracts from the programming experience.
Some EE majors took more than one programming course so they could get a broader perspective and learn how to program computers to solve real problems. But CS majors came out so narrow that the faculty later required students to take a few technical courses outside of their major. Like most EEs, I didn't wait to be told to branch out to other departments because the expected (but not required at the time) physics and chemistry. I took one programming course, FORTRAN, but didn't like it much. Machine shop was much better for me.
One of the great things about starting as an EE is that you can move into programming, but you can also move into mechanical design, optics, semiconductor physics, and host of other areas. Can CS majors do that?
See a related article, Don't major in CS: 5 reasons why, on EDN.