Dev.to WebDev πŸ›  Dev πŸ‘ 0

What "best practice" did you quietly stop following?

Every dev picks up a pile of rules early on. Write tests first. Never commit to main. Keep functions under 20 lines. DRY everything. Comment your code. 100% coverage or it doesn't count. Some of those rules stuck. Oth

What "best practice" did you quietly stop following?

Every dev picks up a pile of rules early on. Write tests first. Never commit to main. Keep functions under 20 lines. DRY everything. Comment your code. 100% coverage or it doesn't count.

bfmeme

Some of those rules stuck. Others got quietly dropped somewhere along the way, usually after a project where following them made things worse.

I'm curious about the ones you dropped.

  • What was the rule?
  • What happened that made you stop?
  • What do you do instead now?

Bonus points if you still follow it sometimes and can explain when.

Two small ground rules so this stays useful:

  • be specific (a real situation beats "it depends"), and if you disagree with someone's answer, reply and say why. The arguments in threads like this are usually the best part πŸ˜„

I'll go first in the comments.

πŸ“° Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.