There is no hard and fast rules to drafting a graphical layout of a programmer's learning curve. It follows a rather loose series usually at the programmer's discretion.

Speaking at the 8th internal Seminar of Describe Web Technologies, Samuel Nengolong, a co-Developer of codemint.net gives a spotlight on harnessing a better learning curve in programming. With several years of experience and expertise in ICT and ofcourse programming he deduced that tackling discomfort as a programmer is a breakthrough to achieving your objectives as a programmer.

You can also call a programmer

Moreso, focus, setting objective, consultations and being time bound are cool blueprints to follow in any career choice and certainly programming;
and as always, he pinned a thumb to three phrases thus:

* Know your business

* Work well in a team

* Solve business problems.

nice