software developer, What Not To Do

As I was working through developing a software, I got completely entangled in straightening out the initial requirements. Later, I got these wrong entirely. Reason? well, I jumped straight into developing UI (User Interface) instead of understanding the user and the way they work and behave as a business process.

Moral of The Story:

Never develop a software without understanding how intended end users work in the real-world with or without existing system(s) in place; and emphasize on translating both electronic and manual business process(es) into requirements.

Something, I shall learn to do from now on; is spend more hours on system requirements.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s