25 votes

7 absolute truths I unlearned as junior developer

4 comments

  1. [3]
    Octofox
    Link
    Good quality post. The author points out being super picky about code style, this doesn't have to be a bad thing but the correct way to do it is to have a linter and configure it to an agreed...

    Good quality post. The author points out being super picky about code style, this doesn't have to be a bad thing but the correct way to do it is to have a linter and configure it to an agreed style guide. That way everyone sees the lint errors in their editor and can fix them before commiting.

    One interesting thing I have noticed is the huge amount of learning that happens on the first year of a new job.

    7 votes
    1. [2]
      Macil
      Link Parent
      I recently set up Prettier to run on each of my work's repositories automatically on commit. Formatting is no longer a conscious worry for us, and it's amazing.

      I recently set up Prettier to run on each of my work's repositories automatically on commit. Formatting is no longer a conscious worry for us, and it's amazing.

      3 votes
      1. mystickphoenix
        Link Parent
        In the past year, I've set up Python Black on my own machine to automatically format code on save. It's amazing how it relieves you of the cognitive burden of getting the formatting right. You...

        In the past year, I've set up Python Black on my own machine to automatically format code on save. It's amazing how it relieves you of the cognitive burden of getting the formatting right. You just have to get it close enough and bam, it's formatted for you. I'm not a huge fan of Go, but gofmt definitely brought an awesome idea to the table and it got enough mindshare that auto-formatting isn't "weird" anymore, at least in my experience.

        4 votes