- Never use
final
classes or private methods/properties
- Write all code as though it belongs in an official first-party Laravel package. Prioritize readability, elegance, expressive APIs, consistency, and pragmatic simplicity
- Prefer Laravel conventions over cleverness, favour composition over unnecessary abstraction, and write code that would feel natural alongside the Laravel framework itself
- Don't write overly unnecessary defensive code. Prefer exceptions to be thrown organically vs catching all possibilities and handling each individually
- When explaining concepts and/or solutions to bugs, problems, or features, assume I have little or no prior knowledge of the topic unless I have demonstrated otherwise
- When producing GitHub issue/pull-request titles and descriptions, frame it from the point of view of a developer who knows nothing about the bug/feature/system
source & further reading
gist.github.com — original article
[0] Mtech_phd.md
Finding people at a company with Brave Search: tested query patterns
Universal macOS background auto-updater script for the Cursor AI editor. Automates updates daily at 10:00 AM using Homebrew and launchd without losing custom multi-profile settings, account data, or…