do you seriously think a non-coder can effectively choose good coders?
do you really think a non-sysadmin can effectively choose good SysAdmins?
I mean, there is enough overlap between the fields that a good sysadmin can usually tell if a programmer is completely BSing, and a good progrogrammer (well, a C systems programmer) can usually tell if a SysAdmin is completely worthless, but I wouldn't trust anyone who was 'pure management' to detect either.
Comments
No offence but you why are you calling the position CTO if he is expected to code and do sysadmin work. Why not simply call him/her an engineer?
Just curios on the choice of title.
do you seriously think a non-coder can effectively choose good coders?
do you really think a non-sysadmin can effectively choose good SysAdmins?
I mean, there is enough overlap between the fields that a good sysadmin can usually tell if a programmer is completely BSing, and a good progrogrammer (well, a C systems programmer) can usually tell if a SysAdmin is completely worthless, but I wouldn't trust anyone who was 'pure management' to detect either.