Skip to main content
5 events
when toggle format what by license comment
Feb 10, 2016 at 23:55 comment added J. M. Becker @dave, The Strongest teams have a technical lead who is a Sr. Dev (on Dev Team), or Sr. Engineer (Ops Team), who provides that technical assessment to the manager. Then the manager makes the business call, which if you have the right lead, you trust them with your reputation. Its just two very different skill sets. If a Dev only sees mobility in becoming management, your managers are either very napoleonic.... OR they just happen to be the most Sr technical Lead... but only for now.
Aug 8, 2011 at 21:19 comment added dave The boss is responsible for the delivery of the product. If he is not technically minded, then he should rely on the assessment of those who are. If he is technically minded, the he should contribute his knowledge and experience to the assessment. Either way, he needs to be involved in the decision - that is his job. I have personally seen many projects where the coders just want to do something that is new, fun or pad their resume. I have seen this as a developer, an architect and as a TL. A competent boss is one who can see the big picture and make the best choice for the project/company.
Aug 8, 2011 at 19:30 comment added Sean McMillan It doesn't matter if the boss has the technical chops or not; What matters is who is responsible for technical decisions. The boss may have all the information he needs to make that decision, but he's not writing the app.
Aug 8, 2011 at 19:27 comment added dave It sounds to me like the boss has a technical background and does understand the issues, the OP just does not agree with his assessment. Many technical people move into management positions because they understand the big picture. I do not know who is right or wrong (it is rather grey) but I would not write off the boss as a Dilbert cliche.
Aug 8, 2011 at 15:52 history answered Sean McMillan CC BY-SA 3.0