I would like to introduce you the Fast Discovery programming. It is based on the discovery on errors or failures as fast as possible to keep going on the good way to achieve the goals.
Fast Discovery, comes from the concepts like fail-fast or fail-early, but fail is not what we want to achieve. What we want is to know what we are doing works. So that, Discovery is a better term than Fail.
This concept can be applied to many fields on your life, like engineering or design, but the below examples are especially for programming.
This tips can help to become faster at programming, saving time for thinking and make things, and not waiting for things to happen like restarting a server or wait for the “Compiling…” alert to be closed.
IDE / Editor
First of all, learn your IDE or editor. Learn how to use it, how it can help you on your workflow.
Learn the shortcuts for the most common actions you usually do. Here are some examples for Eclipse, that you can do instead of moving the mouse wheel up and down or finding a menu options:
- To find and open a file, use Alt + R. It shows a pop up, while you type it shows the files that follow that pattern. Wildcards ‘*’ and ‘?’ can be used.
- Common for saving a file: Shift + Alt + F to format the code and Control + S to save the file.
- Find some string in all file: Control + H.
- Customize the search options, just select the ones that you use. Probably it is just “File Search”.
- For faster results, select the folder or project you want to look for and check the option “Selected resources”. It will not search in ALL the workspace
You name them. Just look for your more used actions and try to find the shortcut on the menu.
These are the most important shotcuts! Too obvious for some, and very unknown for others. You loose important seconds by moving your hand to the mouse, and trying to select some words. Just use the keyboard.
- Control + C for Copy
- Control + V for Paste
- Control + X for Cut
- Shift + (up,down,left,right) for Selection
If there is no more choice and you use the mouse, keep in mind the tips below. You will not need to aim your selection like a sniper. Try it now!
- Double click: select a full word.
- Double click + move: select full words while moving.
- Triple click: select a full paragraph.
- Triple click + move: select full paragraphs while moving.
Fix common options or questions. How many times do you click on an “OK/Cancel” alert on each save or compile. Have you read it carefully? Is it a “Do not ask me again” checkbox? This can save some precious time.
On this example… yes click the checkbox “Run always in background”, and then you can continue working while it executes. It will never show up again.
Unit testing is good for testing, we all know it (well others just hate it). It can help also while we are coding. A piece of code does not need to be finished to be executed with a unit test. Either it is needed the unit test before the code, like on Test-driven development (TDD).
While working on a piece of code, it is possible to isolate its execution with a unit test. With this it is not needed to start up a full application and test just what we want. So much time is saved until the code is finished and tested on the real application.
Network times are always a pain. Try to make your workflow as offline as possible, by using a local server instead of a server located in another network.
Also make your tools not to connect to internet. For example: Maven has the -o option to just use the local repository and do not connect to the remote repositories.
mvn -o install
These are the goodnes of Fast Discovery progarmming. Saving time, just a little or a lot, on each step of your workflow can significantly improve your speed at programming.
And more speed at programming means more results achieved. And that is good for your job. Do not work like this again:
These are just some examples, of course, there are much more. Just tell yours!!!