Astro Bot cool ! N'ayant que la Switch, je vais suivre avec toi cette aventure qui me donnait envie !

L'histoire est un original mélange d'aliens, de fantômes, de combats épiques et de romances improbables. Momo et Ken explorent des lieux hantés/extraterrestres et dimensions parallèles. C'est bourré de références pop culture, de clins d'œil aux classiques des mangas. J'ai adoré !

Le vendre c'est là où il y a le nomdril ?

WTF?!? On dirait une parodie !

Oh thanks for the insight! I hadnt thought about it that way before (maybe I'm overthinking it). This definitely gives me some new ideas to discuss with my teams.

I genuinely dont understand how these methods address quality control and team dynamics, especially with tight deadlines and pressure from the business side to move on to the next feature. Maybe I'm missing something?!?

Ask (open a pull request and wait for discussion before merging): What happens after it's merged? The ego factor comes into play. Devs (and even ProductOwner'n'co) are less likely to admit flaws or suggest changes after the code is already in the main branch. Plus wont this just move discussions?

Ship (merge without review): How do you prevent introducing serious bugs or regressions with this? Even with good testing, code reviews often catch things we miss. It feels like we're sacrificing quality for speed? which can be risky in the long run? How can we address that risk?

Thanks for sharing this! I get the idea of moving faster, but I'm struggling with the "ship" and "ask" approaches in practice.