Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
craig939393257032dHave your colleagues blindly click approve on all pull requests, never link work to stories, no unit tests, 2000 line functions that you scroll right on as much as down, and microservices that are actually poor SOA as they RPC each other, and therefore must be in sync without any story / ticket to piece the release together, and also multiple bug fixes and indeed multiple entire features per branch. Get back to me xD
netikras2659232dWell, as long as merges to develop are squashed and reviewed, it should be alright
but yes, I see your point. It's messy
vomitmachine63032dI most all of my development on master. I'm also one of two developers at the company. Neither of us care a whole lot. Whatever floats your goat dude.
junon282232dSound like your senior knows what he's doing.
People who merge commit in git are the worst.
hjk101292731dThat's agile for you. People over process.
For real though, I've dealt with the same kind of senior developers. This stems from finding the whole version system a bother. Instead of seeing it as a great tool to aid the development process and tracing history (rime and reason) of the code. they see it as hampering their coding and commenting out sections as version history.
Their world view does not match development in teams or CI/CD driven development. Fortunately I'm also a senior developer, responsible for devops and a lot of pull with the board of directors. So I made a presentation for them and the directors with the comparison of the old and new way with some very pointy examples.
We used to have it all. Developer name and other long lived branches (calling me to solve the massive merge conflicts), commits with "Fix" or "." Commit messages. Massive commits with style changes, new features and completely unrelated bugfixes all in one commit.
This mostly changed (still see old code in comments) and devs are very happy with it.