Programming

19656 readers

501 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Does anybody actually use trunk based development in their company? (trunkbaseddevelopment.com)

submitted 11 months ago by onlinepersona@programming.dev to c/programming@programming.dev

5 comments fedilink hide all child comments

I've heard it thrown around in professional circles and how everybody's doing it wrong, so.. who actually does use it?

For smaller teams

"scaled" trunk based development

top 5 comments

sorted by: hot top controversial new old

[–] BatmanAoD@programming.dev 0 points 11 months ago (1 children)

I haven't worked on any teams where all members committed "every 24 hours", and there have always been some branches that live longer than we'd like (usually just unfinished work that got deprioritized but still kept as an eventual "todo"), but most teams I've worked on have indeed followed the basic pattern of only one long-lived branch, reviews and CI required prior to merge, and all feature-branches being short-lived.

[–] ____@infosec.pub 1 points 11 months ago

A hard timeline on commit strikes me as less than ideal.

People are people. They have issues, they screw up, but they still write good code.

Seems like a brutal metric that encourages minimal commits without real change.

[–] Ismay@programming.dev 0 points 11 months ago (1 children)

I do, on a 900+ developer mono repo. Works like a charm.

We just have a CD that allows to deliver each project each micro service individually.

[–] Diplomjodler3@lemmy.world 1 points 11 months ago (1 children)

You deliver your software on CDs?

[–] boblin@sh.itjust.works 1 points 11 months ago

Most likely CD is intended to mean continuous delivery, which commonly means automation in processes that deliver your software to it’s target audience.