As easy as it says, for beginners it is actually pretty hard to do things on the top of our heads but there are a few things that most developers should know what to do:
- Try Googling on relevant pages and bookmarking the relevant pages related to the topic that you are working on - refer them as much as possible as sort like a list of steps on what to do.
- Try stitching the code and modify parts that is needed. Again code working for the sample script should work for your real life project. Stitching the parts needed.
- Look for the API of a particular framework. Some API are hard to read and reality is parts of the framework is under construction and yet not tested and released for developers. Understand parts of project where they uses this API for a better feel of the framework.
- Consult with related parties ASAP or using StackOverflow if there is problems relating to a particular problem. Nothing should stop your progress in making a development work.
- Develop in small incremental steps so the whole application does work on. An analogy is where 0.99 effort of the exponential vs 1.01 effort on the exponential differs greatly.
- We must know that many times our research topic is old. Most of the topic leads from three to four years old so technology could have changed since then. We are not the leading part in R&D so make sure people start posting their own findings up if it is a related thread that everybody is asking to contribute back to the source.
- Nothing is perfect. These days we should know what is correct and follow the lead without the need of blindly Googling.
- People these days asks for founders for their company because they believe they are in the lead edge of expertise. Get a mentor to do things on a different scale.
- Go with online courses to equip with the essential skills that you needed. Courses from Udacity, CodeSchool and others proves valuable into new learning areas with technology.
- Keep on developing new products of a particular project. Make challenges to change the standard way of programming until you learn how development changes from finish to start again - waterfall lifecycle or now says it is rapid prototyping.
- Know Agile and Scrum well versed, every development company uses it.
- Don't expect correct answers is actually the correct solution to the problem. It will take time to people to learn from them and know what is right and wrong.
- Read a lot and start learning. A better answer is probably from expert developers who with many project experiences.
- Good communications is required to work well; reading, writing and listening.
There is actually more to it but I know it is hard work.
Just keep trying :)
No comments:
Post a Comment