4 ms·
That proverb holds a lot of truth. I would add that treating the company's money as if it is your own also works quite well. Never get too attached to a user
by sharken 5y ago
That proverb holds a lot of truth.
I would add that treating the company's money as if it is your own also works quite well.
Never get too attached to a user story/task is another important lesson. Sometimes a task has to go, even though you disagree.
To OP I'd say that you should really try to rediscover the desire to learn.
That and being able to quickly locate related information for a task are two of my most important skills.
- NikolaNovak 5y agoTo add to your point of treating company's money as your own -- "Tracking Money" will help understand a lot of corporate priorities and explain a lot of decisions. --I-- may want to update something because "it's the right thing to do / makes for cleaner code / etc". But the management probably has a reason (good bad or ugly) for their own priorities. Advice I read mid-way through my career is "understand your manager's goals and reasons", and it was so simple and yet so... shocking to so many of us techies. We always expected manager to understand our recommendations and priorities. Hubris! :) (in Public Sector, "Tracking Money", interestingly, did not work as well; but "Tracking Personal Status/Blame/Credit" worked well. The two should be equivalent but in my limited experience there's differences)