When you wrote for the second time almost the same code and for the next time you started to copy & paste those code. That sounds like you should introduce a function. Functions in Makefile can shorten and clean things up and will be shown in the following…
Typing ‘for’, ‘if’, ‘main’… and hitting tab to expand a snippet can save some time.
Testing can be tedious, testing can be tricky and testing can drive whole development… insane ;) But it is an important part of professional software development, but sometimes usually late at night only one line can make the trick. And staying with a shell - the environment devops used to use a lot it gets even more easier to write little one-line tests
Makefiles are long, they tend to be complex and we used to have a configure script which built them for us. Did you ever looked into such generated Makefile, maybe a file of one of a bigger project? For me they seem sometimes like one long regexp ;)
When do you prefer raw console output over using a debugger and setting breakpoints?
When setting up a build pipeline with for example TravisCI or AppVeyor did the first build worked out?
Did you ever thought of alias typos in your shell alias file?
subscribe via RSS