@rudrakvelkara I was exactly the same, problem is, most senior devs will humiliate juniors for asking semmingly dumb questions which isn't good. Stackoverflow is a great example and the site policies seem to indirectly encourage this.
@_newtonjob@SuDevelopers I'm surprised you are of the opinion that simple good practice that results in testable code and a separation of concerns is a recipe of disaster and is even an optimisation, still cool I guess.
@_newtonjob@SuDevelopers I'm a firm believer that controllers must always be dumb from the get go. Data should simply flow in and out with the action or service handling it, anything else is a recipe for disaster in the long term if the project is meant to scale.
@_newtonjob@SuDevelopers I have to disagree. Imagine the refactoring you would have to do if you need to implement the same endpoints in your web.php for an API if logic is tied to your controllers, not to mention violation of DRY.
@_newtonjob In most cases, the user is notified of the same message in the email by SMS and/or push notifications etc. simultaneously, so Notifications are usually better for code organisation