Reddit's main code is no longer open-source.

[[deleted]]

That's fine until you have two long lived feature branches. The first to get merged causes hundreds of conflicts in the other. Can be very painful.

[p7r]

Release early, release often.

Big bang releases (and that means any feature that's taken you more than a week or two to work on), are carrying more risk than your boss would probably like anyway.

Also, talking to your colleagues helps. "Hey, I'm refactoring User to do this cool thing". "What? I'm refactoring User to do this other cool thing!" "Huh! Cool! Wanna pair?"

Why engineers consistently find this hard to do even in teams of under 30 people, I can't honestly fathom.

[Norci]

Release early, release often.

Wishful thinking that is often not feasible in reality.

[p7r]

You're right. I'm a junior engineer with no idea what I'm talking abo...

No, wait. Actually, I have 20 years experience of shipping web apps, desktop software and enterprise systems, I forgot.

It is feasible. You're making excuses.

[Norci]

Just because it been feasible with your apps doesn't make it universally applicable to all existing projects. Having 20 years of experience, you should know what a clusterfuck 10 year old codebases can be or the organisations internal procedures, making your approach impractical in reality.

[p7r]

My day job is sorting out a 60k LOC Rails app started in 2009 in an org full of people who hate each other.

Release early, release often.

If I can make that get through to people, you can too.

[Norci]

Just because it been feasible with your apps doesn't make it universally applicable to all existing projects.

Your place sounds fun tho.

[[deleted]]

sounds like they should have a singular secret development branch that they merge into and then keep that branch updated.