View Single Post
  #2   Spotlight this post!  
Unread 07-10-2013, 20:20
EricH's Avatar
EricH EricH is offline
New year, new team
FRC #1197 (Torbots)
Team Role: Engineer
 
Join Date: Jan 2005
Rookie Year: 2003
Location: SoCal
Posts: 19,810
EricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond repute
Re: Engineer or Lawyer?

Quote:
Originally Posted by Tristan Lall View Post
Surely you can think of counterexamples—a problem solved by a lawyer and a problem created by an engineer. Why don't you list a couple for us to discuss?
Lawyers do tend to solve the problem of innocent people being convicted. Also the problem of deciphering legalese.

Engineers creating problems... Not gonna go there. Let's just say that engineers whose main undergrad work has minimal hands-on work tend to get some "What was that engineer THINKING?" (and worse) from folks that have to build/repair/otherwise interact with stuff said engineers designed.


To answer the initial question: I'll go with engineer, but reserve the right to try to understand the lawyers' thinking.
__________________
Past teams:
2003-2007: FRC0330 BeachBots
2008: FRC1135 Shmoebotics
2012: FRC4046 Schroedinger's Dragons

"Rockets are tricky..."--Elon Musk

Reply With Quote