Andrey (azangru) wrote,
Andrey
azangru

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.
Subscribe

  • (no subject)

    A hilarious piece of web comedy in the style of Monty Python. Can only be viewed on the author's web page, because privacy settings. But so worth it.…

  • (no subject)

    A very impressive demo of real-time noise suppression software for Linux called NoiseTorch: - audio demo on the Linux for Everyone podcast…

  • (no subject)

    Twitter is having fun:

  • Post a new comment

    Error

    default userpic
    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 4 comments