![Ditching a Microsoft Job to Enter Startup Purgatory with Lonewolf Engineer Sam Crombie [Podcast #171]](https://cdn.hashnode.com/res/hashnode/image/upload/v1746753508177/0cd57f66-fdb0-4972-b285-1443a7db39fc.png?#)
Using Traits and DocBlocks for Cleaner Architecture
I worked on a custom CRUD command that generates a Model, Migration, Views, Controller, Request, and Repository class. I created an Action class responsible for handling all CRUD operations. However, the class started growing too large — that was the first issue. To address this, I split the logic into multiple traits, and each trait handles a specific part of the process. These traits relied on global methods and properties defined in the main Action class, which became a major issue for me since I value code readability for myself and other developers in the future. Unfortunately, the IDE couldn’t recognize or analyze these methods properly. To solve this, I used PHP DocBlocks to document the shared methods and properties, which improved code readability and IDE support.
I worked on a custom CRUD command that generates a Model, Migration, Views, Controller, Request, and Repository class. I created an Action class responsible for handling all CRUD operations. However, the class started growing too large — that was the first issue. To address this, I split the logic into multiple traits, and each trait handles a specific part of the process.
These traits relied on global methods and properties defined in the main Action class, which became a major issue for me since I value code readability for myself and other developers in the future. Unfortunately, the IDE couldn’t recognize or analyze these methods properly. To solve this, I used PHP DocBlocks to document the shared methods and properties, which improved code readability and IDE support.
