Day 1 update by Eric, a member of the Symposium event
(media.greatawakening.win)
You're viewing a single comment thread. View all comments, or full comment thread.
Comments (31)
sorted by:
Exactly my point.
The confluence of all that (particularly on the software side) plus business, financial, and political considerations is where my job lies. I rarely push back on the engineers from a design perspective...but I do usually get to ask "what do you need to build it, how many people do you need, for how long, and how are we paying for it?"
Oh yeah... I get asked that all the time. Sometimes you'll get the business side asking, "but do you need THAT one? I mean, isn't there like a cheaper alternative?" No, because this one is accurate to 5 micrometers. The alternatives are accurate to 5 hundredths... we spend some big bucks on engine development and testing lol. Love you business guys though. Finding us money when "we don't have any" is nice and you guys keep us honest.
Personal opinion -- it is exceptionally fair to ask you the "do you need THAT one" question. However as long as you can justify, we need to be supportive. It's a bit of the old "trust but verify" mentality. However we also need to understand the answer you are giving, and know when you are BSing us or not. It's why in my role I can't just be a business person, I absolutely have to have a background in the tech side and know when to lean in versus when to let you guys just do your jobs.
Having said that, in my experience engineers almost never throw BS. Facts and precision are baked into your DNA. Software developers on the other hand...