Inherited project. Lots of things are very legacy, but trying to protect against session hijacking. Of course in the world of mobile even IPs can change. But that, at least, is understandable. I had thought of that but the user had the same IP throughout. Dynamic host names were unexpected!

My favourite was a database query that was slows molasses in prod but fine in dev. Turned out prod was running Postgres 12, and we had Postgres 13 in Sail. PG13 did a much better job of optimizing. Lots of hair lost. But never because of the framework itself!

The irony is waiting until an official Laravel VS Code extension is released to try PhpStorm. lol. Get Laravel Idea plugin as well.

Every path to learning is still learning. I’m not a front end guru so that’s my usual go to. It always needs more work but I gradually learn what is possible at least!

Sometimes the simplest solutions work best: technology is exciting and helps a lot, but it is not the solution to everything. Can an app identify the cans in my kitchen? Yes. Is that convenient to use in the midst of cooking a recipe? Maybe not.

👋 Fellow Canadian here flying the Laravel flag though I don’t get to use it as much in my professional life as I might want to. I do co-maintain github.com/jamesmills/l... as well!

At no age is cucumber water good for you. Now fresh lemon, lime I can get behind. Cucumbers should only be soaked in vinegar.
#teamPickle

If you forked it and then cloned perhaps you could keep it more updated that way. But rather like publishing blade templates from a package, this quickly becomes annoying to reconcile with your own app changes. I think the reality is a starter kit is just that… after that you do you.

Here's a quick n easy primer on writing alt text. If you're feeling time constrained even very brief notes is better than nothing, i.e. for this image "capybara in a hot spring". If there's zero alt text there's 0 context at all.

XOXO!