How should I go about fixing build errors?

Question

Should I fix my build errors as soon as I get them ? Or should I (let's say) try to fix all of my errors every week or so ? Or should I just code the majority of my app and then try to fix all the errors ?

In other words, how often should I be trying to fix all of my build errors ?

I find it's easier to fix errors as soon as they happen, as you will not be able to build your project if any errors are present. I also try to keep any warnings to a minimum as I go. — digitalHound, Aug 12 '15 at 21:06

score 1 · Accepted Answer · answered Aug 12 '15 at 21:06

1

I would consistently try and fix errors as you find/create them, and focus on making a compiling and running application with each individual change you do.

If you are using version control, focus on making each change set a running application, even if some of your stuff isn't finished yet.

answered Aug 12 '15 at 21:06

72A12F4E

1,744
1
14
28

Thanks for your answer – Jack Berstrem Aug 12 '15 at 21:09
You should also fix warnings immedeatly because the more warnings you have the sooner you will overlook the warnings which are really important. – Darko Aug 12 '15 at 21:50

score 0 · Answer 2 · answered Aug 12 '15 at 21:40

Generally, my personal rule is that I don't allow a commit with errors in it. Normally I'll make a commit when I finish a feature or portion of a feature. After I finish roughing out a feature, I'll "cleanup". This is where I format my code, optimize things, and remove warnings.

How should I go about fixing build errors?

2 Answers2