3 ms·
Why wouldn't the architects work on prototypes? In my experience, class distinction between "architects" and "developers" is a red flag. Actually, the term "ar
by gruseom 15y ago
Why wouldn't the architects work on prototypes?
In my experience, class distinction between "architects" and "developers" is a red flag. Actually, the term "architect" is itself a red flag. Come to think of it, even the term "developer" is kind of a red flag.
A lot of red flags :)
- ComputerGuru 15y agoOh they did. I was a developer/architect, did more developing than any of the developers and more architecting than any of the architects. However, not all the "architects" (mind you, none of us actually used that term/title) were developers. We had the head of the QA in charge of testing and real world deployments on the team, as well as the lead interface designer. Their feedback helped to find a solution that would be both feasible and user friendly. That's why I said the developers would work on the prototypes.
- gruseom 15y agomind you, none of us actually used that term/title What terms/titles did you actually use? By the way, I didn't intend my "red flag" comment to imply that your particular setup didn't work well. There are lots of good variations. The sociology of software projects is fascinating.
- ComputerGuru 15y agoTeam Leaders. Even if a team was more smaller teams :) C/C++ Team Lead, Web (C#/ASP) Team Lead, QA Team Lead, Design Team Lead, and The Boss (startup CEO).