December 15th, 2018

(no subject)

An interesting thread on dev.to: some devs (juniors mostly) post their resumes; others critique them: https://dev.to/kaydacode/resume-review-1oei

One of the comments reminded me of the common advice I've seen in various guidelines: apparently it's a good idea to build your bullet points in such a way that instead of focusing on what you did they reflect on what impact your work had on the company (raised indicator x by n percent; saved the company m thousands of dollars, etc.). Which implies that you don't only care about the immediate technical solution to a particular problem, but know how your work affects the whole company.

I understand the appeal of this mindset, but it has always been alien to me. For me, it's the work itself that matters, and the immediate technical problems that it solves; not the company-wide results that it brings.