3 ms·
I guess I could tell you but I also guess you will not understand. Have you ever had a bug in production on a site that can sell for 10 000 000€ on an evening j
by AtNightWeCode 6y ago
I guess I could tell you but I also guess you will not understand. Have you ever had a bug in production on a site that can sell for 10 000 000€ on an evening just cause some guy corrected a stupid spelling mistake? I have.
What I'm saying is that all these issues goes into the same funnel as everything else and get prioritized. If you feel that all these small issues is a problem. Fine, fix them. Otherwise, your senior developers will spend more time reading unnecessary pull requests about garbage than producing real code.
- tuwtuwtuwtuw 6y agoI don't have a senior developer, but I have a ton of people submitting pull requests to me. Sounds like you need to adopt testing. Isn't that part of Agile? Or was that in agile? Can't remember.
- AtNightWeCode 6y agoTo expect manual or automatic tests to cover all changes is naive. If people start to make changes that is not related to the actually task. The risk of missing something is kinda obvious. You (and the op) is barking up the wrong tree. Surely you have to understand it is not the fault of git that ends you up in this stupid situation. It is a broken process. Edit: grammar, not all :)