News for hackers. Stuff that matters.
Re:Commit often, perfect later, publish once: Git best pract... by peakaboo on Sunday July 04, 2021 @05:34AM (#27728382)
Worth it for a few companies, but not for the majority. Most tests are also useless. Going for 100% test coverage is insanity. I think there is a lot of people in tech with autistic personalities who really hate when things are not perfect.
Re:Commit often, perfect later, publish once: Git best pract... by kossTKR on Sunday July 04, 2021 @09:25AM (#27729450)
True, i can also get OCD'ey vibes, myself included, i think it comes with mindset one fosters when looking at a screen for long. Same thing can also happen when doing Music or Digital Art, you can fell into a perfectionism loop, where you spend an exponential amount of time on smaller and smaller tasks, that no one will ever care about.

For lots of projects writing some quick end-to-end or story based tests is sufficient, maybe with some randomisation thrown in.

I honestly think the current framework hell we're in has pushed so many hyper-complex best practices that we just waste way too much time on perfecting process over actually coding - tests being one of the paradigms that has gone overboard.

Re:Commit often, perfect later, publish once: Git best pract... by phone8675309 on Sunday July 04, 2021 @10:44AM (#27729982)
A widely used, large framework having really good code coverage is important, especially if not everyone uses all of the framework.