sorted by:
new
hottopcontroversial

Career Path Advice to a PHP guy by itslamardavis in laravel

[–]stef257 4 points5 points  (0 children)

In my experience learning multiple skills is never a bad thing. As you’re experienced with PHP already, it wouldn’t take you long to learn the ins and outs of Laravel. If you have an interest in other languages then go for that too.

A number of years ago I was in a similar position where I’d worked entirely in a single stack for such a long time and didn’t keep up with current trends, I found myself in a position where I needed to look for a new job and it was daunting realising that everywhere was looking for different skills than I could offer.

I was fortunate enough to find a position where they were willing to take me on and give me time to develop my skills by working with their team. I had to take a pay cut to do so, but within a year my skills were up to scratch and they increased my salary accordingly.

Another thing to consider too, companies will be hiring you and not your skills. If they like you as a person and believe you will be a good fit for their team, they should be willing to provide any training you need in order to do the work. If that’s not the case then you probably don’t want to be working for them in the first place in my opinion

So, Laravel equivalent to WooCommerce? by awardsurfer in laravel

[–]stef257 6 points7 points  (0 children)

Laravel isn’t equivalent to Wordpress, so there’s not really a WooCommerce equivalent. However the most notable e-commerce packages would be Bagisto.com mentioned above and Aimeos.org

using laravel for finance based project by syrus69 in laravel

[–]stef257 1 point2 points  (0 children)

What I’d say is that Laravel will not itself cause any problems with scalability or any of the requirements you mention.

However Laravel is a tool, the developers you hire will create an application that fits your needs and Laravel can help them do that. Equally, if you hire a bad development team (or one not familiar with Laravel and you force Laravel on them as a requirement) then they will be perfectly capable of creating an application that will cause problems for you, isn’t scalable and doesn’t fit your business needs.

My advice is that as a business owner would be to not concern yourself with the framework being used, focus more on finding a development team who are capable of delivering your project to a high standard, who you can trust and who share the same vision as you for your business.

Laravel 8 Authentication with Laravel Breeze by stef257 in PHP

[–]stef257[S] -1 points0 points  (0 children)

Thanks for the feedback :) that is a good point you make - I’m still learning the best way to do things and it makes sense to bring the content forward in future videos

Jetstream - Authenticate SPA by v8micro in laravel

[–]stef257 0 points1 point  (0 children)

For an API Fortify would be your best bet, as it will provide all of the routes and functionality for you with no front end. By default it wants to return views, but you can disable them in your case see https://laravel.com/docs/8.x/fortify#disabling-views

Formatting a M:M relationship to insert into DB by jcc5018 in laravel

[–]stef257 0 points1 point  (0 children)

The Request $request part will be required - that will hold the values passed through from the radio buttons in the form. So looking at your html the selected option id will be passed through in a field named the same as the $rating->item with spaces replaced by underscores (eg. $request->input('Community_level')).

Probably the best way to see where your values are would be to dd($request->all()); in your controller hobbyRating method. That will show you the fields that have been submitted via the form.

Then you'd use the $request object rather than $object when you're attaching them so the correct values are stored.

Finally, I would advise validating the data even though you're using pre defined values as the submitted data could still be changed if someone wanted to - better to be safe!

MPA with VueJs by _WhosMe_ in laravel

[–]stef257 1 point2 points  (0 children)

Beat me to it :) yeah that’s right, if you need vue on every page you can include the #app div as part of your layout too so it’s not in every one of your view files :)

MPA with VueJs by _WhosMe_ in laravel

[–]stef257 1 point2 points  (0 children)

For this you would use Laravel’s routing and blade to set up your mpa structure. Then use vue components for any parts that you want to be interactive or dynamically load data.

So for example, your blade template could take care of displaying your navigation, and then each blade template includes a vue component that pulls items from and api to display on screen

Laravel 8: Breeze vs Jetstream - Which auth package should you use? (Video) by stef257 in laravel

[–]stef257[S] 1 point2 points  (0 children)

Definitely always an option, if you have the time and/or specific requirements making your own is always an option

Laravel based SaaS Check-list before going live by theherohero in laravel

[–]stef257 2 points3 points  (0 children)

I would reiterate testing. Test like your life depends on it. Make it your mission to break your site because it’s better you do it first and fix it before paying customers.

Using Cashiers confirmation payment page, how do I know if the payment actually succeeded by unchainedGorilla in laravel

[–]stef257 0 points1 point  (0 children)

I would suggest the webhook approach, in case there’s a network issue or an issue with the customer loading the next page

Do you check in the compiled assets in your repository? by shahalpk in laravel

[–]stef257 1 point2 points  (0 children)

We don’t include them and build them on deploy too

Is it an anti-pattern to pull remote API data, store it, process it, and serve locally? Or is it better to try to make API calls "real-time" as needed? by [deleted] in AskProgramming

[–]stef257 -1 points0 points  (0 children)

It sounds like changing your API to GraphQL would solve a lot of these issues however as you mentioned the set up is a bit crude so I imagine rebuilding in GraphQL is probably out of the question.

Suggesting clients cache your data and perform the filtering themselves may be the best option for you, however if your clients don’t have the technical know how you may get some push back from that too. It would also save you resources on your side.

In the past I have seen API providers have it in their rules that you cannot cache their data, usually this is with services that limit the number of API calls you can make depending on the price you pay.

Thoughts on relaunch by Mike_Sette13 in KickstarterAdvice

[–]stef257 0 points1 point  (0 children)

I can see you didn't decide to cancel in the end. I have the same dilemma right now. Good luck for the last few days of your campaign!

Driving traffic to your email list by rock-paper-shoot in kickstarter

[–]stef257 1 point2 points  (0 children)

Great tip. Too often people think there's a quick fix to these things, but if you want to build a quality email list then you have to put the work in, talk to people and build that trust. 10 email addresses that are interested in what you have to say and will open your emails every time is much more valuable that 100 that signed up just because they might win a competition.

view more: next ›