I’ve noticed that once you are up and running with a proper web application framework like Laravel, blindly using Cursor on it turns it into a nightmare. It feels as if the quality of answers has gone down over last weeks, but I’m frequently rejecting its suggestions. Often it’s got the SoC wrong.
Anyway, potentially better prompt engineering would fix it, or more training on Laravel framework specifically. Once it fully is trained on the Filament package, it will be amazing.
Some notes
- I am finding myself rejecting a lot of the Cursor agent advice… potentially because it needs training on some newer libraries I’m using; but also I do see the glaring errors it makes sometimes.
- Whilst LLMs are awesome, to mistake them right now for anything approaching intelligence is silly considering ARc2 is being passed at rates less than 5% by AI/LLMs. That really has blown me away. We will see in fall 2025 if anyone has come close. If they do, it’ll be a incredibly scary step forward.
- For traditional web frameworks, Laravel Filament still looking great. Todays development included:
- Mostly smooth configuration of import/export to CSVs on models within the Filament table panels.
- Got job queues setup
- Quality of life improvements to UI
- Notifications work great
- Laravel Pulse is quite good. I was having a few problems with CSV import jobs failing and then infinite retrying but this made me realise I wanted monitoring software asap. Pulse still requires someone to be observing however, and Sentry would still be obvious choice.
I’ll shortly be in a position to launch the very early version
Leave a Reply