Youtube hearted comments of (@JinnGuild).

I'd want to add to the comment in this video about documentation -- Using TDD, we should absolutely be covering each explicit test case regarding the functionality of our code. Whether we're talking about the TDD a dev does using Unit Testing, or the TDD the team (Or SDETs or Automation QA etc) does with automated integration tests (functional, contract, whatever). Those tests describe exactly what is expected of the code, and those tests MUST CHANGE WHEN THE CODE CHANGES. Tests themselves are a form of documentation. Also, if we link test cases, cucumber, BDD, blah blah back to our User Stories, or Tickets, or other feature documentation, then there is a direct link of how the code is implemented to the feature being requested. Not to say that replaces 100% of code comments or other documentation, but it supports a massive amount of that requirement.
16
Work/Life balance is the hardest because it is rooted in nature. So that is where I mainly focus. Beyond that it is Rewards. Those two of your categories are things that require a lot of pressure to be put on the workplace management. Impact and Growth are heavily choice-driven by the individual. About Work/Life balance: At the beginning of adulthood most of us get jobs, as well as marriage and children. People have a desire to spend more time with their young children for the sake of precious childhood memories and raising them with strong foundations. As our children become young/adults, our time spent with them is still valuable, but more recreational and fun. Less foundational. The same goes for any relationship to some degree. Unfortunately, the Professional world works the same way, but moreso Requires you to spend a lot of time and energy early on to earn your stripes. As we get older and hit that juncture where we stop being worker-bees and become managers and/or consultants, we start to make our own schedules and the work/life balance shifts. But by that time our relationships are what they are, and our children are older. Though many of us never really leave the worker-bee phase. That is all a sad fact. But that's also why I focus a lot of attention on fixing broken processes and making work/life balance a real thing. Yes for all in general, but I admit I focus mainly on the people reaching those junctures and helping them push through into the management or consulting phase of their career.
13
@ainocorry3004 (or @ whoever wrote the script) - Great video. Overdue, and perhaps under-done. I think there was a lot of value lost in just reading the 22 year old (99% correct) manifesto. The second half of the video didn't make up for it quite enough. You can see in the comments the pushback that the Agile Manifesto says to deliver every couple months. Being who you are, and the namesake of your channel, it was a huge missed opportunity to mention how the Manifesto is over 20 years old, and the definition of "Continuous Delivery" has a more concrete or well-known meaning these days. Namely; that Continuous doesn't mean Iterative. Iterative is part of the SDLC and Teamwork, but Continuous is part of the Integration and Delivery. Wow would I love to have a chat and collaborate on working these types of details out, because I love yours and Dave's videos for the most part, and have such respect for you all.
3
Thank you for your Service. :D - The battles you have fought (as have I and a few others programming over 20 years) have brought us far. I hope that videos like this one really hope drive the concepts home for those companies and people who are doing Scrumfall or frAgile. Though we took a lot of great lessons from XP, such as Pair Programming.
2