Quote:
|
Originally Posted by phrontist
Sorry, that might not have come out too clearly, my tounge was firmly lodged in my cheek.
|
Quote:
|
Originally Posted by phrontist
It's the audience.
Engineers have no time for this low bandwidth, long, droning, "liberal arts" style drivel. Give me tables, figures, formulas, algorithms, methodology specifications! I don't want to read your 30 page diatribe on the importance of balance between the "Recognition" and "Inspiration" aspects of competitive robotics!
|
Let me try to explain it to you. I think you do know that Engineers have a passion. You will be surprised to see how many engineers and mentors are on the forum at 2 in the morning and 6 in the morning, reading all these long threads. A lot of times Engineers do have to write reports or tutorials (that are 30 pages) for the company they work for or a product they are manufacturing. Have you seen any reports before that was made by an engineer? Yes, there are lot of tables, figures, formulas, algorithms, methodology specifications, at the same time there are explanations if that report was to go outside the company. The only time they use just tables and formulas are when they are communicating between teams (I can be TOTALLY wrong on this one, but I am just posting from my knowledge, my uncle is an electrical engineer, I have been in his office several times and seen the way he works in a team as well as his reports he made for other divisions). I think I have a mind that works like an engineer. I like to work with tables, somethings that are organized and not something that is 20 pages long. But I do like to read when it's meaningful and worth it.
Engineers (wannabes) do have a passion...