> So the work you want to do and the one the company wants you to do will probably only overlap for a short period of time.
Similarly, there's only short period of overlapping of the work you want to do
and the work doing which you would grow. I see too often programmers jumping
around abandoning their half-written application or library once it is
somewhat working, never learning what semantic versioning is about, what it
takes to write good documentation, or how architecture works.
I've seen people proud of having an opportunity to maintain (note: not to
develop, just to maintain) big products. Such product was doing amazing
things and was well-written, of course, but would you think you could take
pride of maintaining somebody else's work?
Similarly, there's only short period of overlapping of the work you want to do and the work doing which you would grow. I see too often programmers jumping around abandoning their half-written application or library once it is somewhat working, never learning what semantic versioning is about, what it takes to write good documentation, or how architecture works.
I've seen people proud of having an opportunity to maintain (note: not to develop, just to maintain) big products. Such product was doing amazing things and was well-written, of course, but would you think you could take pride of maintaining somebody else's work?