# retro Published articles for retro. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Managers Can Develop Team Leadership Through Meeting Delegation DevFeed: [How Managers Can Develop Team Leadership Through Meeting Delegation]() Original publisher: [Read original article]() Author: Ryan Murphy Published: 2025-07-14T12:00:13Z Content type: opinion Language: en Sources: [The Software Engineering Times]() Topics: [meetings](), [decision-making](), [trust](), [real-time]() Tags: [coaching](), [decision-making](), [leadership](), [manager](), [meetings](), [real-time](), [retro](), [support](), [sync](), [trust]() ### AI overview This opinion article argues that managers should avoid leading every meeting and instead give team members opportunities to run standups, retrospectives, and stakeholder syncs. It recommends providing preparation support, staying available, and debriefing afterward to develop independent leaders and reduce managerial burnout. ### Source excerpt Let's just say it straight. If you're the one leading every single meeting, you're either inexperienced, insecure, or haven't been shown how to be a real manager yet. If that stings a little, that's okay. Maybe it should. There are a few exceptions. Sure, incidents. Maybe a gnarly stakeholder review or a performance conversation. But even in those high-stakes moments, there's usually room to coach. Let someone else run the show. As long as someone is clear on decision-making, you don't need to be the one running the room every time. That's not what good leadership looks like. Good leadership is about building people who can do the job without you. Why You Keep Grabbing the Mic Most managers hog the meetings for one of a few reasons: It's faster if I do it They're not ready yet What if they mess it up? I'll be blamed if it goes wrong I'm the one accountable If that sounds like you, you're not alone. I've heard them all before. I've said a few of them too, early in my career. But you need to realise what those excuses are actually saying to your team: You're not ready. I don't trust you. I don't care enough to help you grow. Not great. What It Looks Like to Coach Instead This isn't about disappearing. It's not about sitting out. It's not delegating and walking away. It's about showing up differently. Coaching in real time. Supporting from the side, not from the front. Let them lead the standup. Let them chair the retro. Let them run the stakeholder sync. Then debrief. What worked? What would you do differently next time? What was hard? That's coaching. That's how they get better. That's how you build a team that can do hard things without you steering every move. The Real Reason You're Still Leading Everything Sometimes, it's not about fear. It's about ego. If everything runs through you If you always need to be in the room If you secretly like being the person with the answers That's ego. It's not sustainable. It's not leadership. It's how you end up with a team that ## Abstract and Open Classes DevFeed: [Abstract and Open Classes]() Original publisher: [Read original article]() Author: author@typealias.com (Dave Leeds) Published: 2023-08-21T00:00:00Z Content type: tutorial Language: en Sources: [Dave Leeds on Kotlin - typealias.com]() Topics: [Code](), [interfaces]() Tags: [abstract-class](), [classes](), [compare](), [delegation](), [extend](), [function](), [implement](), [inheritance](), [interface](), [interfaces](), [introduction](), [kotlin](), [learn-to-program](), [open-class](), [polymorphism](), [programming](), [retro](), [speed](), [subclass](), [superclass]() ### AI overview A tutorial chapter explaining how to extend open and abstract classes to create subtypes and share general code. It compares this approach with interfaces and delegation, highlighting that each has advantages and disadvantages. ### Source excerpt In Chapter 12, we saw how we could use interfaces to create subtypes, and in the last chapter, we saw how we could use delegation with interfaces in order to share general code among specific classes. In this chapter, we'll learn how we can extend open and abstract classes to accomplish these same things with a different approach. Each approach has its advantages and disadvantages, so we'll also look at how they compare to one another. ## My Retro PC Gaming Nostalgia Kick DevFeed: [My Retro PC Gaming Nostalgia Kick]() Original publisher: [Read original article]() Published: 2022-07-18T00:00:00Z Content type: opinion Language: en Sources: [Robin Ward]() Topics: [pc](), [Godot](), [Graphics](), [Programming](), [Assembly](), [C](), [3D]() Tags: [3d](), [animations](), [assembly](), [c](), [gaming](), [graphics](), [pc](), [programming](), [retro](), [videos](), [youtube]() ### AI overview The author reflects on making videos about early PC gaming and programming, including Sierra game graphics, palette cycling, 8086 assembly, Godot, and embedding old AGI games with C. ### Source excerpt Over the last couple of months, I've been posting a series of videos about early PC gaming and programming on my YouTube Channel. It's been quite a fun journey and I thought I might write a few words about it. I have a lot of nostalgia for early games, which makes sense since it was how I spent most of my free time in the 80's and 90's. Times were boring before the Internet :)