Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@juzles they used php for routing ... Everthing else was a hack around ... They didn't use migrations.... they didn't use migrations !!!!!!
-
lotd79228y
-
I don't use migrations. I always viewed it as optional since my design is in workbench. Is that wrong?
-
SithLord8508yI never used migrations too, until I realised that I couldn't live without.. no more losing data because of managing schema manually
-
sterex4388y@enchance Migrations allow you to bind the application changes to the DB changes and version them both. Otherwise, you'll have to remember to propagate the DB changes manually during each release.
This can be error prone and a maintainability nightmare especially if you want to rollback changes.
Consider moving to migrations. It's really not very difficult and I'm sure you'll appreciate the value it provides. -
@enchance it's not wrong but when you wanna work with many people it makes the process a lot smoother
-
minhaj3108yWow, 450 line methods, its really gonna be a long summer
btw, i am not gonna deny it so seriously what is "fml" here means
#i_am_new_here
Related Rants
My company took over a project that was previously sent overseas . (PHP, laravel 5.1) so I was pointed a lead developer in this project, when I emailed the "senior developer " from the previous company about version control and code documentation. He assured me there was nothing to worry about . ... I found 450 line methods without comments and as version control I found zip files with dates as the name ... fML this is gonna be a long summer
undefined
php
hell
laravel