| There's lots of freedom and flexibility in things that are okay: - Being trustworthy and getting along with workmates is sometimes more valuable than being a favorite / teacher's pet to a manager. You ideally want to be amicable with both. - Say nice things about your colleagues when they accomplish things - It's okay during interviews to ask for time to show and tell projects, talk about your experiences. There's no rule written in stone to follow their format to the point you can't showcase strengths directly related to the job description. Things that you can do that don't help you always: - Being proactive: Taking responsibility for preventative things when not asked to. I fixed / averted many headaches that have gone totally unacknowledged over the past decade+. Here's the thing: I'd feel dishonest / unprofessional to not be proactive if something is breaking CI loops, typings, etc. It's hard for colleagues / managers to see the value until you wait for it to be a blocker. This is frustrating to me, because I haven't found the solution to reasoning about it. I don't like the idea of waiting for a problem to rear it's head and all developers are blocked by a problem. Things to not do: - Don't bring up any political discussion with colleagues, including outside work. No matter how moderate, harmless you think your viewpoint is. It can only do damage to you, never help. - Even in unfair situations, e.g. it's untenable and you need to end the relationship, to take the route to ending it amicably as possible. Say you're moving to the next place. Whenever in doubt / under stress: default to being professional as possible. |