4 ms·

So, in Agile development it is important to do things in priority order. A typo should practically NEVER be fixed if it is not in the comments. So, this is not

So, in Agile development it is important to do things in priority order. A typo should practically NEVER be fixed if it is not in the comments. So, this is not a GIT issue. This is doing the wrong thing at the wrong time! And, I really, really dislike the term Boy Scouting. It is anti agile. The only result is usually that the none senior developers are changing things that simple is not important and causing new bugs. Formatting code etc, I'm fine with.

tuwtuwtuwtuw 6y ago
Is this sarcasm or.. I can't tell. Or is it "Agile" to never fix spelling errors because there's always a bug which is more serious? Is it agile to not vaccum the house because the toilet upstairs is dripping? Or am I mixing up agile with Agile now?
- 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 ago
    I 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 ago
      To 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 :)

tuwtuwtuwtuw 6y ago

Is this sarcasm or.. I can't tell. Or is it "Agile" to never fix spelling errors because there's always a bug which is more serious? Is it agile to not vaccum the house because the toilet upstairs is dripping? Or am I mixing up agile with Agile now?

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 ago
  I 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 ago
    To 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 :)