A course blog for ENE 502, a graduate course held in the School of Engineering Education at Purdue University.
Saturday, October 16, 2010
What is engineering?, updated from 87 to 118 words.
Friday, October 15, 2010
Outsiders’ approach and their interesting viewpoints
Thursday, October 14, 2010
Put the Lawson & Dorst chapter on Blackboard
what is engineering?
Purdue's Lack of a School of Music
He was busy, but was able to quickly answer my question. "Why doesn't Purdue have a school of music?" I asked. He responded "I don't know exactly, but it has to due with the fact that it is a land grant institution and IU already had a school of music at the time of its founding." I replied, "Did John Purdue establish any requirements when he gave his initial donation prohibiting a school of music?" Jay's response: "no, it was nothing like that."
So there's an argument from authority. But that's hardly good enough, so I went digging in an old book that I bought a while back. It's out of print (though apparently the Purdue library system has it online). The book is called "Century and Beyond: The History of Purdue University". It's a good book and I encourage anyone planning to stick around here for a while to read it.
On page 29 you can find the letter that John Purdue wrote to the Governor of Indiana detailing the conditions associated with his donation. I've reproduced it below:
To His Excellency Conrad Baker, Governor of Indiana:
Sir --
As the General Assembly, at its present session, will doubtless be called upon to consider the questions relating to the establishment and location of the Agricultural College, contemplated by the act of Congress of July 2, 1862, I desire to avail myself of the opportunity to render a testimonial to the county in which I have spent thirty years of the ripeness of my life, and also to manifest my interest in the cause of collegiate education, by offering (as I now do) through your Excellency to the State of Indiana, to donate the sum of one hundred and fifty thousand dollars for the use of such college, provided the General Assembly will, by law, secure me in the following conditions:
First. Locate the said college at such point in Tippecanoe County as may be decided upon by a majority of the present Board of Trustees of the Indiana Agricultural College, to whom I be added as a member.
Second. Name the Institution by an irrepealable law "Purdue University".
Third. Provide that I be a member of the Board of Trustees having control of said institution, and should I cease to be such, I be retained as a advisory member thereof, and have visitorial power over the University during my lifetime.
Upon these conditions I offer this donation, which I agree to pay in yearly installments of $15,000 until the full sum of $150,000 is paid; and I am prepared to render my obligations accordingly as may be required.
I will thank you to present my offer to the Houses of the General Assembly for their consideration.
Very respectfully yours,
John Purdue
April 15, 1869
So to clear up any ambiguities, the fact that Purdue University does not have a school of music really has nothing to do with John Purdue. The exact details are still unclear to me, and I spent a little time digging around trying to find Purdue's actual charter with no success.
My understanding is that because IU predates Purdue (and the Morrill Act) it was a more traditional liberal arts college, representative of post-secondary education at the time. When the Morrill Act was passed the Indiana legislature leveraged it to create an Agriculture/Mechanical (Engineering) college – Purdue – and in the process wanted to avoid duplicating programs that already existed at the other state institution. That is why, for instance, IU has a medical program and Purdue does not. Purdue has a vet med program, and IU does not. IU has a school of music, and Purdue does not (although you can minor in music here). As time progresses we can see some duplication of programs between the two universities, but that is probably to be expected as the enrollment increases. This is simply my understanding, I haven't put forth the effort to find any citations to support my claims.
That said, my main goal with this post is to help prevent the spread of misinformation. I hope that it is clear that Purdue's lack of a school of music has nothing to do with John Purdue.
If someone happens to have more information regarding this particular historical oddity I would be very, very interested in hearing it. Thanks!
Spirit of the Land Grant Colleges
Here's information about the mural: http://www.lib.purdue.edu/hsse/infopages/news/spiritlandgrant.html
Here's the mural: http://www.lib.purdue.edu/hsse/infopages/news/spiritmural.html
Thoughts on "Re-engineering"
At times the paper seemed as though it was arguing that engineers should be engaged in more practical engineering, where practical is defined as going out and actually building something. I think we are long past that point in our history. Engineers no longer build things, they design them. Other people more skilled in construction and (generally) less educated are responsible for taking the schematics that the engineer architected and turning them into reality.
In particular a few quotes intrigued me. I really liked this quote:
" 'This is a book you can read without the use of the calculus.' If you're going to take the calculus out of engineering, you are going to destroy engineering."
I agree with that quote wholeheartedly.
Another quote which was intriguing, but that I disagree with is this:
"The tendency [of research] seemed to be toward such far-out matters as 'a theoretical study of the scattering of electrical waves by perfectly reflecting bodies...'" He
added, "when ... the engineering editor tried to get pictures to illustrate reports on research in progress, he was sometimes told there was nothing to photograph unless he was willing to photograph an equation."
The author seems to be implying that because there were only equations to take a picture of, what was being done must be so "far-out" as to be pure research and totally impractical. We can walk down to the Birck Nanotechnology Center on probably any day of the week, and the people there will be submerged in an ocean of models and equations. A lot of them will be accounting for quantum mechanical effects and other things happening at the atomic and subatomic levels. Particularly when dealing with the subatomic level, you're going to have a really hard time getting any pictures.
Yet, these models are used to guide the creation of new transistors and other solid state devices. There's nothing impractical at all about what is being done here.
Maybe my department is just so far along in this "re-engineering" process that I already reaped its benefits. I think that's probably unlikely, however. The fact of the matter is that we're at a point where a large part of engineering is engineering science, not just because that is what is being taught in colleges but also because that is what is being used in practice. It is for the better that we can model things before we build them.
Week 8, reflections on readings. History of Eng.Ed.
1. People always were dissatisfied with the quality of Engineering Education and always complained that it does not correspond with “the real world” needs.
2. In past , Engineering Education was orientated towards development of practical skills with minimal focus on science and fundamental theoretical knowledge. Later (including present time), people complain that Eng. Ed. is too scientifically directed and does not provide appropriate practical skills.
3. Since the WW2, and up till now, the Government money (and the fights between schools to get this funding) always was a significant factor, which influenced on the development of Engineering Education.
In the second article (for this week) Dorst tried: (1) to identify what is design and (2) to establish the methodology of this process. He argues that the very first attempts to find out how a problem-solver makes decisions came from 1960-1970, when the idea of artificial intelligence was very popular. Dorst argued with Simon’s theory about the boundaries between well-defined and ill defined problems and their roles in problem-solving process. It was interesting article with many different perspectives on design, but in general, the author concluded that design process is still unknown, and many factors may influence on designer’s decisions: “The design is a revolution of paradoxes between discourses in a design situation” (p.17).
This is not too long posting, see you all in class.
Identity issues and Genetic predispositions
I shift to observe how this is happening to engineering education. Do we fit into engineering or do we fit into education? Are we taking pieces of both because we are a grafted newborn? Are we creating our own space? If we are creating our own space, and we see how others have evolved, do we do it the same way and if we do not, then doing it a new way is still doing it some way. That way is responding to a previously established way by either agreeing with it or disagreeing and doing something else (opposite, nuanced, etc.)...but possibly in the same manner. Most of our movements are routines we cannot actually avoid...but uber-reflection has potential to do something different in the space afforded to us by others. So
Wednesday, October 13, 2010
Down the zigzag path to progress
Tuesday, October 12, 2010
Engineering and Engieering Profession
I didn't know "engineering" can be so broad, until:
- At the beginning monologue of the movie My Sister's Keeper (in this movie, a 13-year-old girl Anna has an older sister Kate who suffers from leukemia. Anna was born to be a perfect donor match to help save Kate's life), Anna said: Most babies are accidents, not me, I was engineered, born to save my sister's life. I appreciate a lot the usage of "engineered" here, better than "conceived" which is widely used in introductory literature of this movie and the novel it based on. Because "conceive" is "to take into one's mind" or "to form a conception of "--maybe--by accident or unconsciously, but it reveals here that "engineer" involves doing something on certain purpose.
- I saw an artificial crystal necklace at the Art Fair. The artist put certain materials into certain machine (something like high-temperature oven), and the materials will grow themselves into artificial crystal with beautiful patterns inside. Somebody said the crystal is engineered. Although the colors and materials used by the artists do set some constraints, the way the pattern grows are mostly random, thus we can see here the word "engineer" includes uncertain and uncontrollable factors.
- Koen(2003) says "To be human is to be an engineer".
The advantage is that this broad character of engineering can be used into publicity, to persuade people that engineering is relevant to their daily life, and to encourage them to engaged in engineering, because it's easy, and everybody do it everyday. It's not like science and art that only belong to those gifted people who is somehow "geeky", it belongs to everybody.
However, the disadvantage is more obvious. When the category of "engineering" is broad enough to include everybody, everybody loses their identity as engineer (Pawley, 2009). So I see it's necessary to do a boundary-drawing(Gieryn, 1999) work here, to differentiate "engineering" and "to be an engineer (professional engineer)". Engineering can be very broad as Koen describes, but to be a professional engineer is not. A housewife may do the cook everyday, she does the cook on the purpose of making some food to eat using what she has in the fridge or from the grocery store. Although she is experienced, there are still uncertainty in the process as to things influencing the food that might happen at any time. She is engineering food everyday, but she is not an professional engineer, at best a chef. If there is no boundary here between everyday engineering activities and engineering profession, all professions including cook, writer, and artist can be regarded as engineer. Engineers have striven to professionalize themselves ever since the mid-1800s (Layton, 1971; Noble, 1979; Pawley, 2009), and I see lots of boundary works drawing differentiation between science and engineering, but few among engineering, cooking, writing, and art. Maybe because they looks so obviously different, and there seems no need to say they are different. However, I say, they are essentially the same, if by the definition of engineering no matter I give above or Koen gives. So why they looks so different? In my opinion, what differentiate them are the things/products they are making and the way their products link to business field, namely, the product of cooking is for eating, the product of writing is for reading, the product of art is for appreciation, the products of engineering is for usage, and the business ways these products go to consumers are very different. I think this is why business or money is so important when talking about engineering (myriad of literature has clues of the importance of money, and it's beyond the length of this post. I might develop it in my essay), because the definition of engineering profession must include the description of the purpose (the products) and the way it consumes. We couldn't give engineering profession a definition independently (like making things, or doing design), because this will result in a broad dangerous "universal" category where engineers will lose themselves.
P.S.
I came across Dear Dr. Pawley's article "Universalized Narratives: Patterns in How Faculty Members Define "Engineering"" when doing the quick and dirty review of JEE papers. It's very interesting, and the background introductory part really helps me a lot to digest and make connections among Layton, Noble, Koen, Gieryn, and also the Changing the Conversation Report. After reading the narratives of engineering faculty, I become interested in what the narratives about "engineering" of engineers in the industry will be?
What the new engineer needs to know.
Several things struck me when I read this article. First, that what a beginner needs to learn at once is not really all that different in 2010 than it was in 1944. The "unwritten laws" addressed attitudes and behaviors expected of professionals. The laws make clear that 1) you are part of a whole, 2) your part of the whole is important and expected to be accomplished, no matter how small it seems, 3) the way you relate to and communicate with others will affect your productivity, and 4) that whole that you are part of is a hierarchy, and as a beginner you are not at the top. On a personal level I find these to be absolutely true, and though most students I work with seem to know them, occasionally there are a few that either don't know or don't believe the truth in these statements.
Second, there was nothing in the laws that was specific to engineering, or was technical in any way. There were a few that touched on business aspects of engineering (e.g. "promises, schedules, and estimates are necessary and improtant instruments in a well-ordered business"), but nothing about the technical competence. It made me wonder if either technical competence was assumed, or if technical competence was not a priority. I hope it is the former and not the latter.
Refecting on this article, I see some threads that tie this to the article we read by Dall'Alba, and my earlier post about that article. (See http://ene-hp-f10.blogspot.com/2010/09/epistemology-and-ontology.html for previous post.) In particular, I suggested that "what we call formal engineering education is primarily the epistmological portion of becomming an engineer, and intern/co-op experiences primarily the onotological portion of becomming an engineer."
Since the "laws" are not epistomological in nature, and are more centered on a way of being, I would classify them as ontological. So here's my big question: if they are "unwritten laws" for (dare I say) the way of being a new engineer in industry, how can we, as educators, be sure that our students learn them?
P.S. If anyone is interested in the 5 page article, I'm happy to share copies. Just let me know.
Evolvement of Engineering Profession as described in Noble and Layton
Monday, October 11, 2010
Summary of the description of design
After reading two weeks’ articles on the topic of engineering, I come across some different approaches to define what is engineering. As I read more, my uncertainty in understanding the word “engineering” grows. When I read a new article, I keep revisiting articles that I read before and try to find some similarities to help me link the fragment of ideas together. The most unfamiliar word in my understanding of aspect of “engineering” is “design”. Now I want to summarize my understanding related to “design” from the articles of Jonassen et al, Seely, Dorst, and Figueiredo.
The paper written by Jonassen et al. talked mainly about the attributes of workplace problem to address the need of redesigning curricula and experiences that better prepare students for workplace. They did mention a bit about “design problems” by saying that they were the most complex and ill-structured problems, which were usually vaguely defined or had unclear goals with unstated constraints. They said “design problems” had multiple solution paths, solutions and criteria for evaluating solutions.
In Seely’s paper, I simply interpret “design experience” to be problem-solving skills and practical experiences, and “design” to be problem-solving and practice.
I find lots of concepts related to “design” in Dorst’s article, which need to be further digested (especially the underlined phrases). He introduced several people’s approaches to “design”. 1. Simon defined the concept of “well-structured problems” as opposed to “ill-structured problems”, and considered “design” to be the solution to “ill-structured problems”. But in his definition, whether a problem was ill- or well-structured depended on the availability of solution methods, not by the property of the problem itself. 2. Dorst and Cross described “design” as a coevolution of the problem and the solution. 3. Dreyfus and Suchman described “design problems” as situated problems - if the designer thought the situation to be problematic, then the problem was a “design problem”. Meanwhile, the problem-solving steps could be logical, routine, and implicit, without any real choice by the designer. 4. Hatchuel illustrated that “design” was not merely problem solving, but it also contained other processes. 5. Dorst described in his article the term “design” without using “design problem”. He used paradox instead. He illustrated that “design” was the resolution of paradoxes between different aspects in a design situation.
When I revisit Figueiredo’s paper, I find he tried to give an all-sided definition of “design”. He said that the epistemology of “design” was related to “wicked problems” – the problems that were so complex and close interdependence with social and organizational factors that could not be handled by traditional scientific approaches. He stated that the evolution of systems design had been described as incorporating four categories: design as functional analysis, design as problem-solving (Simon’s approach), design as problem-setting, and design as emergent evolutionary learning (Dreyfus and Suchman’s approach).
To this point, the concepts of “design” are still fragments in my mind and need to be integrated. I could just figure out some key words related to “design”: problem-solving, ill-structured problem, vague and unclear. I hope that my understanding of the word “design” will get clearer by reading more materials in following weeks.