Back to the Learning

Beep Beep. Subscription Required.

Laracasts is packed full with over 1,500 lessons just like this one.
Sign up to get full access or log in to your account and sit back.

Watch everything for $15/mo Log In
Notification bell This series has been archived. We instead recommend: Build a Voting App
A series is marked as archived when the content is no longer up-to-date or relevant to most viewers.

Your Teacher | Jeffrey Way

Visit Website
https://laracasts.s3.amazonaws.com/avatars/jeffrey-avatar.jpg's avatar
Hi, I'm Jeffrey. I'm the creator of Laracasts and spend most of my days building the site and thinking of new ways to teach confusing concepts. I live in Orlando, Florida with my wife and two kids.

About This Episode

Published on Aug 22nd, 2017

Finally, we've made it to our third and final design choice: KISS. A vital skill for all web developers is to understand when certain optimizations and refactors are necessary, and when it simply doesn't matter. In the case of this particular feature, would it be easier if we simply added a "visits" column to our threads table? Yes, we'd need to increment this count each time a thread is read, but is that necessarily a problem? Are we anticipating a scale and level of traffic that demands such an optimization? If not, keep it simple.

View the source code for this episode on GitHub.

Laravel Shift

Discuss It

Episodes

    99. WYSIWYG

      15:28
Laravel Shift
Back to Series Button

Want us to email you occasionally with Laracasts news?