• Andrei Alexandrescu (17/17) Nov 11 2015 Walter and I are planning major marketing moves, for which there's a
• Rikki Cattermole (8/25) Nov 11 2015 So I take it, it's time for a "The D programming language and your
• qznc (3/6) Nov 11 2015 So you are AAA now, Architect Andrei Alexandrescu.
• Chris (6/12) Nov 11 2015 Has anybodv ever read this book? I can only recommend it:
• The Old One (6/23) Nov 11 2015 Excellent, Andrei!
• =?UTF-8?Q?Ali_=c3=87ehreli?= (3/5) Nov 11 2015 I've just used it when talking with a colleague today. :)

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

Walter and I are planning major marketing moves, for which there's a 
necessity to describe my relationship with D succinctly. People 
routinely introduce me as "co-creator of D" and I need to explain "well, 
D had already been created when I joined but I worked on a number of 
features" etc.

Although D looks quite different now than it was in 2006, the "creation" 
act only happens once, so "co-creator" is inaccurate and shifts credit 
inappropriately. Last thing you want in PR is someone in the crowd to go 
"wait, but you didn't create it" and the next-to-last thing is to need 
to define the relationship between you and what you're selling as "well, 
it's complicated".

So we mulled over this for a while and we decided to go with "D Language 
Architect". I'll use that henceforth. Walter will remain of course the 
"D Language Creator".

No need to call me that way :o).


Thanks,

Andrei

Rikki Cattermole <alphaglosined gmail.com> writes:

On 12/11/15 1:26 AM, Andrei Alexandrescu wrote:
 Walter and I are planning major marketing moves, for which there's a
 necessity to describe my relationship with D succinctly. People
 routinely introduce me as "co-creator of D" and I need to explain "well,
 D had already been created when I joined but I worked on a number of
 features" etc.

 Although D looks quite different now than it was in 2006, the "creation"
 act only happens once, so "co-creator" is inaccurate and shifts credit
 inappropriately. Last thing you want in PR is someone in the crowd to go
 "wait, but you didn't create it" and the next-to-last thing is to need
 to define the relationship between you and what you're selling as "well,
 it's complicated".

 So we mulled over this for a while and we decided to go with "D Language
 Architect". I'll use that henceforth. Walter will remain of course the
 "D Language Creator".

 No need to call me that way :o).


 Thanks,

 Andrei

So I take it, it's time for a "The D programming language and your 
future" book?

Would be awesome to define what is wanted for D3, along with project 
goals ext. in it. That way we can incrementally work towards it in D2.

LeanPub would be awesome for this. Add on having it on Github so to 
accept changes. Also means that you don't have to release any time soon.

Anyway, hello big A(rchitect)!

qznc <qznc web.de> writes:

On Wednesday, 11 November 2015 at 12:27:00 UTC, Andrei 
Alexandrescu wrote:
 So we mulled over this for a while and we decided to go with "D 
 Language Architect". I'll use that henceforth. Walter will 
 remain of course the "D Language Creator".

So you are AAA now, Architect Andrei Alexandrescu.

Chris <wendlec tcd.ie> writes:

On Wednesday, 11 November 2015 at 16:46:52 UTC, qznc wrote:
 On Wednesday, 11 November 2015 at 12:27:00 UTC, Andrei 
 Alexandrescu wrote:
 So we mulled over this for a while and we decided to go with 
 "D Language Architect". I'll use that henceforth. Walter will 
 remain of course the "D Language Creator".

 So you are AAA now, Architect Andrei Alexandrescu.

Has anybodv ever read this book? I can only recommend it:

http://www.amazon.com/Architect-Bee-Human-Technology-Relationship/dp/0949874000/ref=sr_1_3?ie=UTF8&qid=1447272861&sr=8-3&keywords=architect+or+bee

Or the revised edition

http://www.amazon.com/Architect-Bee-Technology-Current-affairs/dp/0701207698/ref=sr_1_2?ie=UTF8&qid=1447272861&sr=8-2&keywords=architect+or+bee

Architect or B? No, architect and D! (Bad bad pun, I know)

The Old One <first.last example.com> writes:

On Wednesday, 11 November 2015 at 12:27:00 UTC, Andrei 
Alexandrescu wrote:
 Walter and I are planning major marketing moves, for which 
 there's a necessity to describe my relationship with D 
 succinctly. People routinely introduce me as "co-creator of D" 
 and I need to explain "well, D had already been created when I 
 joined but I worked on a number of features" etc.

 Although D looks quite different now than it was in 2006, the 
 "creation" act only happens once, so "co-creator" is inaccurate 
 and shifts credit inappropriately. Last thing you want in PR is 
 someone in the crowd to go "wait, but you didn't create it" and 
 the next-to-last thing is to need to define the relationship 
 between you and what you're selling as "well, it's complicated".

 So we mulled over this for a while and we decided to go with "D 
 Language Architect". I'll use that henceforth. Walter will 
 remain of course the "D Language Creator".

 No need to call me that way :o).


 Thanks,

 Andrei

Excellent, Andrei!

And what a timely coincidence, since the other day I saw 
"co-creator" and thought less than favorably about you for it. 
But D Language Architect is excellent! Kudos!

=?UTF-8?Q?Ali_=c3=87ehreli?= <acehreli yahoo.com> writes:

On 11/11/2015 04:26 AM, Andrei Alexandrescu wrote:

 we decided to go with "D Language Architect". I'll use that
 henceforth.

I've just used it when talking with a colleague today. :)

Ali