First, learn what is needed for the current job, the processes, the tech stack, the DBs etc. I spend a fair amount of time studying but I take a two-pronged approach. That's not to say I don't do anything extra. Spending 12 hours making sure that documentation is just right might get you a "good job" comment from the manager and might get you the recognization of being a good document writer but you know what a quick bullet list you did in 20 minutes will tick that task complete and that is what your manager is interested inĪfter I got that concept through my head my life in IT became a cakewalk and more important my salary has tripled over the past 10 years (and pretty much no overtime). All your manager is interested in is that you getting done what he or she assigned to you. At my third job, it hit me like a baseball in the nuts with a simple comment from another co-worker. Or at the end of the year my review comes back with all 'meets', and just get the standard raise. I did that for years, and I'd see people getting promoted and then try to figure out what I did wrong. ![]() ![]() I'd be up at 7:00 am, I'd be scripting, I'd be documenting, I'd be on calls helping out people, I'd be helping teammates even if they didn't ask for it, I'd volunteer for tasks, I'd be working late or on the weekends trying to get something done or working the way I wanted it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |