What's one piece of advice every dev should ignore? 🚩🚩🚩

I according to me this is the advice I often hear that I definitely ignore:

If your change is small enough there's no need to test.

The "good code" can definitely be self-documenting to some extent. There can be exceptions of course.

Any super duper opinionated advice on which software to choose for a problem.

A good suggestion is always useful — but when it's approached with an outside amount of conviction, one should take that with a grain of salt. The advice often lacks context.

Dogma which is complemented by dogmatic backlashes to the original dogma: A software story.

"X is dead. You should probably find a hot new thing to learn."

Any advice about documentation that does not include ongoing structure and discipline.

Maintaining good docs is inherently pretty difficult, and there is no magical solution. Good documentation is a matter of a number of combinatory factors that can lead to success, there is no silver bullet.

Why don’t you code code it yourself instead of complaining about that library or whatever-the-heck you called it?

Uh, because complaining is fun, and it will take me an extra 100 years to code it myself…

Advice to ignore: "You should not use Dev.to like you use Twitter" ^^

Most

"Learn X, it's faster and better than Y"

The missing part is that X is something of a hyped POC, with virtually no real project using it, with less DX than Y, while Y is battle-tested and there's no real reason to change it expect for hype and some weird scenarios.

That's scary! 😨

If it works then don't touch it.

No - "Good code is self-documenting" is a basic truth, up to a point ... it's a useful guideline, if not taken too far (sometimes you do need to write comments).

Inheritance is for prototypes & interfaces. Encapsulation / pass through constructor or function, is great at decoupling code