Core programmers are merely advanced programmers who made the transfer from programming applications to programming code units to be used by other programmers.
Learn a programming language that supports building reusable components/packages if you have not done so already in 1.
Take an advanced course in UML and ORM. Most library developers use one or both of them.
Take a course in software engineering.
Learn at least modular, component-based, object oriented, and event-driven programming techniques and concepts. The more programming paradigms and languages you cover the more successful you become as a library/package programmer.
Learn more about the different operating systems and programming frameworks supported by these operating systems.
Focus your learning efforts on platform-independent frameworks, programming languages and technologies.
If the programming languages you learned so far have ANSI/ISO/IEEE/W3C standard versions, master the standards. Try to use standard code whenever possible.
Try to mimic simple, already established libraries, especially open-source ones. This is useful during the early phase of becoming a library/package programmer. Start with simple packages like units conversion and intermediate scientific calculations packages. If you are a collage student, make use of your non-programming courses by trying to implement their equations and scientific core as libraries.
Search for and try open-source packages in your field of programming. First download binaries/executables of the package. Try to use it and find its strong and weak points. After you've done that, download the source and try to figure out how it was done. Try to recreate those libraries or parts of them. At first do that after you've seen the code and later before you see the code. At later phases, try improving those libraries.
Learn the different approaches used to distribute and deploy components to programmers
Usually, library/package programmers tend to think recursively and/or iteratively of all problems they are presented with. Try to think of each problem as a collection of smaller problems (a sequence of simpler tasks) or as a repeated process of reducing the problem's scope to smaller scopes and then piling those scopes upon each other.
Library/package programmers tend to generalize. That is, when presented with a simple specific problem, they usually think of a more general problem and try to solve that general problem which will automatically solve the smaller one.
Learn a programming language that supports building reusable components/packages if you have not done so already in 1.
Take an advanced course in UML and ORM. Most library developers use one or both of them.
Take a course in software engineering.
Learn at least modular, component-based, object oriented, and event-driven programming techniques and concepts. The more programming paradigms and languages you cover the more successful you become as a library/package programmer.
Learn more about the different operating systems and programming frameworks supported by these operating systems.
Focus your learning efforts on platform-independent frameworks, programming languages and technologies.
If the programming languages you learned so far have ANSI/ISO/IEEE/W3C standard versions, master the standards. Try to use standard code whenever possible.
Try to mimic simple, already established libraries, especially open-source ones. This is useful during the early phase of becoming a library/package programmer. Start with simple packages like units conversion and intermediate scientific calculations packages. If you are a collage student, make use of your non-programming courses by trying to implement their equations and scientific core as libraries.
Search for and try open-source packages in your field of programming. First download binaries/executables of the package. Try to use it and find its strong and weak points. After you've done that, download the source and try to figure out how it was done. Try to recreate those libraries or parts of them. At first do that after you've seen the code and later before you see the code. At later phases, try improving those libraries.
Learn the different approaches used to distribute and deploy components to programmers
Usually, library/package programmers tend to think recursively and/or iteratively of all problems they are presented with. Try to think of each problem as a collection of smaller problems (a sequence of simpler tasks) or as a repeated process of reducing the problem's scope to smaller scopes and then piling those scopes upon each other.
Library/package programmers tend to generalize. That is, when presented with a simple specific problem, they usually think of a more general problem and try to solve that general problem which will automatically solve the smaller one.
http://www.wikihow.com/Become-a-Programmer
Комментариев нет:
Отправить комментарий