A monorepo refers to a single repository in your version control system that holds all of the code for an entire project. That project could be made up of many services, front and back end code, ETLs, etc.
There are many technical arguments for using a monorepo vs a bunch of smaller repos that are more targeted to that functionality. But, one argument is often left out of the discussion.
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?
I don’t do hourly billing (if I can help it) - but most businesses and partners still ask about my hourly rate. Hourly billing is bad. There are so many reasons. But in this article I will just focus on one: you get the worst results with hourly billing. Let’s find out why.
The other day I was troubleshooting some code for a form in Laravel that was using a PUT method. Turns out the previous developer had not understood - and I had missed - that the @method override was missing. So I got to thinking - what if we made a form component that handles this for us? Is this a good idea?
I use Things for my todo list. I like it, but I don’t like the voice control. You have to say “Add I want to buy candy to my things 3” - sometimes you can leave off 3. This works sometimes - but for longer things it’s not great. What’s an alternative? I got one - and it’s way better.
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?!
Ever open a file in VSCode and get annoyed by all of its highlights of your code, or find that it has mis-identified the content? Sometimes it’s just easier to turn off the language highlighting in Visual Studio Code. It’s simple:
It’s nice that you can customize the 4xx/5xx error blade files if they’re published in Laravel - I like that. But what if you want to access the current user - or even use your standard layout - for the not found / 404 error? It’s actually quite easy. Let’s check it out.
What do you do when your website looks great to you - but others say the text is hard to read and the image is grainy? Well, because of this specific reason, I use two monitors always - one with a higher resolution and one with less. So, as it turns out, there’s a way to make both resolutions - and people - happy. Let’s see how.
The specific challenge is to sort users in a Laravel Nova application by their role. For this specific example, though, we have a number of assumptions. Although this article solves this very specific problem, you can probably extend it to apply to other custom data challenges in Nova. Let’s check it out.