Re:Things I've learned transitioning from engineer to engine...
by vonmoltke on Monday September 25, 2017 @08:41AM
(#15329901)
> I write this from personal experience, having seen teams been disbanded who did a great job shipping... stuff that brought in zero value to the company.
How do you get to this point? I have never been on a team where someone further up the business wouldn't come up to us at some point and ask, "Uh, what is the business value of what you are doing?"
Re:Things I've learned transitioning from engineer to engine...
by lozenge on Monday September 25, 2017 @08:56AM
(#15329996)
"We need this refactoring/migration to enable feature X"
Re:Things I've learned transitioning from engineer to engine...
by chi18 on Tuesday September 26, 2017 @06:37AM
(#15337525)
> have a great team building things that matter with satisfied members.
Cherish this, and secretly examine every nuance of its ups-and-downs while you can. The basis of all of your future management efforts will be to get back to something similar to this point.
Just remember, a manager is a well-organized servant leader who is ultimately never responsible for success.
I write this from personal experience, having seen teams been disbanded who did a great job shipping... stuff that brought in zero value to the company. This is something I personally would want to avoid if possible, hence me putting "company first" as #1.
Of course no two situations and companies are the same, so there might be cases when having a healthy team trumps doing what the company (thinks it) needs. For now I'm personally sticking to aligning all three where I can: have a great team building things that matter with satisfied members.