Aurora bonanza last night. Joe needs fireworks?

Been using Laravel since 5.1. I’ve seen many MVC codebases from old CodeIgniter, .NET, Next.js, and new Laravel projects. Many developers seem to struggle with knowing where “the rest” should go. Everything ends up in the controllers or the model. Could a base project in Laravel make this easier? 🤔

After the wheel and antibiotics, the snow blower must be one of the greatest inventions.

Laravel developers, when looking back at old code—yours or others’—what common issues do you often see? I have my thoughts, but I’m curious to hear yours. This is about learning, not pointing fingers.

I think I have the nicest customers that is taking the time and write small emails like this. 🙏

Laravel devs: what are your goto solution for preventing form spam in these days? A captcha service? Honeypot fields?

No need create SPAs anymore for smooth transitions? (Only in Chrome and Safari preview). 🫣

Next week’s task: untangling a Laravel app from Spark Classic. It served us well—no hard feelings! I took precautions against this dependency six years ago, yet they’ve quietly spreading like a fungus here and there. Have you noticed how easy it is?

@mijustin.bsky.social
Alright, you got me into Bluesky. I’ve got high hopes for this, so no pressure or anything, but if this doesn’t work out… it’s totally on you. 😆

Got it! Here’s a more toned-down version:

👋 Hi everyone, new here.

I’m a developer and full-time startup founder, working on Laravel-forge-Menubar.com and the SaaS Moln8.se

Looking forward to seeing what this place is all about.