Robotics: An alternative to Prime Number Syndrome?

[JesseK]

I started at GT as a Computer Engineer before I realised that it was like the hardware version of Computer Science. 2nd and 3rd year classes are particularly dull, and the interactive (and freakin HARD) labs don't start until 4th year. In my 3rd year I swapped to EE since I wanted a control systems-oriented engineering degree and have never looked back. I even took some of the embedded systems classes required for CE's so I still got both worlds. BSEE '05.

That said, you probably know that control systems require tons of algorithmic math, and I am a Math Freak. While this news is great in some respects, I think that programming math algorithms for a bit really helps programmers understand how to take theory to code. Robotics helps them take some design that has specific requirements to code. If you've ever done research that requires programming, often times you'll find that there is a HUGE difference between the two. So long as they keep (even the intro) classes to the former, this is a great idea.

How else would anyone be inspired to take a mathematical algorithm (such as Collatz Theorem), program it and graph it for fun, then try to reverse, sideways, and upside down engineer it to figure out how to use a pattern found in a "pretty picture" created from the graphs? That is true Computer Science. Otherwise you're simply repeating something that someone else came up with.

[Richard Wallace]

Originally Posted by JesseK

... BSEE '05.

GT EE = helluvan engineer.

Originally Posted by JesseK

That said, you probably know that control systems require tons of algorithmic math, and I am a Math Freak.

I do know that. Controls was one of my coursework areas for the MS and PhD, and there is a chapter on controls in my dissertation.

Math freaks rule.

Originally Posted by JesseK

This is a wrong step if they move the entire CS program in that direction. It will turn the science of programming into a mere programming job and leave all of the design work to an engineer that might not know of all the tools available in the field.

I agree -- and so did people who ran the EE department at GT when I was there. I imagine they still feel that way today, and probably there are similar feelings in the CS department. I hope the robotics course is aimed at 1st and 2nd year students, as a way to inspire them into the field by showing the kind of project work that is possible.

Inspiration is the starting point, but it won't replace the hard work required to get the skills needed to attack the details of an engineering challenge.