> Laravel lets you create migrations to manage the state of the DB
> your colleague doesn't give a flying fuck, just raw SQL on the db to perform every change
> performed initial insertions without seeders, can't reproduce his db on my local environment
> can't even run migrations anymore 'cause it would break everything

Take the frying pan of shame and explain your feelings in a way he understands.

Blame PHP

@kamen or don’t. Rarely is anything PHP’s fault (except in cases where the bug is caused by the wrong type of PHP array...) but the poor subpar devs’ who should either switch to a more restrictive language or consider a career change.

@100110111 so it's not PHP's fault, but people's for choosing to use PHP. Fast food isn't unhealthy, but choosing to eat fast food is

@eo2875 that’s one way to read it. Other way would be to become a better dev / hire better devs.

There’s nothing really wrong with PHP, and less with every new version it seems, apart from the two array types to be careful with and the lack of generics. I do avoid PHP frameworks like a plague, though. Those are not worth the pain.

@100110111 I was being sarcastic.

PHP doesn’t kill people, people kill people.