88
Does anybody actually use trunk based development in their company?
(trunkbaseddevelopment.com)
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
It's effort to switch, and we don't benefit from having separate copies of the repo bc we're so small. No one steps on eachother's toes, so distributed version control isn't necessary.
Now, the fact that most devs know git and SVN is dead is not lost on our CTO, but putting the effort to switch over doesn't provide direct value to the customer, so I have to make the case that switching to git would do enough from a productivity and maintenance standard to effect customers.
But just productivity and maintenance but if your devs start to leave or retire, you're not gonna get the best quality replacements for them if you're using outdated tech. No one wants to learn new skills that aren't going to help with their career growth.
I'm a relatively new hire and we just hired another person 2 weeks ago