Avatar

glad_cat

glad_cat@lemmy.sdf.org
Joined
10 posts • 810 comments
Direct message

I’m actually confused by the whole post.

In contrast, the branching model

TBD is a branching model which works fine with DVCS. I’ve used it successfully with git and it was better than the other “git/github flows.”

The point of TBD is to have well-defined branches for certain tasks or topics. Nothing is forced for how you achieve this. For example you won’t get conflicts if you have a rule to merge the master/develop/main branch, or squash or rebase your commits on your feature branch before your merge request is ready.

Also, I disagree with the person who says it’s a “developer culture problem.” IMHO it’s a branching model that should be respected in the same way we have rules for code formatting or using linters before a commit whether it’s a tool, a hook, or a check in the CI.

Overall I prefer TBD because it has fewer branches than the other methods.

permalink
report
parent
reply

TBD only says that you should have less branches than the other branching models. I quite like it and have used with git and merge requests. I may be misunderstanding something, but I only see this as a way to organize the branches, nothing more.

permalink
report
parent
reply

What do you mean by local? git can hide merges or feature branches, and you have to save your temporary code by pushing it to the server at the end of the day. You can rebase your code or squash it before merging, but TBD is not talking about that IIRC.

permalink
report
parent
reply

TBD forces teams to collaborate synchronously since changes are pushed straight to trunk

The main page about TBD says you can still use feature branches, merge requests, or squash/rebase, and that’s how I use it. It only says why and how you should use release branches, and how you should fix bugs in a release. The linked article is not talking about TBD at all, hence my confusion about this whole post.

permalink
report
parent
reply

ne pas upvoter

Trop tard, upvoté depuis lemmy.sdf.org. Ça t’apprendra, petit chenapan !

permalink
report
parent
reply

Pareil, me too, idem, +1. Tupperware était bien dans les années 80 quand il n’y avait pas d’alternatives, mais aujourd’hui tu peux trouver un vague équivalent par exemple chez IKEA pour bien moins cher. Je ne fais pas la pub de IKEA, mais j’ai une collection de petits plats carrés en verre avec couvercles que tu peux acheter séparément et les joints sont nettoyables. Je ne vois pas pourquoi j’irai chez Tupperware désormais. Ils ont bien essayé de vendre quelques trucs chez Carrefour il y un ou deux ans, mais j’ai l’impression que ça a fait un bide.

permalink
report
parent
reply

Pour avoir bossé dans 5 ou 6 boîtes qui faisaient de l’agile, les managers s’emparent du process et font du cycle en V avec micro-management. Et comme ce sont les managers qui décident, ça fini toujours par partir en couille. Alors oui, l’agile c’est comme le vrai communisme : en théorie c’est marrant, dans la pratique ça n’existera jamais sauf pour une startup entre potes.

permalink
report
parent
reply

Intéressant le commentaire sur le ramadan. Ça pourrait être intégré à la société comme les fêtes ou machins chinois du nouvel an, façon “marché de noël” avec des trucs à manger (on aime tous ça)de mais à la place c’est très restreint aux collègues de travail musulmans qui font ça dans leur coin parce qu’il n’y a rien de global.

permalink
report
parent
reply

Don’t forget to install the Winamp skin for this. God, I miss themes and skins…

permalink
report
reply

free speech only applies to governments

That’s the American view of free speech from the American constitution. It’s very specific, and not universal at all. Free speech can be a philosophical concept, and it existed way before the American continent was discovered.

permalink
report
parent
reply