The world of writing and programming
You are probably wondering how writing and programming are a lot a like.
When you write a story, the idea is to take the reader through a process that arrives and comes to the same conclusion that you intended.
Good programming works the same way. You wouldn't be reading this if I had to think about how this will look at the end if it I had to write it in purely HTML or had to transfer what I'm writing form Microsoft Word to Blogger format.
So a good program can be defined this way. A program is a logical progression of choices which enable you to perform a task in three or less steps. Your phone applications. You touch an icon and the application begins to run. If it connects to the internet, it uses the username and password you provided it to make that connection. You are then given the main screen and you type in or select a person you want to send an email to, type in a subject. type in some content and press the send button.
These are known facts to anyone who has used an Email program
The problem is with generating a uniform and logical pattern for other kinds of emails, such as automatic responses and normal replies.
And this is also where writers and programmers alike fail miserably.
If I may, take a look at this:
When working with email, you have the option to send a new email, reply to an existing one, block emails and automate responses.
What's wrong with it?
Everything!
Is that a job description? Or a bunch of train car style mashups?
Truth is, is just a really bad sentence filled with intent to cover all the topics in a really bad gramatical way.
The end user just wants to know how to send an e-mail.
To send an e-mail:
This is a very specific set of steps for the end user to follow to create and send an email.
It is also the statement of work (SOW) needed to be done by the programmer to write the code.
Clear descriptions create clear tasks for both the programmer and the program user.
When you write a story, the idea is to take the reader through a process that arrives and comes to the same conclusion that you intended.
Good programming works the same way. You wouldn't be reading this if I had to think about how this will look at the end if it I had to write it in purely HTML or had to transfer what I'm writing form Microsoft Word to Blogger format.
So a good program can be defined this way. A program is a logical progression of choices which enable you to perform a task in three or less steps. Your phone applications. You touch an icon and the application begins to run. If it connects to the internet, it uses the username and password you provided it to make that connection. You are then given the main screen and you type in or select a person you want to send an email to, type in a subject. type in some content and press the send button.
These are known facts to anyone who has used an Email program
The problem is with generating a uniform and logical pattern for other kinds of emails, such as automatic responses and normal replies.
And this is also where writers and programmers alike fail miserably.
If I may, take a look at this:
When working with email, you have the option to send a new email, reply to an existing one, block emails and automate responses.
What's wrong with it?
Everything!
Is that a job description? Or a bunch of train car style mashups?
Truth is, is just a really bad sentence filled with intent to cover all the topics in a really bad gramatical way.
The end user just wants to know how to send an e-mail.
To send an e-mail:
- Tap your Mail icon
- Once running, click on new
- Start entering the persons name
- If it already exists, it will be automatically added
- If it doesn't already exist, just continue typing in the email address
- When done, click your tab key
- Enter the subject
- When done, click your tab key
- Enter the body of your message
- When done, click the send key.
This is a very specific set of steps for the end user to follow to create and send an email.
It is also the statement of work (SOW) needed to be done by the programmer to write the code.
Clear descriptions create clear tasks for both the programmer and the program user.
Comments
Post a Comment