|
|
|
|
|
|
by no-bugs
3621 days ago
|
|
|
To be clear: I was NOT speaking of the first one :-). As for the second one: > the architect is the guy that can sketch that reporting engine that will be nurtured and improved by the team, Yes (in fact, I LOVE this definition ;-)). > therefore he both codes and shares knowledge. Not necessarily, and that's the whole point. Initial development (as noted in the article) is one of the exceptions - but "sketching a thing that will be improved" (which I agree with) is VERY different from "working day in and day out on improving it" (which I do NOT like). And this difference is the whole point of the article. |
|
|