Yeah it's a scam. They'll claim they lost all the money that went into making the movie because no one would buy it for the price they wanted. If they'd sold it for the highest offer, they'd have lost less.
How is that any different than burning down my own building and claiming it as a loss in my taxes?
As I've gotten older, I've come to appreciate shows that do a tight story in six to eight episodes. Many shows with 16-24 episodes per seasons always add in filler episodes that only need to exist to sell more ads over the course of the season. And shows that drag on season after season eventually lose the plot.
Remember Lost? One hundred and twenty-one episodes only to drop entire plot lines, mysteries, etc.
Is it fair to say that your process has stabilized in a good place? It sounds like your team is happy with the current way of doing things.
I think that's largely true. Not trying to assume intention, but I do think a few more of the junior folks on the team read something in a book or blog and think we have to do it that way. Or that it'll work for us because it worked for Etsy/Netflix/ThoughtWorks/etc.
Whenever I read about kanban, the author eventually talks about gathering metrics so the team can run experiments and see what happens to the metrics.
You know, metrics might be a great way to discuss some of these concerns/ideas are coming up. For example, the topic on Jira was related to Cycle Time. If we were concerned about Cycle Time, changing how we use Jira for a few weeks would see what happened to the metrics.
Thanks for helping me reframe my thoughts. I definitely don't want to call anyone's concerns unimportant.
More specifically, I view retros as a time to talk about improving the team, either through experimentation or doubling down on good practices. To that end, I'd want topics to be problems or shout outs.
Something like "how do we test credit cards" might be a sign of "our documentation isn't great and it slows me down" but it's talked about as a discreet item. Similarly "I haven't seen Jira used this way before" isn't a problem; maybe the underlying issue is "I don't understand how we use Jira" or "what we're doing causes a lot of paperwork"
I want the creators I watch on YouTube to continue to get paid, both from YouTube and their sponsors. My contributions through premium are sliver of what they see, but if everyone stopped supporting them in that way, the total would be zero.
I back some of them on Patreon where I can, but it's not economically feasible for me to back them all in such a way.
The fact that Google started as a search company and yet search in their own apps sucks is boggling.
In YouTube Music, when you're building a tuner to create a station, you can't search at all. Instead, you get an endless scroll off bands and have to find the one you want that way. The order is random.
Like .. Pandora let you do the same thing with search back in the 00's
I'm glad I worked at a startup without benefits while I still had coverage from my parents. I'm also glad I realized I prefer medium-sized companies before I lost that coverage.
I regret the mentality that kept me at shitty jobs for five years. Being afraid the grass wouldn't be greener left me in a cycle of getting mad enough to polish my resume and send it out, but then never really following through.
Well yeah, if you go on strike when your union says you shouldn't, you're going to lose your job.