3 ms·
To quote "The Mythical Man-Month": > Question: How does a large software project get to be one year late? Answer: One day at a time! 12000-thousand-line-long
by anton_gogolev 13y ago
To quote "The Mythical Man-Month":
> Question: How does a large software project get to be one year late? Answer: One day at a time!
12000-thousand-line-long methods do not appear out of nowhere and in one go; rather, it gradually acquires cruft. To combat this, introduce peer review: code review by sending a patch to an internal mailing list, merge/pull requests in GitHub/BitBucket/GitLab/Stash, feature branches, etc.
- jlengrand 13y agoI fully agree with that. Our bigger mistake, being such a small team, was to let the guy fully in charge of the project for so long. But the conditions were also kinda special. I was the junior, with him having close to 15 years of experience. We were only 2 in the office. The rest of the team being in another country. So I was basically the only one to see the code. And he would listen to me, being the junior. So I requested not to work anymore, not being able to bear the situation. In the end, he worked alone :S
- midas007 13y agoSounds like https://en.wikipedia.org/wiki/Cowboy_coding https://en.wikipedia.org/wiki/Cowboy_coding >.< Best advice might be to double-down on putting everything you're doing in the issue tracker and tying to commits. Don't get lumped into the "problem" when "why aren't we executing?" gets raised. Focus, ship & get credit for your work that gets shit done.