What next

You've got enough Symfony to read a codebase and build a CRUD app with forms + auth. Here's where people usually go next - without me writing five more books in this repo.

Practice project ideas

• Notes app (you already did PDO CRUD - redo it with Doctrine + Twig forms)
• Tiny issue tracker (users, projects, comments, voters)
• JSON API for a Vue/React client + token/session auth you understand

Ship something imperfect. Reading alone doesn't stick.

Ecosystem paths (pick by taste)

Path	Vibe
Twig + Stimulus / AssetMapper	classic MPA, light JS
API Platform	serious JSON APIs, OpenAPI
EasyAdmin / Sonata	admin panels fast
Messenger + Scheduler	background work & cron-ish
UX packages	Turbo / Live components (server-driven UI)

If you love React/Vue SPAs - keep Symfony as the API + auth backend and stay in your FE comfort zone.

Laravel later?

Still valuable - friendlier defaults, huge starter-kit culture. Your PHP fundamentals + Symfony DI experience transfer; you'll re-learn Facades and Eloquent aesthetics. There's a Laravel twin tutorial on this site if you want that path next.

Habits worth keeping

• Join associations on list pages (kill N+1)
• Validate at the edge (forms / constraints)
• WebTestCase the auth boundaries
• Never APP_DEBUG=1 in prod
• Prefer injected parameters over scattered getenv

Docs that matter

• symfony.com/doc - actually good; use them
• php bin/console debug:* when lost - the framework wants to show you its wiring

You're past the scary part. Go build a small thing this weekend.

Wish you all the best.

Best,

-- ł.