Tuesday, July 26, 2005

Capstone.. what I've learned so far

This capstone project has been fun.

I think the electrical engineering department has it right: you should have build a physical prototype.

The other departments (mechanical, civil, industrial), your project doesn't have to be (ie it can be theory/calculations/software simulation only.).
But then you don't experience all the fun of "implementation" issues.

Anyhoo, I've learned that:

a) Writing proposals such that you promise to get done the minimal amount is a good idea

b) Motorola microcontrollers, although used extensively for teaching purposes, are HORRIBLY designed. Must be those damn Japanese. The limitations we are having are mind boggling (for example, the timer system, you CANNOT reset the timer. Period. Essentially, something that should be realitively easily to implement in assembly becomes more difficult you have to work your way around it.

c) Then, according to b), in retrospect, full requirements for the timing algorithm should have been sketched out beforehand (ie. need to reset the timer), and then selecting the microcontroller based on that :)

d) And so the saying goes, if it works on paper/software, it don't mean shit. Really hits home ;)

e) The simplest idea is often the best. KISS :)

But hey.. that's what the project is for. So you get a feel for these things :)


At 10:19 p.m., Blogger Zutroy said...

The whole reason you have to do Capstone is to learn these things before you screw up in the real world :)

I'll tell you one thing, co-op really gives you a taste of what office politics can be like.

At 5:31 p.m., Blogger Medieval said...

Yep, regardless of where you work, there is politics.

Some places have more, some have less, but it's always there.

It all depends on the politics you prefer, I guess :)


Post a Comment

<< Home