Hi there,

There is another way of localization -> you can find in detail information here: https://laravel.com/docs/12.x/localization

Basically, you can edit those default files, but I would advise against editing the default files unless your app trully needs (the localization parts).

Best regards

Hi there,

First that comes to mind is Laravel + Inertia (Vue or React) - it is super easy to make such things with components and props that refresh on change (Inertia is super good for this).

Maybe check those out.

Best regards.

Hi,

For dev/staging/prod environments I really suggest you try out Docker containers, as it allows you to mimic all the different server setups. If you have a client that already has a server (controlled hosting or a VPS) you can mimic their setup, even install docker on it and not worry about the environment.

As for the staging part itself, my workflow is to have a subdomain with all of the llms.txt, robots.txt, even hardcoded ips in the .htaccess so that I am sure that noone that is not allowed access the staging environment.

Hope it helps a tad bit.

Hi @snapey ,

Thank you for those words of wisdom. Those two lines - "Do not assume they cannot afford it" and "They are not paying you to do the job, they are paying you so that they do not have to do the job" - pure revelations, shifting my mindset when it comes to thinking of bureaucracy.

Yes, the experience part is what I am struggling a bit, but that will come with time (and actual work).

Do you write detailed specifications or just a high overview of the minimal functionalities? Do you do them in word/pdf or some other helper software?

Thank you so much for this.

you have to invest some time to create sales, whether that is writing proposals, attending calls, research, etc etc.

So some of what you earn has to be put to one-side to reinvest to win more business in the future.

This is all down to experience unfortunately, both in sizing of the project and knowing which projects to chase.

Early in my career, someone said something to me that has stuck and that I remind myself over and over "Don't assume they can't afford it". Its far better to let them tell you your price is too high than to make the assumption and cut your price before you even ask.

Also when pricing remember, they are not paying you to do the job, they are paying you so that they don't have to do the job.

Regarding contracts and specifications, you don't have to repeat it, just have the contract reference the specification(s) (versioned).

Ah, that is a nice one, getting paid for specification (the discovery phase) - that way, even if you do not land the project, you got something for your time. That is a perfect one I have not even considered.

Yeah, if the client picks you for the project, you can decide if you want to give them a "discount" since they already paid for the proposal and specification.

Nice, thank you so much for this, this is going into my SOP :)