@cmuratori @michaelbartnett So he's giving his definition of what it means to be an engineer when he has never actually engineered anything?
-
-
Replying to @cmblasko
@cmblasko@michaelbartnett Yes, he was a technical evangelist, he has literally zero engineering experience.1 reply 0 retweets 1 like -
Replying to @cmuratori
@cmuratori@cmblasko@michaelbartnett His job was to get developers interested in developing for DirectX.1 reply 0 retweets 1 like -
Replying to @cmuratori
@cmuratori@cmblasko@michaelbartnett And as a sidenote, I don't think he's ever even _claimed_ that he has any dev experience.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@cmblasko@michaelbartnett I mean maybe he had some back before he was a printer evangelist (his original MS role AFAIR).1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@cmblasko@michaelbartnett But certainly not since then. I think he just assumes everyone knows he wasn't a dev.2 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@cmblasko Especially considering his byline in that article literally says, "co-creator of the DirectX family of API’s"2 replies 0 retweets 0 likes -
Replying to @michaelbartnett
@michaelbartnett@cmblasko And to be fair, evangelism was a very important part of making DirectX happen, so it isn't a lie,1 reply 0 retweets 1 like -
Replying to @cmuratori
@cmuratori@michaelbartnett@cmblasko But it's definitely a complete fallacy to think that Alex St. John ever solved a hard tech problem...1 reply 0 retweets 1 like -
Replying to @cmuratori
@cmuratori@michaelbartnett@cmblasko ... let alone an easy one. He simply has no idea what that actually entails in practice.1 reply 0 retweets 0 likes
@cmuratori @michaelbartnett @cmblasko Especially since most of the hard problems in DX1 were solved by Todd Laney :)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.