A question for my engineering friends: is there a body of knowledge around how to craft "solo" roles that don't sit on a team / are the first person to start doing the work that will eventually be owned by a team?
-
-
If I couldn't get that second person full time right away, I'd at least move in that direction ASAP. E.g., external code/arch reviews. Or borrowing somebody to pair program 1 day/week.
- End of conversation
New conversation -
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.