I'd +1 this answer: find an open-source project, but find one the right size to feel like you are making a difference. I never managed to break into WordPress - the FLOSS I probably use the most - however, doing some scripting (Google Apps Script) for a organisation I volunteer for I've really got into what a fantastic little language JavaScript is and ended up working on a little project with just a few of us contributing (Flubaroo). I'm hoping to start earning with JavaScript eventually - watch this space...
I can certainly understand where the submitter is coming from, I like all the dots and crosses in place (oh, the luxury of lavishing time on dotting and crossing) but I also appreciate how this can slow things down, and trying to change people is just a world of pain. Talk to the guy; talk to the team; talk to your boss. Work out what the project's trying to achieve: a rock solid low-level bit of code, or a fast and dirty prototype, or something in between. Then try and find your place in amongst it where you can appreciate everyone's contribution... or go work somewhere else.
I worked one place where the dotters and crossers got the OS code and the fast and dirty bunch got to write the apps, and we all rubbed along nicely.
Slashdot Mirror
I'd +1 this answer: find an open-source project, but find one the right size to feel like you are making a difference. I never managed to break into WordPress - the FLOSS I probably use the most - however, doing some scripting (Google Apps Script) for a organisation I volunteer for I've really got into what a fantastic little language JavaScript is and ended up working on a little project with just a few of us contributing (Flubaroo). I'm hoping to start earning with JavaScript eventually - watch this space ...
I can certainly understand where the submitter is coming from, I like all the dots and crosses in place (oh, the luxury of lavishing time on dotting and crossing) but I also appreciate how this can slow things down, and trying to change people is just a world of pain. Talk to the guy; talk to the team; talk to your boss. Work out what the project's trying to achieve: a rock solid low-level bit of code, or a fast and dirty prototype, or something in between. Then try and find your place in amongst it where you can appreciate everyone's contribution ... or go work somewhere else.
I worked one place where the dotters and crossers got the OS code and the fast and dirty bunch got to write the apps, and we all rubbed along nicely.