Tag Info

New answers tagged

22

You assume the fix does not introduce any new issues and fixes the old ones complete. But lots of fixes are worth a review on their own - and that is probably much easier when the incremental changes can be reviewed separately.


1

Lots of good answers already, so I won't duplicate them. However, one other process I've found useful is performing a self review of your code before yours send it out. This is a really simple thing to do and it will make you team mates lives reviewing your code a lot easier. All you do is look at your diff before you send it out and do a quick code review ...


0

One approach I have been taking that has been very helpful is: starting out with acceptance test without implementing it to give the context of what needs to be worked on and then diving into building the structure. Once there is some structure (i.e. I have classes, interfaces, some unimplemented methods) I go ahead and start writing unit tests for ...


1

What approach do you take (or what do you incorporate into your approach) to coding tasks that help avoid carelessness and ensure you're doing a thorough job? I by and large don't - it's a waste of time. Missing attributes is a 30 second fix and will be easily caught by testers/integration tests/UAT/whatever. In my current position (and others I've ...


3

Do 1 thing at a time and progress to the 2nd thing only after you're done with the first. You missed those [httpPost] bits because you didn't write a controller, and all its associated code, you went straight to the next one before you'd completed the first. We all do it to some extent, and its generally caused by coding away oblivious to what your code is ...



Top 50 recent answers are included