"What's the triangle?" I (perhaps naively) asked.
"That's the source of ontological truth".
That's when I realised there's a whole other level of ability that some people have. This guy was a zen master of bullshit.
"What's the triangle?" I (perhaps naively) asked.
"That's the source of ontological truth".
That's when I realised there's a whole other level of ability that some people have. This guy was a zen master of bullshit.
However, one of the most frustrating colleagues has been a former Chemical Engineer. In 15 years, he has only implemented new technologies when absolutely forced to by people higher in org chart, even when the need is beyond obvious. He fought against 64-bit computing, hypervisor virtualization, automated config management, privileged account management, SaaS apps, and IaaS cloud platforms.
So, I don’t think that you can determine whether someone is a good engineer solely based on their background. I just try to stay away from the people who want to change everything and the people who want to change nothing.
there are so many bozos faking this precicley because a surface glance doesnt necicarily tell you they are full of shit.
A key indicator is do they dig into code?, do they look at data bases?, do they mock stuff up and prototype? do they reference company strategy and financial targets?.. they cant just talk the talk, they also have to walk the walk.
If someone said this to me then showed me a prototype integrated masterdata and business intellignence solution, how it would interface with busines governance, change management etc. i would be happy.. if they just had that triangle and wanted someone else to "do the technical stuff" then its another story :)
Or a cheeky way of looking at it.. does involving this person normally make things more or less clear? does the time to get value from work reduce or increase?