4
I was recently introduced to an article in Medium on Trunk Based Development (TBD). The title was totally provocative, You don’t need Feature Branches anymore... ("You no longer need Feature Branches" in free translation).
So I come to question:
- What is the TBD?
- What promises of problem solving that TBD promises to solve?
- Already used in practice? If yes, which of the advantages real obtained by using it?
- Taking advantage, what disadvantages you have experienced using it?
So much compared to another code-flow or things you just realized yourself
- Taking advantage, what disadvantages you have experienced using it?
- How to work with remote teams with TBD?
One of the points of Medium’s article was that "Pair Programming is essential", how to do with a decentralized team? Or remote limbs with no physical proximity to each other?
Someone voted negative without being followed by a closing vote. I would like to know if you have something that has shown no effort, or lack of clarity/usefulness to the community. If you have something like this, please comment so I can improve the question
– Jefferson Quesado
I was the one who downvoted. I’m sorry I gave the reason at the time, but anyway, your question is absurdly wide, with at least 4 questions. At no time are you objective in doubt, saying what is the specific problem/doubt you have and how/if you tried to solve it. After all, it is impractical to answer everything. I suggest you read more about it (https://trunkbaseddevelopment.com/) and if you have any PUNCTUAL questions, return to the OS so we can be more objective in the resolution.
– regmoraes
@regmoraes, so it was a lack of objectivity in doubt and a broad question on my part. Your suggestion for improvement would be to divide it into smaller questions of lesser scope and more manageable, correct?
– Jefferson Quesado
Exactly. With smaller and more objective questions it is easier to get a quick answer. With many questions in the same question, it becomes laborious and tiring, which can even amaze people who even have something to contribute, but by laziness give up (I’m even hehe).
– regmoraes
@regmoraes , the second point (resolution promises) is extremely linked to the point of what is TBD. After all, why talk about it without talking about "why" using TBD? The third point (and its sub-paragraph) ends up being a question of practical use, asking to report experiences. Does that sound integrated, or do you disagree? The fourth point, remote team + TBD, seems a little out of place at the time of rereading, months after the writing of the question. But at least I try to justify his presence there. Maybe I could remove, who knows.
– Jefferson Quesado
@regmoraes , and to finish, would be extremely flattered if you create a pair of question-answer and mark this as a duplicate of your question. So, I can create a new question (and let this be marked as duplicate) focusing on what was missing (or new plural questions, if I notice that some topics I think it’s fair did not fit properly in the answer of the hypothetical question-answer that you might ask
– Jefferson Quesado