Smaller PRs make it easier to spot potential issues. A massive PR where all you see is a BIG chunk of consecutive red lines, followed by a BIG chunk of consecutives green line can’t be valuably reviewed unless the reviewer knows all the requirement in their head.

I don’t know who needs to hear this but recreating the lock file is not BAU. You are either doing something wrong, or using a terrible package manager.

Harry Potter spells are SO specific that they feel like admin commands to me rather than magic.

Alohomora: set lock false <objectId>

Avada Kedabra: set alive false <entityId>

Expelliarmus: set weapon null <entityId>

Reparo: set state $(get history state --last <entityId>) <entityId>

A scrum team, but it’s not just engineers. There are members from legal, marketing, security, etc. No centralized orgs dependencies. Features that take 3 weeks to be built are delivered in 3 weeks. No more built in 3 weeks, shipped in 3 months. Why is this not the norm? What am I missing?