Brilliant! How nice to see you all here and to have this little archival piece of our first year. Great too to have Phil Nash on the recording.
📢 Episode 205 is out! 📢 In this episode, we record live from the first ever C++ Under the Sea! We interview Phil Nash about C++20 Coroutines, #Swift and upcoming conferences and also chat with Jonathan Müller about his P4329 reflection paper! https://lnkd.in/gA_Yuq5g
New Episode! "Unraveling the Shadow of the Erdtree" Summary In this episode, the hosts discuss the lore of Elden Ring and dive into the story of the DLC. They explore the characters' motivations, including Mikela, Radon, Moog, and Marika. They also touch on the role of the Hor...
New Episode! "Unraveling the Shadow of the Erdtree" Summary In this episode, the hosts discuss the lore of Elden Ring and dive into the story of the DLC. They explore the characters' motivations, including Mikela, Radon, Moog, and Marika. They also touch on the role of the Hor...
📢 Episode 182 is out! 📢 In this episode, we continue our conversation with Doug Gregor! We chat about C++11 variadic templates and pack expansion, C++26 pack indexing, tuples, variants, the Swift language and more! https://lnkd.in/g9rEpY6U
Why just focus on a mobility exercise? Create an exercise "flow" that will allow your client to work on gaining range of motion, but also learning to stabilize in that new-found movement. Full episode: https://lnkd.in/ekCiqBXZ
In all fields and in ours in particular, getting good at a skill set is hard, on multiple complementary skill set is harder, knowing where and when to apply those skills with an awareness of the business context you’re working in, to create impact for your team and/or the company, is a completely different monster to slay, M. Kelsey Hightower explains these ideas and principles in very simple frames (Activities vs Impact) (great episode)
🎯 Activities vs. Impact: Why Code Alone Isn't Enough! 💡 Hear more from Kelsey Hightower in episode 180 https://lnkd.in/d8X37VP8
Culture says you have to fake it until you make it. But, what if you didn't? What if there was a quiet resolve forged by the unchanging truth of who God called you to be? The latest episode of Grace & Audacity is now live! We're talking restoration from the inside out and the power of #quietconfidence. Watch now at https://lnkd.in/eqiXhk3v
Some BTS of our new Episode of "Read the Room" This episode was one of my favorites to direct! This BTS of myself Directing the sketch called "Can't hear the battle Speech" If you want to watch the whole thing check out the link below :D https://lnkd.in/gr5uVP2r
Achieving Maximum Precision with MAV Plate Rolls: The latest episode from the MAV series. Davi Promau https://ow.ly/3uFf50STzeS
In this new Baseworks Transmission Reflection episode, join Ksenia Shcherbakova, Baseworks co-developer, in exploring how enhanced perception leads to more effective actions. By highlighting the link between perception and action, Baseworks suggests that refining our perception can greatly influence the outcomes of our practices. Adopting jozef frucek's philosophy, the importance of receiving feedback in any practice is emphasized—if it’s lacking, revisiting your approach might be necessary. This principle is applicable across various fields, encouraging improved performance and understanding. Watch or listen to full episode: https://lnkd.in/gkk6jvZ7 #Baseworks #perceptionactionloops #ProfessionalDevelopment
Entrepreneurial DevOps Engineer | Balancing Technology, Craftsmanship, and Engagement to Optimize Impact
I recently finished episode 180 of the Tech Lead Journal podcast, featuring Kelsey Hightower and hosted by Henry Suryawirawan. Of the many gems in this episode, one key point stood out to me: learning the difference between "activities" and "impact". First - Thank you Henry Suryawirawan for consistently delivering inspiring content on Tech Lead Journal podcast. Your podcast is a significant source of inspiration in my day-to-day work, pushing me to re-examine my problems and context with a fresh perspective. Kelsey emphasized that to identify impact, we often need to zoom out and consider a broader time horizon. This is a crucial point that cannot be overstated. On several recent projects, I have started gathering data to quantify impact even before beginning work. This approach allows my team and leadership to see the tangible effects of our efforts over time. Tracking the change in metrics over time not only demonstrates the impact of our activities but also helps us determine whether those activities are achieving the anticipated results, fast enough. It's a powerful way to ensure we are not just busy completing work, but actually making meaningful change. I encourage all engineers to take a step back and think about what they can measure and demonstrate impact in their projects. It's not just about what we do, but the difference it makes. Why not create a compelling story about the (amazing) technical work we all do? How have you created metrics to quantify the impact of your work? Or have you encountered problems that were difficult to quantify? Share your experiences in the comments below! #TechLeadJournal #DataDriven #ImpactOverActivity
🎯 Activities vs. Impact: Why Code Alone Isn't Enough! 💡 Hear more from Kelsey Hightower in episode 180 https://lnkd.in/d8X37VP8
"that was the good era [...] because they invited me" Shots fired! 😂