Trunk-Based ThierryAfter 3 years I finally came to publish the last part of On the Evilness of Feature Branching ...
Where is the Evilness of Feature Branching?
the evilness surprisingly hides behind the use of feature branches
Jeff GriggThere's also the issue of adopting git and Bitbucket "because everyone else is doing it," and so imposing Code Reviews "because it's part of the tool, and everyone else is doing it," but having *NO* process discipline, nor process understanding, and so ...
The "code reviews" are useless,
*AND*
they take *DAYS* to accomplish.
Sometimes a week or more of delay, for every "code review" step.
Typically the expectation is that code reviews will "solve all our problems." The scope of the code review work keeps expanding. But absolutely no time or resources are scheduled to actually *do* the work. And the bosses pressure the coders being reviewed to get it done sooner, while pressuring the reviewers to focus on other work.
So it's long, costly, unpredictable delays that create no value.
soaproot@JeffGrigg @tdpauw I've seen enough benefits from code review that I'm not sure what my overall position is, but I do agree with "pressure the coders being reviewed to get it done sooner, while pressuring the reviewers to focus on other work" (or more subtle versions of what amount to similar misalignments in terms of who is tasked with getting the task done).
@soaproot @JeffGrigg Exactly that!
Jay Bazuzi@tdpauw I want to weave Refactoring into this take, but I'm not sure how.
@JayBazuzi good point. Refactoring probably fits in the incremental software engineering skills.