Or hey, here's a radical idea: reduce the number of features N.pic.twitter.com/s5PtMBthTT
-
That's actually a problem in lots of project. Managers thinking more dev = can get more done. Which is true up to a point... It also mean more maintenance, more communication, more buggy code, regression and user workflow broken. "The mythical man month" is a timeless book.
tMMM was among my earliest lessons in the limits of social scalability (in this case of engineering teams)pic.twitter.com/KI81KqvIeb
-
-
My experience. 1. One experienced comitted senior dev gets you further than ANY number of mediocre devs. 2. At some point of mediocrity you start going backwards not forward. 3. Coupling experienced dev with talented, less experienced devs at 1:2 -1:3 ratio worked 4 me best.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Are those... honey badgers?!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The book many software engineers have read but no non-technical manager of software engineers has ever read.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.