#trunkbaseddevelopment — Public Fediverse posts

🚀 "Trunk Based Development" 🤔 is like a never-ending intro to a term you didn't ask for, sprinkled with more buzzwords than a startup pitch. It promises "continuous" everything, yet leaves your brain stuck in an endless loop of jargon. Good luck branching out of this verbose forest! 🌲💥
https://trunkbaseddevelopment.com/ #TrunkBasedDevelopment #ContinuousDelivery #JargonOverload #StartupBuzzwords #TechHumor #HackerNews #ngated

🚀 "Trunk Based Development" 🤔 is like a never-ending intro to a term you didn't ask for, sprinkled with more buzzwords than a startup pitch. It promises "continuous" everything, yet leaves your brain stuck in an endless loop of jargon. Good luck branching out of this verbose forest! 🌲💥
https://trunkbaseddevelopment.com/ #TrunkBasedDevelopment #ContinuousDelivery #JargonOverload #StartupBuzzwords #TechHumor #HackerNews #ngated

🚀 "Trunk Based Development" 🤔 is like a never-ending intro to a term you didn't ask for, sprinkled with more buzzwords than a startup pitch. It promises "continuous" everything, yet leaves your brain stuck in an endless loop of jargon. Good luck branching out of this verbose forest! 🌲💥
https://trunkbaseddevelopment.com/ #TrunkBasedDevelopment #ContinuousDelivery #JargonOverload #StartupBuzzwords #TechHumor #HackerNews #ngated

🚀 "Trunk Based Development" 🤔 is like a never-ending intro to a term you didn't ask for, sprinkled with more buzzwords than a startup pitch. It promises "continuous" everything, yet leaves your brain stuck in an endless loop of jargon. Good luck branching out of this verbose forest! 🌲💥
https://trunkbaseddevelopment.com/ #TrunkBasedDevelopment #ContinuousDelivery #JargonOverload #StartupBuzzwords #TechHumor #HackerNews #ngated

Trunk Based Development

https://trunkbaseddevelopment.com/

#HackerNews #TrunkBasedDevelopment #AgileDevelopment #SoftwareEngineering #DevOps #ContinuousIntegration

🚀 Trunk based development simplifica la integración de código en equipos ágiles. Menos ramas, menos conflictos y despliegues más rápidos. ¡Conoce esta estrategia! 💻

Lee más 👉 https://www.soloingenieria.org/ingenieria-de-software/trunk-based-development/

#TrunkBasedDevelopment #IngenieríaDeSoftware #DevOps #Integración Continua

El código que no se integra rápido, se convierte en deuda técnica. Trunk based development te obliga a mantener tu trabajo siempre listo para producción. 💡 Pequeños cambios frecuentes superan a grandes cambios esporádicos.

#TrunkBasedDevelopment #IngenieríaDeSoftware #DevOps #Integración Continua

0 days since hearing someone say "pair programming is not enough, a pull request has to be made anyway so someone fresh can review the code!"

PR is waste. PR is too late. PR is too little. Reviews after the fact are fine, but should not be blocking, unless someone worked solo. "Fresh eyes" is a fallacy and mostly offers nothing else than manual nitpicks.

#Software #SoftwareDevelopment #PullRequest #CodeReview #PairProgramming #Mobbing #MobProgramming #Teamwork #TrunkBasedDevelopment

0 days since hearing someone say "pair programming is not enough, a pull request has to be made anyway so someone fresh can review the code!"

PR is waste. PR is too late. PR is too little. Reviews after the fact are fine, but should not be blocking, unless someone worked solo. "Fresh eyes" is a fallacy and mostly offers nothing else than manual nitpicks.

#Software #SoftwareDevelopment #PullRequest #CodeReview #PairProgramming #Mobbing #MobProgramming #Teamwork #TrunkBasedDevelopment

0 days since hearing someone say "pair programming is not enough, a pull request has to be made anyway so someone fresh can review the code!"

PR is waste. PR is too late. PR is too little. Reviews after the fact are fine, but should not be blocking, unless someone worked solo. "Fresh eyes" is a fallacy and mostly offers nothing else than manual nitpicks.

#Software #SoftwareDevelopment #PullRequest #CodeReview #PairProgramming #Mobbing #MobProgramming #Teamwork #TrunkBasedDevelopment

0 days since hearing someone say "pair programming is not enough, a pull request has to be made anyway so someone fresh can review the code!"

PR is waste. PR is too late. PR is too little. Reviews after the fact are fine, but should not be blocking, unless someone worked solo. "Fresh eyes" is a fallacy and mostly offers nothing else than manual nitpicks.

#Software #SoftwareDevelopment #PullRequest #CodeReview #PairProgramming #Mobbing #MobProgramming #Teamwork #TrunkBasedDevelopment

0 days since hearing someone say "pair programming is not enough, a pull request has to be made anyway so someone fresh can review the code!"

PR is waste. PR is too late. PR is too little. Reviews after the fact are fine, but should not be blocking, unless someone worked solo. "Fresh eyes" is a fallacy and mostly offers nothing else than manual nitpicks.

#Software #SoftwareDevelopment #PullRequest #CodeReview #PairProgramming #Mobbing #MobProgramming #Teamwork #TrunkBasedDevelopment

Published an update to: So, Yes, Trunk-based Development! Now What?

Added the missing reference to the Walking Skeleton when implementing large changes.

Thanks to Steve Hallman for bringing that to my attention 🫶

#trunkbaseddevelopment #faq

https://thinkinglabs.io/articles/2025/08/10/so-yes-trunk-based-development-now-what.html

How can you maximise feedback, streamline pipelines and minimise disruption caused by bugs etc?

I really enjoyed chatting to Bryan Jones about trunk-based development and many other things on his Quality Blether podcast! Listen to this episode and relive the vibe.

https://shows.acast.com/quality-blether/episodes/688160332a38d6f5cb162996

#CSudberyRecordings #ContinuousIntegration #TrunkBasedDevelopment

How can you maximise feedback, streamline pipelines and minimise disruption caused by bugs etc?

I really enjoyed chatting to Bryan Jones about trunk-based development and many other things on his Quality Blether podcast! Listen to this episode and relive the vibe.

https://shows.acast.com/quality-blether/episodes/688160332a38d6f5cb162996

#CSudberyRecordings #ContinuousIntegration #TrunkBasedDevelopment

How can you maximise feedback, streamline pipelines and minimise disruption caused by bugs etc?

I really enjoyed chatting to Bryan Jones about trunk-based development and many other things on his Quality Blether podcast! Listen to this episode and relive the vibe.

https://shows.acast.com/quality-blether/episodes/688160332a38d6f5cb162996

#CSudberyRecordings #ContinuousIntegration #TrunkBasedDevelopment

How can you maximise feedback, streamline pipelines and minimise disruption caused by bugs etc?

I really enjoyed chatting to Bryan Jones about trunk-based development and many other things on his Quality Blether podcast! Listen to this episode and relive the vibe.

https://shows.acast.com/quality-blether/episodes/688160332a38d6f5cb162996

#CSudberyRecordings #ContinuousIntegration #TrunkBasedDevelopment

How can you maximise feedback, streamline pipelines and minimise disruption caused by bugs etc?

I really enjoyed chatting to Bryan Jones about trunk-based development and many other things on his Quality Blether podcast! Listen to this episode and relive the vibe.

https://shows.acast.com/quality-blether/episodes/688160332a38d6f5cb162996

#CSudberyRecordings #ContinuousIntegration #TrunkBasedDevelopment

At work I have a monorepo with a bunch of helm charts in it.
The LCM for this repo is garbage - I wrote it a few years ago not really knowing what I was doing, but also knowing it was a temporary thing.
Turns out it’s not so temporary.

The company is looking to move to trunk-based development and I’m looking to redo the LCM of this repo.

Specifically this TBD: https://trunkbaseddevelopment.com/
We want to be able to say “we are doing this” and point at an industry way of doing things, rather than looking at something home grown or modified.

TBD makes sense to me, I’m pretty sure I understand it.

But- the charts on the repo are released altogether monthly (looking to change this, but anticipating another year or more before being able to do so), there are two breaking changes a year.

If I need to patch an old (supported) version, I might not be able to commit it to trunk and cherry-pick back to a relevant release branch because feature flags are hard to impossible in Helm (specifically in the way we use a library chart to provide 99% of the templating).

Am I “allowed” to commit/PR directly to the release branch in this case?
I know I technically can, but I can’t find what is idiomatic TBD in this situation.

#branchingstrategies #trunkbased #trunkbaseddevelopment #git #lifecyclemanagement

I've added a new project page to my blog for git-next, complete with an animation, to help explain the workflow that git-next enables.

https://kemitix.net/projects/git-next/

#git #TrunkBasedDevelopment #ci #ContinuousIntegration

Web & Wine bei Meteocontrol – spannende Talks über Bug-Management und Trunk-Based Development! Wie hält man einen Bug-Tracker schlank? Sind Feature-Branches wirklich der beste Weg? Zwei spannende Perspektiven aus der Praxis.

Den vollständigen Rückblick mit allen Insights findet ihr auf meinem LinkedIn!

#WebAndWine #SoftwareDevelopment #BugManagement #TrunkBasedDevelopment #DevLife #Augsburg

"As we can only rotate on code that can be integrated into Trunk, we are incentivized to take small steps. The smaller the step, the faster we can rotate. The more we rotate, the more engagement we feel as a group."

#softwareengineering #productengineering #smaller #trunkbaseddevelopment #continuousintegration

https://www.industriallogic.com/blog/trunk-based-ping-pong/

"As we can only rotate on code that can be integrated into Trunk, we are incentivized to take small steps. The smaller the step, the faster we can rotate. The more we rotate, the more engagement we feel as a group."

#softwareengineering #productengineering #smaller #trunkbaseddevelopment #continuousintegration

https://www.industriallogic.com/blog/trunk-based-ping-pong/

"As we can only rotate on code that can be integrated into Trunk, we are incentivized to take small steps. The smaller the step, the faster we can rotate. The more we rotate, the more engagement we feel as a group."

#softwareengineering #productengineering #smaller #trunkbaseddevelopment #continuousintegration

https://www.industriallogic.com/blog/trunk-based-ping-pong/

"As we can only rotate on code that can be integrated into Trunk, we are incentivized to take small steps. The smaller the step, the faster we can rotate. The more we rotate, the more engagement we feel as a group."

#softwareengineering #productengineering #smaller #trunkbaseddevelopment #continuousintegration

https://www.industriallogic.com/blog/trunk-based-ping-pong/

"As we can only rotate on code that can be integrated into Trunk, we are incentivized to take small steps. The smaller the step, the faster we can rotate. The more we rotate, the more engagement we feel as a group."

#softwareengineering #productengineering #smaller #trunkbaseddevelopment #continuousintegration

https://www.industriallogic.com/blog/trunk-based-ping-pong/

Branching is a great workaround for problems elsewhere in the system that we are unable or unwilling to fix.

Instead of looking for workarounds, what if we actually fixed the other problems in our system?

More at https://agiletechnicalexcellence.com/2024/07/08/why-we-branch.html #TrunkBasedDevelopment

Удобный CI/CD доступен каждому

Привет, Хабр! Недавно я выступал на Moscow Python Conf, где делился нашим опытом создания и использования CI/CD пайплайнов. В данной статье я расскажу об этих пайплайнах, раскрою их особенности и покажу, как они помогают нам быстро доставлять код и поддерживать высокий показатель Time To Market. Надеюсь, что наш опыт будет полезен и вам.

https://habr.com/ru/articles/820451/

#ci/cd #gitlab #pipeline #artifactory #trunkbaseddevelopment #phd #phdays #python

Удобный CI/CD доступен каждому

Привет, Хабр! Недавно я выступал на Moscow Python Conf, где делился нашим опытом создания и использования CI/CD пайплайнов. В данной статье я расскажу об этих пайплайнах, раскрою их особенности и покажу, как они помогают нам быстро доставлять код и поддерживать высокий показатель Time To Market. Надеюсь, что наш опыт будет полезен и вам.

https://habr.com/ru/articles/820451/

#ci/cd #gitlab #pipeline #artifactory #trunkbaseddevelopment #phd #phdays #python

Удобный CI/CD доступен каждому

Привет, Хабр! Недавно я выступал на Moscow Python Conf, где делился нашим опытом создания и использования CI/CD пайплайнов. В данной статье я расскажу об этих пайплайнах, раскрою их особенности и покажу, как они помогают нам быстро доставлять код и поддерживать высокий показатель Time To Market. Надеюсь, что наш опыт будет полезен и вам.

https://habr.com/ru/articles/820451/

#ci/cd #gitlab #pipeline #artifactory #trunkbaseddevelopment #phd #phdays #python

@yvg All right, bomb dropped, let's see what the team reacts. #TrunkBasedDevelopment

I'm going to go against software engineering orthodoxy, on a couple of topics:
1. Monorepos
2. Trunk-Based Development.

There ideas can be particularly toxic to small startups when taken as gospel truth.

#softwareengineering #git #monorepos #trunkbaseddevelopment

(Image credit: Microsoft Designer AI with the prompt: "A diagram of a git workflow with a datacenter server in the background"

#meme #softwareComplexity #TrunkBasedDevelopment

#meme #softwareComplexity #TrunkBasedDevelopment

#meme #softwareComplexity #TrunkBasedDevelopment

Very interesting talk on #trunkbaseddevelopment and how huge software implementations handle #releases by @jakobehn here #AzureDevops
https://www.youtube.com/watch?v=hL1OZfgoZGk&t=379s

GitHub Pull Requests issues

"We are investigating reports of degraded performance for Pull Requests. We are experiencing a delay in processing for repository push events, which may result in delayed updates to pull requests."

Is this not an in-built feature "degraded performance when using Pull Requests", being a disrupted integration? as opposed to continuous integration ...

#trunkBasedDevelopment

Trunk-based development and continuous delivery go hand in hand like 🥜 butter and jelly. The former enables the latter by ensuring a clean codebase, rapid iterations, and easy deployment. 🌟 #TrunkBasedDevelopment #ContinuousDelivery

Unpopular opinion about trunk-based development: I prefer having two branches over having a feature toggle. In case there are changes in both branches that are not compatible, git will tell me with a merge conflict. In case of changes with both the toggle on and off, good look finding and merging this. Long-lived toggles are worse than long-lived branches. So keep both small. If you can't, prefer branches.
#TrunkBasedDevelopment #git #Software

@Kanekotic
I'm curious..... Do you consider #trunkbaseddevelopment to consist of _only_ pushing directly to main, without a peer review? (I'm assuming non-pair-programming here)

when you se #github #gitlab... publicizing the use of pull requests and making them central to their platform. When will we get better tooling for #trunkBasedDevelopment ?

Still using #FeatureBranching? Try #TrunkBasedDevelopment instead. https://www.infobip.com/developers/blog/trunk-based-development-vs-feature-branching

The "problem" that GitFlow ostensibly solves is that of asynchronous quality gates.

It allows a dev to push code that has not yet been validated, and which may be later validated and promoted piecemeal.

Of course we've known for a long time, and the available evidence keeps growing, that this is a terrible way to ensure quality, or do anything else of value.

#gitflow #trunkbaseddevelopment #qa

"The industry has adopted pull requests as *the* way to code, and it's unfortunate.

The Pull Request was invented to accept code from people who are *not* on your team. From people who you don't know. People who may not have the context you have. It's deliberately an anti-team procedure."

#trunkbaseddevelopment #agility #pullrequest #meatloaf @qcoding

https://www.youtube.com/watch?v=ndxjPNDWUjs

My biggest trouble with advocating against #PullRequests and gating merges behind #CodeReview is that it is legimately effective for finding defects when done thoroughly. You get something valuable for the cost in review work, increased batch sizes, and multitasking. It makes it harder to convince myself and others that it's better to drop it for the sake of flow.

#Programming #SoftwareEngineering #SoftwareDevelopment #TheoryOfConstraints
#TrunkBasedDevelopment