> > > Don't get me wrong, I'm not discounting engineering skills; we're all on > the same side there. What I was hinting at above is that if you get lucky > and get good managers at a mid-to-large co, you have the opportunity to > learn how organization in the large works, and that's an important skill > too. >
Note: You reminded me of my favorite line "People don't leave organization , they leave managers". > > That said, I should clarify, when I say, 'spend the first couple of years > maintaining somebody else's crap code', I say that from personal > experience. Maintaining something you didn't build teaches you a lot about > the importance of building good readable, maintainable, malleable code. I > know I write good code because I don't want people who end up maintaining > it (myself included) to go through the agony I had to back then. That's > probably one the biggest takeaways I have from back there; and that was > what I was primarily pointing to. > > In most support project you don't change code until there is a requirement from client, else you end up supporting the tickets etc... -- * "Talk is cheap, show me the code" - Linus Torvalds Winning Regards KraceKumar.R http://kracekumar.wordpress.com +91-97906-58304 * *+91-85530-29521* * * _______________________________________________ BangPypers mailing list BangPypers@python.org http://mail.python.org/mailman/listinfo/bangpypers
