{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"North Meets South Web Podcast","title":"Laracon, controller middleware, and permissions","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/ede071f9\"></iframe>","width":"100%","height":180,"duration":3050,"description":"In this episode, Michael and Jake kick things off with some Laracon travel talk, sharing their hotel plans, coffee quests, and even jokes about pillow fights at the conference hotel. Michael reveals his precise coffee scouting for the Vib by Best Western hotel, determined not to survive three days on Starbucks alone.\nShould you define middleware in a controller’s constructor?\nMichael explains why he avoids it - preferring to keep all middleware in route definitions for better visibility and maintainability. Jake explores the pros and cons and why he’s still tempted to use it for certain edge cases.\nDynamic permissions vs. static definitions:\nWe switch gears to talk about the balance between flexibility and clarity when defining permissions for applications, especially when it comes to handling user roles, teams, and complex business rules.\nMentioned in this episode:\nLaracon US travel plans\nVib by Best Western (the hotel coffee and tacos!)\nLaravel middleware usage\nPermission handling in apps\nTravel gear for developers on the go","thumbnail_url":"https://img.transistorcdn.com/mT5S1gXia4pvcxxfbLvPcwUcyvwqS6tzlMWw5Ee-v0Q/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQ4ODMvMTU3Mjc3/NzAzNi1hcnR3b3Jr/LmpwZw.webp","thumbnail_width":300,"thumbnail_height":300}