4 ms·
I agree. In order to optimize efficiency, changing priorities (ie. interrupting work) should be avoided unless absolutely necessary. A five minute task equates
by TravHatesMe 7y ago
I agree. In order to optimize efficiency, changing priorities (ie. interrupting work) should be avoided unless absolutely necessary.
A five minute task equates to: context switching, creating a branch in JIRA, checking out the branch, complete this small task with a few lines of code, debug and run tests, create the PR.. It is awfully distracting and I often lose focus on what I was previously working on. Great, I think I'll take a little break or go for lunch a bit early.
- levosmetalo 7y agoThen it’s your process that makes all this overhead. Why not just commit those two lines of code to the main branch and continue?
- TravHatesMe 7y agoBecause the process pays off. If you have a mature code base, all changes should be reviewed by at least one member of the team. Being consistent with your branching process is important. I favor squash-merging pull requests to keep a clean history of the target branch, it makes it easy to track down bugs. In my mind, this development process, as tedious as it may be, is worthwhile. In my mind it is the proper way of managing a codebase, I consider it part of the job.
- wool_gather 7y agoBecause when the two lines of code are the wrong thing and nobody notices the problem with them for five weeks, you're going to spend much much more than that overhead tracking it back down and fixing the original issue properly.