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

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

What does your team dev workflow look like?

Please tick which apply, or comment for more info.

For those who use a monorepo with trunk-based workflow, can you teach me how code review, linting and security testing (e.g. SAST) fit into your workflow?

#MonoRepo #GitFlow #TrunkBasedDevelopment

"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

"By the time you need advanced Git — the wheels have already come off car. Let's focus instead on using core Git correctly."

https://blog.trunk.io/minimum-viable-git-for-trunk-based-development-81a5da7a77a7 #git #sourcecontrol #pullrequests #gitflow #trunkbaseddevelopment

Someone on Stack Exchange asked about whether #trunkBaseddevelopment and #gitflow are the same. This is my answer (they're not the same at all. One is based, one isn't) https://softwareengineering.stackexchange.com/a/442919/23915

Someone on Stack Exchange asked about whether #trunkBasedDevelopment and #gitflow are the same. This is my answer (they're not the same at all. One is based, one isn't) https://softwareengineering.stackexchange.com/a/442919/23915

It spotted the human side of why people tend to stick to their pull requests and code reviews quite well... #trunkbaseddevelopment #chatgpt

Deleting a feature flag and the code after releasing is a nice feeling of accomplishment.

Why are #FeatureFlags my preferred release approach?

1. Decouple deployment from releasing.

👉 Improving the #4keymetrics
👉 Allows #trunkbaseddevelopment

2. Releasing is less tense as rolling back is one click away

3. Able to test in production for a set of users instead on staging environments that bring a false sense of safety

Announcement on #GitHub about a new #DotNet Virtual Monolithic Repository

I'm a big fan of the #Nx build system - the tooling for #Angular is lovely but the .net support (or certainly how I want to use it) is limited.

Hoping this might take my #AzureDevOps CI/CD pipelines in an interesting direction.

Definitely something to keep an eye on.

Announcement here: https://github.com/dotnet/announcements/issues/241

#DevOps #MonoRepo #TrunkBasedDevelopment #ContinuousIntegration #ContinuousDeployment #ContinuousDelivery

Despite being sick as a dog, this was a *good* work week.

Prepped a client for a prod release that moves them forward in a number of ways - using #Terraform for the first time (and doing it well), tons of #TestAutomation, #TrunkBasedDevelopment, much better #DevSecOps pipelines, #FeatureFlags, shifting things to the left, doing so transparently & collaboratively.

Change is hard in big, highly-regulated companies. But it does feel really good to lay the foundation for orgs to improve.