Unable to control myself from Code cleaning !

[P@Anand]

I also have the habit of saving the VI more often. Not only just save, Ctrl+Shift+Save and I started doind all the other applications as well. Many times I get a pop-up window when I try to do the same with MSWord.

[Hornless.Rhino]

---

@crossrulz wrote:

I am so bad that I usually clean up somebody's diagram just to figure out what they are doing.  I also created a few shortcuts to help me clean up.  And my number one righ-click menu that I use is "Clean Wire".

---

Oh really....

It seems that I may have found a way to cleanup my code without me putting in any effort.

So uh crossrulz...do you uh...want to look at my code *whistles innocently*

[P@Anand]

---

@Hornless.Rhino wrote:

---

@crossrulz wrote:

I am so bad that I usually clean up somebody's diagram just to figure out what they are doing.  I also created a few shortcuts to help me clean up.  And my number one righ-click menu that I use is "Clean Wire".

---

Oh really....

It seems that I may have found a way to cleanup my code without me putting in any effort.

So uh crossrulz...do you uh...want to look at my code *whistles innocently*

---

Tim didn't mention that he review the code for free

[crossrulz]

---

P@Anand wrote:

---

@Hornless.Rhino wrote:

---

@crossrulz wrote:

I am so bad that I usually clean up somebody's diagram just to figure out what they are doing.  I also created a few shortcuts to help me clean up.  And my number one righ-click menu that I use is "Clean Wire".

---

Oh really....

It seems that I may have found a way to cleanup my code without me putting in any effort.

So uh crossrulz...do you uh...want to look at my code *whistles innocently*

---

Tim didn't mention that he review the code for free

---

That is correct.  So would it be easier to go through the purchasing process or fix your own code?

[Ray.R]

---

P@Anand wrote:

There are many situations where I have to develop code within short time, but I am not able to control myself from cleaning the BD.

From some of my fellow collegues I was advised not to care about the wire bends and other stuffs and complete the code. Later part we can cleanup the code, but I am not able to follow this.  Even when I check the code of others and if I see wire bends and mis-alignment I start correcting them. 

Feel free to post your opinion.

---

I'm the same way...

Especially when I work with others on the same project.

We do not seem to be the only ones..  That alone should count towards a CLD!

[TiTou]

---

P@Anand a écrit :

There are many situations where I have to develop code within short time, but I am not able to control myself from cleaning the BD.

From some of my fellow collegues I was advised not to care about the wire bends and other stuffs and complete the code. Later part we can cleanup the code, but I am not able to follow this.  Even when I check the code of others and if I see wire bends and mis-alignment I start correcting them. 

Feel free to post your opinion.

---

I do this too. Compulsively. Its a major psychotic obsession.

[LV_Pro]

It bit me big time recently. I had inherited some code, was going through it trying to figure how it worked and was unconciously straightening wires, etc. I, without thinking, corrected some spelling errors (for two years, following this programmer, I have managed to resist this), and two weeks later, when we tried to run final tests on 80 parts, found that their initial test data (necessary for the final test) had not been saved in the local results database. It took a while to find, but, ummm, the unconcious corrections and meant that the initial test data did not match with the existing database field names. Doh!  Thankfully we had enough time to rerun the first tests (after correcting my corrections) and then run the final tests to get the parts shipped.

[P@Anand]

Thats why I always have a backup before start checking the code, so that I can replace and get rid off the mess I create by cleaning .

[crossrulz]

---

P@Anand wrote:

Thats why I always have a backup before start checking the code, so that I can replace and get rid off the mess I create by cleaning .

---

It's called source code control!

[P@Anand]

---

@crossrulz wrote:

---

P@Anand wrote:

Thats why I always have a backup before start checking the code, so that I can replace and get rid off the mess I create by cleaning .

---

It's called source code control!

---

Manual source code control