Skip to content

Topic: When not to follow industry standards #1

@Hamilton-dfp

Description

@Hamilton-dfp

Sometimes we just follow a standard because it's the standard, or because it's best practice.

90+% of the time, we should be following standards. But more importantly, we should be 100% of the time striving to understand the standard and why it's applicable.

One example of this is the best practice of checking in package-lock.json. I completely agree with the reasoning of why as described here: https://stackoverflow.com/questions/44206782/do-i-commit-the-package-lock-json-file-created-by-npm-5

Now discuss the unavoidable platform independent build that made all those arguments moot.

Discuss how the team reacted when I added package-lock.json to .gitignore.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions