DEV Community

Discussion on: Dealing with Imposter Syndrome

Collapse
 
jingjing142 profile image
Jing

Hi Mike, sure!

So, for example, when I first started, I did a Udemy course on TypeScript. And shortly afterwards I worked on a ticket converting part of our codebase from JavaScript to TypeScript. So I wrote down "took TypeScript Udemy course and learnt about the fundamentals of TypeScript". For the ticket itself, I wrote down

PR #XX Ticket name

  • Link to ticket
  • Converted several components to TS
  • Worked largely independently and applied newly acquired knowledge
  • Pair-programmed with XXX to solve unexpected, tricky errors
  • Addressed PR comments from other team members
  • Took notes that others can use as a future reference when converting files to TS

Of course it can vary a lot based on the ticket, but that's how I do it. I mainly use bullet points to keep it simple. I also note down the number of the PR, since I find it quite motivating to see how many tickets I've already handled, but of course the amount should not matter as much as the quality :P It's just a personal thing. I also add the link, so I can always go back and check my own PR in case I'm doing something similar again or forgot how to do something I already did (it happens).

But again, it really depends on you and what works best for you. You can always experiment and see. Just try not to discount your own achievements. What might seem small to others, might be a big achievement for you, and you should record it accordingly :) Working independently, for example, might not be worth mentioning for some others, but as a career changer it felt like a little milestone so I recorded it.

Hope that's helpful 😊

Collapse
 
artdevgame profile image
Mike Holloway

Thank you Jing for the detailed reply, very helpful.