| PHP & Laravel Articles | https://aaronsaray.com |
| Laravel Contract Dev | https://morebetterfaster.io |
It seems that every project we run into has missing or out of date documentation. Wikis become stale. Don’t even start me on that out of date README.md file. It’s almost not worth writing documentation because it gets out of date so fast. Right?
We always write tests, and can't imagine working without them. But is there ever a time where it might make sense to delay writing some tests until later in the project? Let us tell you a story about a recent project where we made that decision.Become a more confident Laravel developer. Sign up...
Awesome. You used interfaces so you can abstract out the dependencies and swap services. Your database queries are all built with an ORM that is database agnostic. You don’t rely on anything special with your servers/cloud. You did it! You now have a project that retains the business logic while allowing all the technical aspects to be loosely coupled! But should you have done it?!
Tips and tricks for working with Large Language Models like OpenAI's GPT-4. - GitHub - brexhq/prompt-engineering: Tips and tricks for working with Large Language Models like OpenAI's GPT-4.
Joel Clermont
