Ready.
A (programming) method(ology) is some way of organizing the programming process. A method may sometimes come in the form of a set of principles, at other times, it may be some computer software or hardware that eases your programming, and makes harder in other ways. When you adapt to it, you are using its (implicit) method, even if you are reciting of no particular principle in your mind.
Even if you used no particular method, the particular programming language, and especially the compiler and other tools you use would still be implicitly imposing some specific method on you. For example, when writing a Lisp program with a pure text editor, versus using a rapid-application-development tool with Java, would be altogether different ways of organizing the code-writing, testing, etc.
There are also more developed methods, telling ideas for a variety of details, maybe also providing tools for automatizing the suggested steps.
In other words, each tool is implicitly a new method, as far as you use it, and adapt to its guidelines. A tool may be a anything from a flowchart-template that makes flowchart-drawing easier, to a full visual-programming suite, with source-code modification facilities. The tool being used would also influence the program testing, etc.
The suite of tools you have available may change your programming style, quite naturally, without much explicit thinking. If the tool you use can convert a flowchart to a program code, you may more likely use it at the development phase of your software, as opposed to having a tool that only lets drawing but not much else.
This page is being edited, yet. Please visit later again.