Mar-22-2017, 08:45 PM
My coding approach is a more or less the "inside-out" one. I try to split the problem into manageable parts, then write these parts with functions that I try to keep small and focused. Since most of my professional coding is server code that's hard to debug on the fly, I test my functions very throughly on the side before adding them to the code (I'll often write as much "test" code as "production" code). I'll even change the design to isolate the "hard" parts in pre-testable functions. Once all this is working I put the bricks together with some glue code to make the final application.
I do like the current trend of starting by writing the (automated) tests, then writing the app is just debugging an empty source file (or source code repository).
I do like the current trend of starting by writing the (automated) tests, then writing the app is just debugging an empty source file (or source code repository).
Unless noted otherwise, code in my posts should be understood as "coding suggestions", and its use may require more neurones than the two necessary for Ctrl-C/Ctrl-V.
Your one-stop place for all your GIMP needs: gimp-forum.net
Your one-stop place for all your GIMP needs: gimp-forum.net