Three Piece Proactiv

Check out these Ebay listings for Three Piece Proactiv products.

eBay Logo  

Proactive Three Piece Product Kit

Proactive Three Piece Product Kit


$11.00

Here are a few great Three Piece Proactiv deals on Amazon:


Proactiv Solution 3 Step System Kit, 2 Month Supply

Proactiv Solution 3 Step System Kit, 2 Month Supply


$34.59


Our basic clear skin kit includes full-size bottles of the essential Proactiv® Solution system. This system, developed by dermatologists, uses Combination TherapyTM to help heal and stop breakouts at their source.

Includes:
Renewing Cleanser to wash away excess oil and dirt

Revitalizing Toner to balance skin tone

Repairing Lotion to help attack bacteria…


Proactiv Solution Micro Crystal 3 Piece 120 Days Luxury Set

Proactiv Solution Micro Crystal 3 Piece 120 Days Luxury Set


$62.45


3 PC PROACTIV SOLUTION MICRO CRYSTAL 3 PC 120 DAY LUXURY SET

8 OZ RENEWING CLEANSER
8 OZ REVITALIZING TONER
4 OZ REPAIRING TREATMENT

FRESH, SEALED AND NEW!!!!…


Olay Professional Pro-X Clear Acne Protocol

Olay Professional Pro-X Clear Acne Protocol



…

Proactive Programmer

If you are reading this article then it is evidence enough that you want to move your career into the excellence path.  To improve your skills and invest your time and energies in the direction where every moment you work should pile the success of your career.

This article will guide you in few areas in project life cycle where as being a programmer one can make the difference.

Programming Paradigm:

In his famous book of “You don’t need a Title to be a Leader” Mark Sanborn explains that how anyone anywhere can make a positive difference in his work without waiting to be awarded with titles.

Unfortunately the technology and skill race does not allow a programmer to focus his attention other than his own R&D of technologies, tools, open sources etc. during this race he become so focused and devoted that he hardly understand that there can be a significant difference in the success of a project if he put some percentage of his work into other areas.

In a way this is also required, that without proper R&D and focus the team of developers cannot produce what is expected from them. However the success of the project is not only dependent on the development area, in this article I am going to explain the areas where a programmer can stretch himself for not only to increase his skill set for career growth but also to the successful contribution in making the project a success story.

Before the Project

In an ideal flow you will be notified about your future project in advance. However sometime you become suddenly part of a running project or a recently initiated project.

In the later case you hardly have any room for preparation, but in the first case where you have a forecasted engagement with another project. Your Strategy should be as follow:

Strategy

  • Get maximum information about the domain of the project and get familiar while reading/talking and debating with the related peoples. Get authentic statistics about the domain and ground realities.
  • Enquire about the Failures of projects in the same domain, which can help you learning from the experiences of others.
  • During the current project create a separate repository of utility methods / components which can be used in the coming project, prefer only the general utility methods / components collection.
  • Download /install open source solution of the same domain
  • Maintain a personal notebook of lesson learned in the current execution of the project

 

During the start of the Project

If you spent good number of hours in the preparation of the project and you have shared the learning to your upcoming PM then there is a pretty good chance that you will be requested to involve in the meetings and share your learning in the Project Management meetings. Your Strategy should be as follow:

Strategy

  • Share tangible evidence in each of the R&D you have done earlier. In case you have not completed proper R&D then still make it authentic what little information you have.
  • Note down the high level risks of the project, any ambiguity and any other challenges which can hinder the development activities.

 

During Requirement Management

In some methodologies the whole team is part of the requirement gathering and then participated in the design. However in some the developers get engaged few days before the development starts. Whatever the situation in your environment, if you have chance to get involved in the requirement gathering sessions then it is a golden opportunity for you to contribute and step forward.  

Strategy

  • Highlight the non happy flow of the processes during the sessions.
  • One part of your mind should constantly thinking about the alternative solutions.
  • Note down the part of the requirements which require R&D or your team has never done it before.
  • Try to turn the requirements into small tangible pieces which can be developed  independently
  • Highlight the risks based on the knowledge you have learned and with your experience
  • Note down the testing scenarios which meets the actual Stakeholder’s requirements

 

Designing solution

In some methodologies prototyping is being used, somewhere only charting is used and in some places actual coding of the project starts. Your Strategy should be as follow:

Strategy

  • Think more about the actual user’s need and link it with the technology tools you have learned so far.
  •  As part of the project team never wait for the development phase to write the code, initiate the coding of classes / methods which supports the parts of requirements. Create dummy tables, collections to help support your template methods.

 

 During Development

This is where actual work is begun, although you have been given your assignments with briefings and deadlines. You need to have the following checklist with you. Your Strategy should be as follow:

Strategy

  • Before you take the assignment make sure you have enough understanding of each artifact required to be developed. Any ambiguity can result in an unexpected deliverables.
  • Write your code as it is the last time you are writing and your work is going to be inspected after that.  If you think that you will do the refactoring or improvement in later time, believe me that’s not going to happen.
  • Your code must be accompanied with the Unit Testing, alternate scenarios, GUI, User friendly and non functional expectations.
  • Complete your tasks well before the assigned date and use the remaining time to break the code. Turn yourself into a cracker position and try to break your own code.  
  • Ask your peer to test your developed features and take the third opinion. You never know what you are missing.

 

During Testing

During testing your participation can make the testing team evaluate the developed solution more perfectly. Your Strategy should be as follow:

Strategy

  • Work along with the testing team as one of the tester, learn how they are testing and treating the features. Learn what non functional requirements are major or critical.
  • Help the team in learning the functional cycle and provide insides of the critical areas of application.
  • Learn the testing methods so you know well enough when developing the code that it will be tested in such manners

 

About the Author

Over 11 years of Development and Management of enterprise solutions globally, the author has the professional certifications in IBM XML, Sun Certified Programmer, Web Component Developer and Sun Certified Enterprise Architect. Received the ICT Award 2007 for the development of Dawn.Net Portal
He is working in Telenor Pakistan as Manager Application Management and can be reached through his email aligreat@gmail.com,

Some of the other articles by the same author

http://www.codeproject.com/KB/architecture/Iterative_Development.aspx

http://www.codeproject.com/KB/architecture/Introduction_to_Faults.aspx




3/11/10: White House Press Briefing

 Mail this post