|
|
|
|
|
|
by wruza
1645 days ago
|
|
|
When doing a non-trivial task that you’ll probably do again, but not daily, write down all the commands/steps you execute into your OBTF (that’s another tip for you to have one). This way helps with things that you can’t practically automate into scripts but it’s easy to reproduce by copying a section of OBTF into an untitled.txt, renaming some names and pasting it into a terminal line/block-wise. Edit: another, related one: use snippets (files or folders) for temporary/sandbox projects. I found it useful to strip down a business logic off a working project and use that as a project template. If you want to test how a feature or a design approach feels before making it a branch or a module, you can just spin up a separate project, spread the mud there, distill, and then use it almost as is in your work project. Of course you can do that on a branch, but sometimes it feels better not to, because in-project testing may damage your development dbs, use irrelevant (or costly) services, etc, i.e. leak some logic to sandbox which ought to be destructive from the beginning. |
|
|
[1] no hits at Wikipedia, less than a handful hits on Hacker News, none with an explanation
[2] seems to be "one big text file"