😗KISS

Keep It Simple, Stupid. Even if the solution looks stupid, a simple one is better than a complex one. This principle encourages writing clean, simple, and maintainable code. Instead of overcomplicating logic, you should break down tasks into smaller, reusable, and structured components.

Routing (Follow RESTful Conventions)

Use resourceful routes instead of defining each route manually.

❌ Bad Example (Manually Defining Routes)

Route::get('/users/all', 'UserController@getAll');
Route::post('/users/create', 'UserController@store');
Route::put('/users/update/{id}', 'UserController@update');
Route::delete('/users/delete/{id}', 'UserController@destroy');

✅ Good Example (KISS Applied)

Route::resource('users', UserController::class);

✔ Why?

• Uses Laravel’s built-in RESTful methods.

• Reduces redundancy and improves maintainability.

---

Controllers (Short & Focused Methods)

Keep controllers clean by separating validation and business logic.

❌ Bad Example (Controller Doing Too Much)

public function store(Request $request)
{
    $validated = $request->validate([
        'name' => 'required|string',
        'email' => 'required|email|unique:users',
        'password' => 'required|min:6',
    ]);

    $user = User::create([
        'name' => $validated['name'],
        'email' => $validated['email'],
        'password' => bcrypt($validated['password']),
    ]);

    return response()->json($user, 201);
}

✅ Good Example (KISS Applied)

public function store(UserRequest $request, UserService $userService)
{
    return response()->json($userService->create($request->validated()), 201);
}

✔ Why?

• Uses UserRequest for validation.

• Uses UserService For business logic, keep the controller clean.

UserRequest (Separate Validation)

class UserRequest extends FormRequest
{
    public function rules()
    {
        return [
            'name' => 'required|string',
            'email' => 'required|email|unique:users',
            'password' => 'required|min:6',
        ];
    }
}

---

Models & Eloquent Queries (Use Scopes & Relationships)

❌ Bad Example (Raw Query & Complex Logic)

public function getActiveUsers()
{
    return DB::table('users')->where('status', 'active')->orderBy('created_at', 'desc')->get();
}

✅ Good Example (KISS Applied)

public function getActiveUsers()
{
    return User::active()->latest()->get();
}

✔ Why?

• Uses Eloquent scopes (active()).

• Uses latest() instead of manual sorting.

User Model: Adding Scope

class User extends Model
{
    public function scopeActive($query)
    {
        return $query->where('status', 'active');
    }
}

✔ Now, you can call:

User::active()->get();

🚀 More readable, reusable, and maintainable!

---

Service Classes (Encapsulate Business Logic)

A service class helps keep controllers lean by handling business logic separately.

Example: UserService for Business Logic

class UserService
{
    public function create(array $data)
    {
        return User::create([
            'name' => $data['name'],
            'email' => $data['email'],
            'password' => bcrypt($data['password']),
        ]);
    }
}

✔ Now, the controller only delegates work to UserService.

---

Blade Templates (Avoid Logic in Views)

❌ Bad Example (Logic Inside Blade)

//blade
@if(Auth::user()->role == 'admin')
    <p>Welcome, Admin!</p>
@endif

✅ Good Example (KISS Applied)

// In User model
public function isAdmin()
{
    return $this->role === 'admin';
}

//blade
@if(Auth::user()->isAdmin())
    <p>Welcome, Admin!</p>
@endif

✔ Why?

• Moves logic to the model, making the Blade file cleaner.

• Improves reusability across the application.