At my previous contract we did RFCs for complex concerns that cross-cut multiple features. Or when we wanted to throw out an idea and have it relentlessly challenged by our team members.
If we are dealing with 10s of sentences we are okay. If it is 100s of sentences, or god-forbid 1000s of sentences then you can literally end up becoming a technical writer. You have to keep-it-simple or else it becomes a waste of time.
-
-
I think at an early point people have to learn to be like "stop-the-theory and let's actually see what this looks like in practice". And get real feedback, either through prototyping or by doing whatever behaviour was discussed.
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.