Jump to content

WriteBrain Communicates Technology: Difference between revisions

From Wikidelphia
Created page with "http://home.comcast.net/~writebrain1/index.html Explaining can mean a lot of things: <br>- Your customers explain what they want. <br>- You explain what you did for them; and,..."
 
No edit summary
Line 1: Line 1:
http://home.comcast.net/~writebrain1/index.html
http://home.comcast.net/~writebrain1/index.html  


<br>


Explaining can mean a lot of things: <br>- Your customers explain what they want. <br>- You explain what you did for them; and, when you're done... <br>- The User Guide and Help system explain all the puzzling features<br> of the interface, things that you thought were self-evident. <br>- And, hopefully, the SDLC (systems development lifecycle)<br> documentation explains inner workings to future generations of<br> developers (say, in 3 months or so).


Explaining can mean a lot of things: <br>- Your customers explain what they want. <br>- You explain what you did for them; and, when you're done... <br>- The User Guide and Help system explain all the puzzling features<br> of the interface, things that you thought were self-evident. <br>- And, hopefully, the SDLC (systems development lifecycle)<br> documentation explains inner workings to future generations of<br> developers (say, in 3 months or so).
Like the old cartoon showing 20 different wrong ways to build a tire swing, a lot can go wrong when you don't pay attention to communication throughout the development process.<br>  


Like the old cartoon showing 20 different wrong ways to build a tire swing, a lot can go wrong when you don't pay attention to communication throughout the development process.<br>
[[Category:Is-Business]][[Category:Is-Consultant]][[Category:Does-Writing]][[Category:Does-Consulting]][[Category:Is-Enterprise]]

Revision as of 16:54, 6 February 2015

http://home.comcast.net/~writebrain1/index.html


Explaining can mean a lot of things:
- Your customers explain what they want.
- You explain what you did for them; and, when you're done...
- The User Guide and Help system explain all the puzzling features
of the interface, things that you thought were self-evident.
- And, hopefully, the SDLC (systems development lifecycle)
documentation explains inner workings to future generations of
developers (say, in 3 months or so).

Like the old cartoon showing 20 different wrong ways to build a tire swing, a lot can go wrong when you don't pay attention to communication throughout the development process.