General Engineering Introduction/Notebooks/quiz

{Click on the triplets that will get you points for writing in the notebook: |type="[]"} + GoingToDo Doing Rant - Hypothesis Procedure Conclusion - Problem Solutions Testing - Design Details Next Steps {Which are appropriate responses to mistakes or anticipation of mistakes? |type="[]"} + drawing a light horizontal line through text .. so that it is still readable - taking a black marker and obliterating something so that it can not be read + putting a big X through what one doesn't want considered - ripping out the page - writing in pencil or eraseable ink - using white out, nail polish or something similar to hide the mistake {Why does using the margins appropriately inspire respect? |type="[]"} + understanding design purpose of a tool and using it appropriately - efficient use of the pages + there is meaning to the pattern in which white space is used + randomness arouses suspicion {Why is it important to form paragraphs, lists, drawings, draw diagonal lines through unused parts and skip one line between paragraphs? |type="[]"} - efficient use of notebook + makes impossible to go back and add text, drawings without destroying pattern + patterns inspire respect + makes it impossible to leave space to write in later {Why is it important to write in a font that fits between the lines? |type="[]"} - efficient use of notebook - fonts way too small or large indicate a brain tumor - easier for the instructor to read many notebooks + indicates an attempt to make the notebook attractive and easy to read {When the course is over, what happens to your notebook? |type="[]"} + you take it home - becomes school property - you leave at school to inspire other students taking this class - it is destroyed because it is no longer needed, everything important is in electronic form {Why should you always write in the first person using "I" when everyone is working together? |type="[]"} + to make it clear what you are doing versus what others are doing .. transparency + inspires confidence in engineering project managers .. who is doing what becomes clear + project managers expect completely different details from engineers observing the same events, writing in first person inspires this - writing the exact same "I" statements in engineering notebooks makes manager feel comfortable that there is a consensus + differences resolved are more respected by project managers than instant consensus among everyone involved {Which of these indicates Chronological Integrity? |type="[]"} - leaving blank spaces in the notebook to go back and write in later + signing in and out + using diagonal lines through blank spaces that are never going to be written in + patterns in pen color/texture + patterns in mood + patterns in white space utilization {A title is needed at the top of the page when |type="[]"} - all the time - at the beginning of a project only + when new page is started because of a new activity/topic + when a new page is started because of a new day - when a new page is started because the previous one filled up {SignIn starts engineering. Why is this important? |type="[]"} - record time so can get paid or get points in the class + record time for future project estimations + begin engineering, feel like accomplishing something + creates an open vessel to capture the unknown engineering accomplishments that might occur {Why is it important to only write down the odd pages and never leave blank spots to write in later? |type="[]"} - helps fill up then notebook + violates chronological integrity + capture next step thinking in RANT, not in blank spaces - logical flow of thoughts and concepts is important - need to write like a lab report or book {How does the discipline of notebook writing help an engineer get paid for being ignorant? |type="[]"} + helps you learn from nature + helps you get better, faster at learning on your own + helps you establish trust, transparency, accountability and respect + helps you get better at reading manuals that do exist and improving them {Most students don't initially want to Rant or Signout. Why? |type="[]"} + afraid of loosing the creative flow + worried brilliant thoughts will be lost forever - don't want to earn the three points + think the current interruption can be dealt with quickly - want to prove they stayed up all night {The best notebook drawings are: |type="[]"} - orthographic showing 2 or 3 sides + look like a patent drawing with arrows leaving letters or number pointing to features - don't need words to describe them + are also described in words as if the drawing is not there - are large + start small and get bigger as detail is added - are drawn separately on paper then tapped or pasted into the notebook - are similar to sketches made in art classes {What are the reasons for stopping in the middle of a page and leaving the rest of it blank? |type="[]"} + new day - want to draw a big graphic, can not in the space left + title doesn't reflect what plan to do now - trying to fill up notebook quickly {Suppose it is time for lunch. You are planning on coming back from lunch. What do you do? |type="[]"} - sign out, draw diagonal line to the bottom of page + sign out, no diagonal line so can sign in underneath sign out when come back - Finish the GoingToDo Doing RANT triplet - write note "spent one hour at lunch" in the left margin {The english policy in this class is |type="[]"} - spelling has to be correct + has to be readable - don't need to worry about capital letters and periods - grammar has to be correct {How does a notebook turning playing into engineering? |type="[]"} - helps time fly, helps one focus so much that a sense of time passing is lost + re-reading helps one continue the playing, the focus of the previous day + notebook slows one down so that grokking can mature + writing, re-reading helps one remember, reorganizes the brain + notebook turns into a muse {Why are small triplets rewarded by counting them, rather than large triplets when grading notebooks? |type="[]"} - indication of time management - indication of dealing with OCD problems + creation of engineering boundaries + helps prevent freshman messes {Writing after the fact can be detected by: |type="[]"} + lack of random detail + more rational linear thought than usual + line thickness changes in writing + pen color changes + fewer graded triplets than normal in the time claimed + uniform emotion in the handwriting {Initially writing in a notebook feels like it is slowing you down, making you less efficient. But soon, it will speed you up because: |type="[]"} - your hand will stop cramping - you will develop photographic memory + you will stop running around in circles lost in the forest of confusion and fog + you can pick up where you left off faster + you do things once rather than over and over again + you will do things over again clearly expecting to see something new {GoingToDo do is typically stimulated or related to: |type="[]"} - the project + the title + previous RANT + previous Testing - previous GoingToDo {GoingToDo captures: |type="[]"} + intention - success + chaos of the moment - memories + expectations {GoingToDo is trivialized and can result in the triplet not being counted if: |type="[]"} + repetitive for no reason + no intention, expectation or anticipation - logically makes no sense - seems disconnected from any stimulus {Examples of doing are: |type="[]"} + documenting program bug - writing a program + documenting what trying to do that the drawing program is not letting you do - drawing + documenting google keywords that are closest to what is being searched for - writing url and successful google keyword searches + describing steps and what is working/not working - describing only steps of the shortest path to success + uncommon tools used - lists of trivial materials and tools repeatedly used over and over again {The dangers in doing are: |type="[]"} + trying to prove you did something by writing + writing huge doing and not getting as many Project triplet points - logically not relating to GoingToDo - RANTing inside of Doing + avoiding RANTing by making large Doing {Doing is where design emerges. How? |type="[]"} + issues are discovered that stimulate new designs + data is collected that helps choose between designs + problems emerge that kill designs + scope is discovered that constricts or opens up many more possibilities + possibilities, alternatives are discovered {RANT in the context of notebook writing means: |type="[]"} - let loose, emphasize anything that makes you mad and write about it - explore your feelings + Reflect, Analyze, NexT steps - Run ANTs through everything to dig up detail {The Reflect part of RANT means: |type="[]"} - explore personal meaning, growth, values, goals, feelings, morality + summarize the chaos of Doing + compare with intentions and expectations of GoingToDo - list all the things that went wrong {RANT can be done |type="[]"} + at any time - only when there is enough doing + once per GoingToDo, Doing - only when feelings are strong {The Analyze part of RANT includes: |type="[]"} + logically consistent - say nothing new .. everything has to already be said in GoingToDo and Doing + looks at what went right/wrong and why + picks through Doing looking for errors, how could be done more accurately + laments that if had more time would have .... + describes a better (perhaps invents) tool for the job + if could do over again would ........... + would automate (turn into robot) this .... in the future {The Next Step part of Rant includes: |type="[]"} + short summary of GoingToDo and Doing + suggests possible next GoingToDo + what was expected and not expected + at minimum is a list of the next steps {The goal of this course is to: |type="[]"} + Push students through the playing, doing it first, designing and problem solving narrative + Turn students into problem solvers - Turn students into designers - Turn students into people that do things first {Issue characteristics include: |type="[]"} + No ownership - Complete awareness by everyone + Avoidance by everyone + Possible engineering problem {Which below are owned by an individual engineer? |type="[]"} - Issues + Problems - Solutions - Problem/Solution Pairs {How is an engineering problem different from what most people call a problem? |type="[]"} + Possible solutions are not part of the problem description. + The next step is not finding the one solution, but visualizing many solutions/designs. + The are no consequences because nothing is in production or use yet ... the engineer is doing something first. + There many not be a solution. - problems emerge from projects + projects form around problems {Who is responsible for fixing an engineering problem? |type="[]"} + project teams of engineers form around problems, they attempt to fix them together - the engineer who owns the problem - the engineer that turned the issue into a problem - a different engineer than one that created the problem, forcing engineers to communicate and document + perhaps nobody because there is not a solution {Who comes up with problem/solution pairs? |type="[]"} - engineers + technologists/technicians/experienced experts - students doing homework - teachers creating the answer key {Big Projects with out problems are: |type="[]"} - Rare + Not engineering projects - Always have a blame game associated with them - Have clear requirements {Big Projects with requirements are: |type="[]"} + engineering projects + each requirement is the result of a known "problem" - require technologist expertise - require scientist expertise {Whose problem is it that you don't know something? |type="[]"} - You, the engineer + The world - The teachers - The text book {Whose problem is it that you can not follow any of the existing tutorials? |type="[]"} - You, the engineer + The world - The teachers - The text book {Whose responsibility is it to create/revise/polish a tutorial you understand for others like you in the world? |type="[]"} + You, the engineer - The world - The teachers - The text book {Whose responsibility is it to take this issue of not being able to follow a tutorial or non-existence of a tutorial and turn this into an engineering project? |type="[]"} + You, the engineer - The world - The teachers - The text book {When an engineer is blamed or is frustrated, the engineer |type="[]"} - finds someone else to blame + defines a problem + creates a project + creates project requirements + starts designing solutions + methodically checks solutions {An engineer deals with frustration by: |type="[]"} - ignoring it - exercises, medication to deal with the pain + leveraging it into inspiration + reviews the frustrations in anticipation of solutions appearing in dreams + reviews the frustrations in anticipation of 1000 questions flowing creatively + reviews the frustrations in hopes of seeing more clearly the answers in the scavenger hunt of life {Engineering problems are |type="[]"} - lists of causes + symptom details - pain of change + hopes, expectations, possibilities - solutions + form and function + unit testing input and expected output - algorithms {Frustration is caused by |type="[]"} - lack of training + fog, uncertainty - knowing what we don't know + knowing what we want to know + not knowing whether anyone else knows {The three parts to testing are: |type="[]"} - negotiating the test protocol + describing the test + performing the test + analyzing the test results {Suppose you need to work on an engineering project, but do not have your notebook. What should you do? |type="[]"} - Write on a piece of paper as if you had your notebook and staple the paper into the notebook at a later date. + Give up trying to get notebook points for what was done. - Write a summary of what you did in your notebook at a later date and signing in and out at the later date. -After the notebook is found, sign in with the date of the work done, write in as much detail as possible in the usual format and sign out at the estimated finish time. {When writing in an engineering notebook, sometimes one must stop writing on a page, draw a diagonal line to the bottom and then start writing on a new page. When is this necessary? |type="[]"} - Were interrupted (bathroom, lunch) + new day - somebody else has arrived and joined the team + Switched to a different project/title