James LaChance
3.3K posts
James LaChance
@FatBoyXPC
I'll most likely be found playing with Rubik's Cubes, playing FPS games, driving my MR2, taking pictures, or nerding out in some form of programming 🤣
Tampa, FL Katılım Ağustos 2012
196 Takip Edilen231 Takipçiler
@FatBoyXPC You can build this already. Just part of your deploy script. But it could be automated pretty easily with an extra DB column and config option.
English
I’d go so far as to say migrations themselves are unnecessary. At least beyond their changeset. Once applied, they should be removed and the latest schema should be snapshotted. There’s no reason any application should run hundreds of “old” migrations in sequence.
Freek Van der Herten@freekmurze
I never write down migrations. Down migrations are the least tested code in any Laravel app. They're written once and never run. And when you do need to roll back, you don't know beforehand what you need to do with the data would already be stored in the updated schema.
English
@gonedark An interesting idea, though! I've been giving this thought and I feel like this could work if doing this on maybe a release or two after the migration goes to prod
English
@FatBoyXPC That's kind of the missing link keeping this a "manual workflow task".
You could determine this when `migrate` is ran in the "production" environment. But then production would need to "commit" back (which is strange and has implications). So, again, just an idea...
English
@martinbean @gonedark Because when you stand up a new environment you do in fact run hundreds of migrations. If you run tests using refresh database trait or migrations trait, you again, run hundreds of migrations.
In contrast with git where these text files do nothing until you decide to view them
English
@FatBoyXPC @gonedark And what “cost” is that? They’re text files that are less than a kilobyte each. If that’s a cost too high to bear then your eyes are going to water when you see the “cost” of your Git history. Best get all those commits squashed pronto!
English
@martinbean @gonedark These are very different things. The cost on keeping migrations around is greater than not squashing commits. Now, I'm not convinced the approach mentioned is how I would prefer to do things, but I've also never tried it.
English
@gonedark An application doesn’t run “hundreds” of “old” migrations in sequence; just any outstanding ones.
Curious: do you constantly squash your Git history after each commit? Just there’s no reason a developer should be running hundreds of old commits based on that logic.
English
@jesseleite85 @gonedark This is correct, and is one of the reasons I didn't understand why people say they like to uninstall it. Like, if you don't want to use their syntax, fine, but the test runner is still awesome.
English
@gonedark I'm in same boat! Super excited to use Pest 4's sharding in our github actions.
Did a little test w/ Statamic, and I think you can even just use Pest's runner to run all your oldschool phpunit tests. Don't think you have to convert all your tests to the new syntax at once 🔥
English
I haven't converted to Pest yet. No reason really. Just going with what I know.
But I'll give Nuno credit. He's stacking more and more features onto Pest that make it a no-brainer. Pest v4 might finally get old JMac.
English
@jtregunna @2disbetter @dhh Yeah, I've had stuff like configuration for formats change but you get warnings for it unless you do what your said haha
English
@FatBoyXPC @2disbetter @dhh Yeah stuff tends to break more when you leave it for 3 months between updates. Do it as part of a weekly thing, and very little breaks if ever.
English
We moved to Linux as the default for new dev hires at 37signals a while back. Our setup flow complexity collapsed. It's just so much easier to automate everything on top of Linux than on Mac. And for our work, Linux is also just way faster since we use Docker for DBs etc.
Richard Stafford@rsstafford
Linux desktop setup up and running with Omarchy, thanks to @dhh efforts and recommendations. Been on Macbook for years, seriously considering moving Dev team to Linux, all tools we use confirmed working on Omarchy. Combined with Beelink SER8 its a powerful setup at a fraction of the cost. Way more flexible single keystroke context switching between project envs with Hyprland. 👌
English
@2disbetter @dhh Arch full time for 8 years and nothing has broken for me due to rolling releases. The only major catastrophe I'm aware of is when they decided to default python to 3 instead of 2. I find the fear of rolling releases largely unfounded for desktop use. Nix makes it even better.
English
@dhh Your confidence has got me using Linux on the Framework 12. I would love to use Omarchy BUT really prefer an LTS distro, because crap just breaks too much on rolling releases. Anyway thanks for the inspiration and also for Campfire!
English
@taylorotwell @LaravelWorkflow @ButscH @buggregator Lol I love when I find people that geek out over nonsense benchmarks like this, then end up writing very inefficient database queries, which in my experience, is super common among teams where multiple languages is relevant.
English
James LaChance retweetledi
@ButscH @buggregator Dude. It doesn’t matter if your framework is 3x faster if it’s 10x shittier in every other conceivable way. ✌️
English
#Laravel is amazing #php framework, until you start building something which require multiple teams/languages communicate over set of strict conventions. In that case high coupling will play a bad joke with you. Thats why I switched to #spiral framework and #roadrunner.
English
@rissa_bubbles @timacdonald87 @LaraconUS You definitely could! I was just able to be part of your journey!
English
@FatBoyXPC @timacdonald87 @LaraconUS Thanks James! So glad we finally got to meet last Laracon after so many years of being friends!
I don't think I'd be here without you and your mentorship!
English
James LaChance retweetledi
So excited to be speaking at @LaraconUS for the second time! Such an amazing lineup and I'm so excited to listen to all the amazing talks from those awesome speakers! ❤️
Taylor Otwell@taylorotwell
So many awesome speakers confirmed for @LaraconUS. Can't wait hang out with you all and share what we've been cooking. 👨🍳 Some new speakers: - @willking - @colindecarlo - @jbrooksuk - @LeahTCodes - @inxilpro - @johnrudolphdrex - @dhicking - @timacdonald87 - @rissa_bubbles - @TMoney1371 laracon.us
English
@iBotPeaches I dont really know where those settings are at. I play through steam rather than Xbox store, but I can try to remember to take a look at them and enable them. Thanks!
English
@FatBoyXPC Just my luck a Laravel engineer finds a bug in a Laravel app. Looks like you have some heavy privacy settings enabled so I can't pull data.
I can get some basic overview stats and thats about it -leafapp.co/player/FatBoyX…
English
Working a new Leaf feature for Top 3 specific to each Playlist.
Have a few bugs still, but its coming together. It helped me find a ton of cheaters not yet marked as banned.
Also if you are farming medals against people going 0-90 you are getting the "farmer" badge.
English
@iBotPeaches Twitter did a horrible job of sending me this push notification but I'll give you one guess 😉
English
@iBotPeaches Yo! I just checked this out and it doesn't see anything for me except one tactical slayer from July 2022, I'd love to see some stats though!
English
They also just renamed Husky Raid -> Husky Assault in terms of the playlist. Which is odd. So CTF stats mixed with Assault.
English
@sir_brian_d @taylorotwell Pretty frequently here, and it's annoying enough I don't particularly enjoy different databases under test vs production.
That said, if Laravel were to ship with it, that's fine, as I'm changing test config from new Laravel applications regardless.
English
Should these two commented lines be uncommented so that a SQLite in-memory database is the default when running tests on new Laravel applications?
English
@gonedark @JacobBennett I much prefer writing code that doesn't mock anything like this, then these false positives won't even be relevant
English
Using `shouldReceive` can lead to false positives when used without a quantifier, like `once`. It's better to form the habit of using `expects` - which is an alias for `shouldReceive->once`.
Think of `expects` like MUST. Whereas `shouldReceive` is SHOULD, but doesn't have to.
English
@BWay124 @MikeBenzCyber Are you going to share access to that?
English
What document are you seeing in the New JFK files that links it to tick born viruses?
Operation Mongoose is in there.
I built a LLM service to chat with that has all 1123 documents in plain text, and summarized with Grok via api calls that I can talk to in plain language with vector databases backing it all.
No reference of viruses, lyme, or even a general carter in new files? Any PDF link should have the id.
English
Shocking reveal in the new JFK Files that basically confirms the Pentagon creation of and intent to deploy the tick-borne viruses (Lyme, etc) detailed in Kris Newby's book Bitten
Benny Johnson@bennyjohnson
🚨Mike Benz DIVES DEEP into how the Pentagon Created Lyme Disease 60 Years Ago in the SAME Lab as COVID: “The military was funding the tick viruses in the same lab as COVID… It’s the same playbook.”
English