this post was submitted on 27 Mar 2025
230 points (97.9% liked)

Programmer Humor

22186 readers
4002 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 

AltIndiana Jones swapping out an artifact for a fake one meme template with the text "existing code" on the real artifact, "new commit" on the fake one, and "linter" on the pedestal / trap

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 5 days ago* (last edited 5 days ago)

Why would it be on each dev to setup?

Your repo can, and should, include workspace settings for major editors that provide a uniform experience for anyone onboarded to the platform.

I agree that precommit hooks are good for uniformity. But slow pre commit hooks are frustrating, they are also often turned off. Your CI will always be the last gatekeeper for linting/formatting rules regardless.

Making precommit hooks slower means more devs disable them, which is the opposite of what you want. Save them for simple, read, checks and validations that can run in < 1s for even huge changesets.