Lazy Loading a Laravel Model relationship through a repository

If your Laravel Model needs access to repository for pulling relationship data, think again.

It’s the wrong way round, don’t do it. Your models need access to data without any N+1 issues from using Lazy load. So if you need to merge some data streams and return a collection, rather than use a repo call to access each stream object; Create a view table which `Union ALL`’s the data various models. Then the model can have lazy load access to all the things you need, and the laravel commands, `->with()` or `->load()` can work without slowing it all down

The Rurbric for Digital Handins

What does the Rurbric look like for a digital hand-in with no specified medium of hand-in..?

If it’s ok to hand in a Twitter Stories wall, video, pdf, PPT, IOS Game, Website, chatbot…

I know it’s really un-realistic, and students shouldn’t be handing in things that aren’t going to get the points (otherwise, what’s the point) but I did just wonder. I suppose the medium doesn’t matter, as long as it’s going to get the marks and express / show the learning and effort.

But then, when is a Twitter Stories wall ok?

Should you allow clients into your bug tracking software?

I believe yes, you should. With the proper caveats and training, your client should be able to see what’s going on.

The client has fewer surprises, is in on the problems and #FTW’s. They feel more connected to the product and weirdly will start to feel more “onside”.

Sure it might seem scary at first, but after the initial storming, the process does begin forming!

It’s all about improving process through transparency.