Sounds like one I had to deal with for a while. Had a mix of codeigniter, zend, angularjs (1.x), two extra node servers (because some people didn't want to deal with the mess that was the PHP side anymore, so started porting stuff, never finished).

On the front end, each page was a separate angular application, where PHP was used to render javascript objects into the global scope, which the corresponding angular app picked up to hydrate.

An API endpoint could be in one of 3 repos, you had to search stuff you saw printing out or getting returned, to find where.

PHP side used raw SQL, then there was a node app that used raw SQL, and then another node app that used ORM (sequelize).

These would call each other in completely undocumented and unpredictable ways.

On many pages, half of the database was pulled straight into the browser so that there's no need for complicated endpoints to fetch the required data.

Summary: If you can't move to another project, don't bother for too long...

@FrodoSwaggins Yeah, that's sort of what I'm planning to do. Get those offers in the door and make a decision before going offline for a month or two.

@theuser Wondering if they brought the issue up with Linus Torvalds yet, as master is a Git default, rather than a GH one. Let's also remember the huge amounts of direct and indirect references to master, all the tutorials, books, guides, documentation, etc that assume master to be the default, or by accident. Not to mention build/test/deploy pipelines. The next logical step would be for Google to start penalizing resources where master is used instead of <correct-name>.

Has anyone ever talked to / read a complaint from someone who felt oppressed while working with or seeing a master branch? Who came up with this shit first? Do we have a root source for this mess? Some SJW blog post or something? Even if someone's actually offended, why should that be a reason to offend the intellect of so many more with stunts like this?

Let's go ahead with this, but I also suggest other git hosting companies to all adopt different names, so that people can congregate on one of these services depending on their default branch, forming new religions. I suggest adding your preferred default branch name to your CV, that way you can signal virtue on there too, even without charity work experience.

@miksaraj I hear you. No intention of letting it get out of hand more than it currently is. I can still go on for a while (and I'll have to, my notice period being what it is), but I obviously have no desire to try and fix things, I've been trying for the last couple of years... you get small wins sometimes, but there are fundamental issues.

@heyheni Yeah, we absolutely need at least one dev, ideally two. We're hiring a dev this month, which is good. Used to be 3 of us when I joined, I'm the only one left. Had another person on a completely different project which was also too big for one person, he left recently. That project was also "the future", it's an iOS app which is supposed to be a more "premium" way to access our services, but is actually way inferior to the website in every way. I warned them not to push the app because we'll have to maintain two things instead of one, and building new stuff across them will be a mess. Nope! Now we have an inferior app that's being left behind, yay.

To be honest, I'm supposed to be the manager you're referring to (in addition to being lead dev). It's just ridiculous to try and manage my own workload that way, when it's only me.. And trying to do that is just more stressful than coding to be honest. We do have a contractor designer though.