mirror of
https://github.com/archtechx/laravel-tips.git
synced 2025-12-12 05:14:04 +00:00
initial commit
This commit is contained in:
commit
1beb9dd34c
281 changed files with 56773 additions and 0 deletions
14
content/tips/dont-just-write-procedural-code-in-classes.md
Normal file
14
content/tips/dont-just-write-procedural-code-in-classes.md
Normal file
|
|
@ -0,0 +1,14 @@
|
|||
---
|
||||
title: 'Don''t just write procedural code in classes'
|
||||
tweet_id: '1272822462040899584'
|
||||
thread_slug: laravel-clean-code-tactics
|
||||
author_username: samuelstancl
|
||||
images:
|
||||
- 'https://pbs.twimg.com/media/Ean2u-YX0AEmwEd.jpg'
|
||||
created_at: 2021-04-06T16:07:28+00:00
|
||||
slug: dont-just-write-procedural-code-in-classes
|
||||
---
|
||||
|
||||
This ties the previous tweet with the other tips here. OOP exists to make your code more readable, use it. Don't just write 400 line long procedural code in controller actions.
|
||||
|
||||
Here's code from my first Laravel project 😬
|
||||
Loading…
Add table
Add a link
Reference in a new issue