A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Discussing AI software development, and showing off what we're building.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
Movie and TV enthusiasm, criticism and everything in-between.
Memes and software development shitposting
Web design, graphic design and everything in-between
A community of golfers and golfing enthusiasts
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other.
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
If you have any sort of branching then you are not doing CI, you are doing promiscuous integration but not continuous integration.
Do you mean it's better to work on master and/or a monorepo approach?
master
yes, absolutely.
I’m aware of this ideology but I think that branching has too many practical and psychological benefits. :)
I’d be curious to hear how it works in practice with a specific project and team.
If you merge multiple times per day, it implies that average lifetime of branches is less than a day, and that’s as continuous as you can do imo.
Branching generates a lot of integrational and operational cost to the software development process.
In there I explained my point of view.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If you have any sort of branching then you are not doing CI, you are doing promiscuous integration but not continuous integration.
Do you mean it's better to work on
masterand/or a monorepo approach?yes, absolutely.
I’m aware of this ideology but I think that branching has too many practical and psychological benefits. :)
I’d be curious to hear how it works in practice with a specific project and team.
If you merge multiple times per day, it implies that average lifetime of branches is less than a day, and that’s as continuous as you can do imo.
Branching generates a lot of integrational and operational cost to the software development process.
why branching on git is wrong
Adrián Norte ・ Oct 27 '18 ・ 1 min read
In there I explained my point of view.