3 ms·

This is good, and I'd add on to the part about the successes. Learn to document your successes and be able to verbally communicate why anything you do is import

This is good, and I'd add on to the part about the successes. Learn to document your successes and be able to verbally communicate why anything you do is important or useful to less technical users. If you don't have a good boss who can see that you are good at what you do, you will have to be able to speak up if you want to be paid what you are worth. You want to be a step up from a computer janitor who needs to be told what to do, to being someone who delivers value to the business and helps people get their jobs done, and can anticipate problems before they occur.

lighthawk 12y ago
> Learn to document your successes and be able to verbally communicate why anything you do is important or useful to less technical users. And on the software engineer/developer side of things the same applies. This is why whenever I am given a self-assessment or asked to help with a review of myself, I go back through my git log, email, etc. looking for what I've done instead of just attempting to summarize based on memory. Then I keep a personal copy of my self-assessment. That way, I have a record of what I did, and so does my company. Wikis, file servers, and other document repositories change, and when you switch jobs, you have that available to look at to update your resume. If your company doesn't make you do at least annual and hopefully quarterly self-assessments, you should do it on your own.