@michaelbartnett No. He was the PR man for the project. He doesn't have any coding or development experience at all.
-
-
Replying to @cmuratori
@cmuratori@michaelbartnett That's pretty terrible if so. Nearly every writeup I've seen describes him as architect/designer of original DX.4 replies 0 retweets 7 likes -
Replying to @nothings1 reply 0 retweets 0 likes
-
Replying to @dougbinks1 reply 0 retweets 0 likes
-
Replying to @broepstorff
@broepstorff@dougbinks@nothings@michaelbartnett He was a printer driver evangelist at Microsoft originally...1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@broepstorff@dougbinks@nothings@michaelbartnett ... then he was@checker's evangelist for WinG (I met him when I was there!)1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@broepstorff@dougbinks@nothings@michaelbartnett@checker I don't know what he PR'd in between then and DX, but then...1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@broepstorff@dougbinks@nothings@michaelbartnett@checker ... he was the head evangelist for Eisler and Engstrom on DX.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@broepstorff@dougbinks@nothings@michaelbartnett@checker Like I said, PR and developer "liason" work for DX was important.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@broepstorff@dougbinks@nothings@michaelbartnett@checker So it's not like he was an incidental part of the project.1 reply 0 retweets 0 likes
@cmuratori @broepstorff @dougbinks @nothings @michaelbartnett @checker But he wasn't the guy writing the API or the driver layer.
-
-
Replying to @cmuratori
@cmuratori@broepstorff@dougbinks@nothings@michaelbartnett@checker Also, the revisionist history here is absurd: http://www.alexstjohn.com/WP/2013/02/23/bunnygate/ …2 replies 0 retweets 1 like -
Replying to @cmuratori
@cmuratori@broepstorff@dougbinks@nothings@michaelbartnett@checker Alex in no way _intended_ to "leak" the rumor as a PR strategy.0 replies 0 retweets 0 likes
End of conversation
New conversation -
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.