Friday, November 19, 2010
Tuesday, November 9, 2010
Ideas
So... totally forgot to do this. I had a calc midterm last night so I checked out mentally after that and forgot about this. But anyways, here are my ideas:
1) So I have the passion of helping those in need, so an idea that comes to mind is employing people in developing countries while giving them either water or shelter. I don;t know exactly, but even setting up small scale dams or wind turbines (anything that can employ a small number of people) as well as building electricity powered shelters (get the electricity from the dam or turbnines). Even 1 shelter for a community could help alot of people who struggle to have a warm place to sleep or anything.
There you go. That was on the fly. Peace.
Andrew
1) So I have the passion of helping those in need, so an idea that comes to mind is employing people in developing countries while giving them either water or shelter. I don;t know exactly, but even setting up small scale dams or wind turbines (anything that can employ a small number of people) as well as building electricity powered shelters (get the electricity from the dam or turbnines). Even 1 shelter for a community could help alot of people who struggle to have a warm place to sleep or anything.
There you go. That was on the fly. Peace.
Andrew
Friday, November 5, 2010
iEFX System
http://www.scribd.com/doc/41213020
Alright so first off, I feel like I haven't written a blog in ages. Either that's true, or I have become addicted and am on withdrawal. Okay so there's my little iEFX system that I drew and scanned in and all that. One thing about systems is that they can either be very objective and numerical or very subjective and descriptive. In my opinion, the iEFX system is subjective (for the most part) and can be looked at from various angles. Basically, I'm justifying any possible errors that my drawing and analysis has (but I didn't just tell you that).
Okay so inputs: obviously we (engineering freshman) are the main inputs into iEFX. Another way you could look at it is engineering freshman, iCOAs, and all the leaders are the inputs. In my opinion, the iCOAs and leaders are already a part of iEFX and so are not an input.
Process: So the process is probably the most complex part of the iEFX system. There are tiny processes that go on behind the scenes and there are the main stream processes that we participate in every day. Technically, the list could be endless; I only put 7 that first came to mind and that could reasonably fit in my little box. Some of the mainstream ones, obviously, are the classes that we are introduced to (Eng 198 and all those other Eng ones that we were told during our lab the other day), our iTeams and all the activities we do with them, and the seminars and workshops that we are invited to. In a very general sense, the process of iEFX is the learning and growing that we all do throughout our time in iEFX.
As for the outputs, they're the the actions that us engineers take. One big one is the iEXPO. There, we see all the smaller activities that the iTeams did throughout the year. Some smaller things that come out of the system are the friendships and, although a non-concrete thing, the knowledge and understanding that us engineers gain. Obviously, there are endless things that could come out of iEFX, but those are the typical ones.
Last, but not least, is the feedback. Feedback is an extremely important part of a system in that it makes it more efficient as time goes on. With iEFX only being in it's second year, it (clearly) has a lot of kinks to remove from and add to the system. The day to day complaints from the students are some of the feedback iEFX will get. More formally, end-of-the-year surveys will provide a solid form of feedback. Non-written forms of feedback include grades (if you compare those of iEFX students to those of regular engineering students). Comparing grades could theoretically show if iEFX students are learning at a higher level or if the ideas taught to them are making any impact on them. Another non-numerical thing could be whether or not the iTeams stay together or if friendships last. Once again, feedback can come in many forms, but all feedback, whether positive or negative, will help the iEFX system adapt to make the outputs of the system become better and last longer.
I'm blogged out. I was too lazy to make a video for this one, so look for that next week. Anyways, time to go.
Stay Classy,
Andrew
Alright so first off, I feel like I haven't written a blog in ages. Either that's true, or I have become addicted and am on withdrawal. Okay so there's my little iEFX system that I drew and scanned in and all that. One thing about systems is that they can either be very objective and numerical or very subjective and descriptive. In my opinion, the iEFX system is subjective (for the most part) and can be looked at from various angles. Basically, I'm justifying any possible errors that my drawing and analysis has (but I didn't just tell you that).
Okay so inputs: obviously we (engineering freshman) are the main inputs into iEFX. Another way you could look at it is engineering freshman, iCOAs, and all the leaders are the inputs. In my opinion, the iCOAs and leaders are already a part of iEFX and so are not an input.
Process: So the process is probably the most complex part of the iEFX system. There are tiny processes that go on behind the scenes and there are the main stream processes that we participate in every day. Technically, the list could be endless; I only put 7 that first came to mind and that could reasonably fit in my little box. Some of the mainstream ones, obviously, are the classes that we are introduced to (Eng 198 and all those other Eng ones that we were told during our lab the other day), our iTeams and all the activities we do with them, and the seminars and workshops that we are invited to. In a very general sense, the process of iEFX is the learning and growing that we all do throughout our time in iEFX.
As for the outputs, they're the the actions that us engineers take. One big one is the iEXPO. There, we see all the smaller activities that the iTeams did throughout the year. Some smaller things that come out of the system are the friendships and, although a non-concrete thing, the knowledge and understanding that us engineers gain. Obviously, there are endless things that could come out of iEFX, but those are the typical ones.
Last, but not least, is the feedback. Feedback is an extremely important part of a system in that it makes it more efficient as time goes on. With iEFX only being in it's second year, it (clearly) has a lot of kinks to remove from and add to the system. The day to day complaints from the students are some of the feedback iEFX will get. More formally, end-of-the-year surveys will provide a solid form of feedback. Non-written forms of feedback include grades (if you compare those of iEFX students to those of regular engineering students). Comparing grades could theoretically show if iEFX students are learning at a higher level or if the ideas taught to them are making any impact on them. Another non-numerical thing could be whether or not the iTeams stay together or if friendships last. Once again, feedback can come in many forms, but all feedback, whether positive or negative, will help the iEFX system adapt to make the outputs of the system become better and last longer.
I'm blogged out. I was too lazy to make a video for this one, so look for that next week. Anyways, time to go.
Stay Classy,
Andrew
Subscribe to:
Comments (Atom)