Once again Bran, I love it! ... I've been bikeshedded so many times, while others breeze by with their fancy industrial nuclear fission factories ... It really doesn't matter they are fictional. 😂 To be frank: Sometimes I just want a bike shed somewhere, experiment, practice and leave the context for what it is. Focus on the material, make art in code, or real life. One should be able -within reason- to lose them selves in the beauty of a great bikeshed. I do get it though. I never ask for microphones anymore, but a multi camera live setup. Speaking off: Love to get a studio tour some time. Keep it up!
Of course experimenting and practicing is good! If you're actively doing that, it's not bikeshedding right? It's having a different goal :) The studio/gear tour will come someday, once I'm ready for it. Thanks for watching!
I've been stuck for a couple of days with going back and forth with endless code reviews about removing comments, variable naming conventions etc.. still trying to merge xD , the worse is that between each reviews and commit I loose hours waiting the reviewers.
I recommend pair programming instead of working alone and then doing a code review. But if that's a step too far for now, discuss with your team in a retrospective how you can minimise waiting time and handovers, and explicitly mention your frustration with waiting time.
Great topic! Thank you so much for your explanation and reasoning about this topic.
Once again Bran, I love it! ... I've been bikeshedded so many times, while others breeze by with their fancy industrial nuclear fission factories ... It really doesn't matter they are fictional. 😂
To be frank: Sometimes I just want a bike shed somewhere, experiment, practice and leave the context for what it is. Focus on the material, make art in code, or real life. One should be able -within reason- to lose them selves in the beauty of a great bikeshed.
I do get it though. I never ask for microphones anymore, but a multi camera live setup. Speaking off: Love to get a studio tour some time. Keep it up!
Of course experimenting and practicing is good! If you're actively doing that, it's not bikeshedding right? It's having a different goal :)
The studio/gear tour will come someday, once I'm ready for it.
Thanks for watching!
love the topic
Nice Maslow programming piramid
I've been stuck for a couple of days with going back and forth with endless code reviews about removing comments, variable naming conventions etc.. still trying to merge xD , the worse is that between each reviews and commit I loose hours waiting the reviewers.
I recommend pair programming instead of working alone and then doing a code review. But if that's a step too far for now, discuss with your team in a retrospective how you can minimise waiting time and handovers, and explicitly mention your frustration with waiting time.
@@branvandermeer that's what I was thinking about, just have a call and fix the minor issue right away.
Noo! No more calls! Code reviews are the place to discuss that. Just use automated linters and QA tools for trivialities.