Software development teams, for the love of software engineering, STOP splitting frontend/backend applications into separate repositories!

The amount of bullshit contract-level testing that you have to do just because of this is enormous!

Being able to re-use the same code-level symbol across layers is an advantage.

And no, making a `shared` repository somewhere else just amplifies deployment issues @_@

Pointing you at https://12factor.net/

"One codebase tracked in revision control, many deploys".

Extra points if you manage to use something like Nix to cache dependencies, avoiding full rebuilds of everything at every tiny change.

You can freely make a `frontend/` and `backend/` sub-dir in there, but at least it will change atomically.

Each cross-repository dependency you create inside a company leads to exponentially more work: https://en.wikipedia.org/wiki/Metcalfe's_law

The Twelve-Factor App

A methodology for building modern, scalable, maintainable software-as-a-service apps.

@ocramius Stop, don't move, photo is about to be taken in 3,2,1 second ! Click !

Now going to print this and put it all over the place at work.