Friday, September 24, 2010

Communication in Engineering

Communication in engineering is crucial between team members and other scholars in the sense that it will allow for greater accomplishments and a merging of ideas.

Considering written communication alone, engineers can made great use of both free writing and directed writing, using them as a tool to improve and expand their projects. For example, free writing often allows for more thought progression as the writer is not as concerned with how his ideas are being presented but more so what the ideas actually are- the reflection on which often produces new ideas or a clearer understanding of existing ones. These freely written forms can also be read by other team members or scholars, who can add insight and possibly further the project even more.

Directed writing, on the other hand, focuses more on the presentation once the idea is solidified and perfected. Writing in this manner is used as a practical way of communication, written in a format that is common and easily followed. In engineering this would often mean writing in a very structured manner and language that eliminates any ambiguities as to the idea and how it works.

It seems to me that free writing fosters thought a great deal more since the writer is not forced into a format and is allowed to focus on the actual subject of the paper and the point that he or she is conveying.

This idea can be transfered to verbal communication as well. It is the same concept as talking freely (bouncing ideas off of teammates, etc) vs giving an oral presentation on the topic. When talking freely with teammates or scholars in the area, the engineer is more open-minded and thoughtful about the topic rather than when he or she is speaking in a more tense, presentation atmosphere.

In essence, communication of both types are needed to make a project understood and widespread but it seems that free-writing or freely talking is present in the developing stages while directed writing/verbal presentations are used in the final stages of the project, once everything is clear and finalized.

Friday, September 17, 2010

Networking/ Taking Initiative

As I see it, networking is all about building strong connections and relationships that will help both parties in their future goals. With this thought, I decided to start building a network to help me reach my current goal of switching into Aerospace Engineering.

I applied to the university at the last minute and although I knew I was interested in engineering, I did not spend time deciding exactly what I wanted to do. Under the circumstances and time constraints, I applied to General Engineering. However, as I thought my interests over in the summer and during the beginning of the year, I realized that aerospace engineering is what has been drawing me into engineering.

It has become my goal to switch into aerospace engineering and although I could not during summer registration because the major was closed, I wish to complete this transfer as quickly as possible. I began networking with upperclassmen from aerospace engineering, learning about their classes, professors, projects and also gaining tips as to who to talk to about switching majors. I spoke to my chief advisor about switching majors, even during summer registration. With the communication started, getting an approval and recommendation for transferring majors should be a simpler process as the advisors are already familiar with my situation.

I am not only interested in officially switching majors, however. I also wanted to get involved in the aerospace community, gaining connections for the future, possibly internship opportunities and learning more about the subject while doing so. This week I came upon a perfect opportunity to start this network within the community and signed up for the Space Vision conference that will be taking place at U of I in November. I feel that I could learn a great deal about space technology as well as greatly expand my network for the future by taking part in this conference.

Wednesday, September 1, 2010

Missing Basics and Mini-Action Plans

I apologize for writing this post late.

About the missing basics concept, I feel that those basics are essential in many subjects (not only engineering). However, I do not necessarily believe that these skills are missing. These "missing basics" seem like topics not explicitly covered in a strictly engineering curriculum but still present as skills in the students. Many of these concepts such as decomposing design problems, visualizing solutions, generating ideas and asking questions seem natural in the process of engineering and that they do not necessarily have to be explicitly stated to exist. Many people will decompose problems whether they do so purposefully or automatically.

I do not believe the basics are really missing, they are just not needed to be shown explicitly in many situations or environments the students are in. However they are still being practiced through the many tasks students complete. It seems to me that only basic that may need to be practiced more in a classroom setting would be communication of the ideas. A person cannot force an adult student (already conditioned to think a certain way) to have good ideas or think of good questions. These have to come from the student and some have more ideas than others. The only thing that seems reasonable to practice is making the student comfortable and confident enough to verbalize his or her ideas and questions. Even this seems unlikely to change dramatically as it would require changing the person's character if he or she was less confident before but it seems reasonable that confidence and communication skills can be developed to some level. The other skills, however, seem innate or conditioned early on in the way a person thinks.

My own plan for developing my character and skills this semester include improving my vocabulary (which I find to be a weakness), communicating my ideas more often in class and learning Python (a programming language). To improve my vocabulary I will read a book every two weeks, as reading is a very good way to expand your vocabulary. To achieve my second goal, I will speak at least once in every discussion class. The vocabulary from my first plan will also help in this goal since it will give me a better means of communicating exactly what I want to convey. To learn Python, I will read a chapter or two of the Python tutorial from MIT OpenCourseWare a week, while working on small programming projects to help me practice what I learn.