I work in a similar environment. Most of our projects lifecycle we were 4 devs who knew each other reasonably well and all had high trust in each other. Unless it was a one-liner or a hotfix at 4am did get merged without a code review. Most if the reviews were just hitting the checkmark, things look fine done. But sometimes someone makes a mistake, as is human. In that case we caught it before it hit main.
- Posts
- 1
- Comments
- 27
- Joined
- 1 yr. ago
- Posts
- 1
- Comments
- 27
- Joined
- 1 yr. ago
IMHO it should not really mean shorter batteries. Might we loose 5% capacity or something like that for them to be more repairable? Probably.
But the option to manually replace the battery will - over the life of the device - outweigh that in my opinion.
My phone is now 4 years old - the main reason why I'm considering getting a new one is the battery life degrading. It still has ~80% battery health left - enough to get me through a non-demanding day but not enough for a more regular one.
If I could just replace the battery - I'd have done that already. But also I'll have to replace it next year anyways as it'll be EOL on security patches.