@pixelcave_john I think this is the most common scenario. And sometimes you might need to plug in the production database into local … and then the disaster happens 😄
@haztakki@calebporzio Same here, after I cleared views, the error was gone, but had other sort of issues like modals not opening for example. I removed blaze for now, will give it a new try in the next days.
@benjamincrozat I think that most of the positions have like 2-4 weeks severance / heads up. A few months could be too much for a small company. I think that a few months is on the table for bigger companies with mass layoffs (collective contract etc.).
@michabbb@simonhamp Or finding a random n+1 query … I mean .. that’s not because the tool is great, but because your code is bad, right? Anyway, I installed nightwatch and it’s a nice tool, that could be useful in some scenarios.
@christophrumpel For me, things changed - after watching the show, I couldn’t imagine the characters looking any different when I read the last books. But that’s just me :) Anyway, the show’s awesome too - you can watch it after you finish the books.
@jessarcher @laravelphp Hey @jessarcher, it seems it's working after I specifically added NIGHTWATCH_INGEST_URI=127.0.0.1:2407 on the 1st app, and also the demon having the listen-on flag. However, I thought these were the default, so it should have be working? 2nd app had it right from the start.
@karakhanyanS@PovilasKorop Same here, but in my case it was because of the number or SQL queries - running a lot of jobs with constant data manipulation, so I had to disable it using NIGHTWATCH_IGNORE_QUERIES, and use Nightwach for the rest of the features only (for now).
@benjamincrozat Couldn't agree more. It's similar to other tools/frameworks etc. if you use it right, you get good results. My experience is great so far: small components, keep data at a minimum, don't use live models unless really necessary.