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.
It was mostly excellent however a big problem that can occur is over-extension of an idea, and the sense that you must clarify everything explicitly. Software Engineers are bad at sketching. Like, you start to solve A and then you get drawn in B, C, D, etc. Drawn into the weeds.
-
-
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.
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.