Tips for Working in Dev-Team. Part 1: 5 Non-Laravel Tips

[@RustyNox]

This is exactly me in the last few months, from solo (business owner) to employment (team based). Looking forward to the rest of this series, very timely, cheers (:

[@PhillipMwaniki]

Git can make your life interesting. Rebasing, resetting has made my life hell at the moment

[@thecongvu6383]

Really great! Thank you so much!

[@CHSKnight]

Loved this. Thank you

[@Code2Master]

Amazing, thanks❤❤

[@sagarnaliyapara4660]

I agree on we should not have too much comments in our code, If comment is there then it is flag that code is not self descriptive

[@stefanbogdanovic590]

In readme i just put make setup, and put all commands in Makefile

[@hurairidzulkifli2886]

so good !

[@gram_o_phone]

Great, thanks! Quick Q: backend and frontend uses the same DB. Frontend is going to be developed further by freelancers. What would be the best practice: separate repository or just separate main/dev branches for front/back? Earlier seems cleaner but has issues with migrations/seeding. However backend does much more than handling frontend content, it's codebase is 20 times larger than frontend.

[@LaravelDaily]

It's preference of your team, it's how you agree to work and what is more convenient to you, there's no "one best practice" here, it's literally YOUR decision.

[@WhiteSiroi]

loved it, is there a part 2 ? cann't find it. thank you

[@LaravelDaily]

Yes, this is the video: kzbin.info/www/bejne/ZprIimCPotl6gaM

[@WhiteSiroi]

@@LaravelDaily thank you so much, love your vids, very helpful

[@haroldpepete]

y que jopo