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

"X is flexible, easy to install and use, and powerful". Which means it's neither.

I would say that Don't do that what everyone else is doing.black magic to separate lovers

Stop using if/else if

build it from scratch

and ofcourse > "If it works, don't fix it!"
(sometimes may be true, but the consequences may be also quite hard later)

1) don't learn PHP
2) don't do drugs :)
3) don't read manuals

What’s wrong with good code is self-documenting?

Advice to ignore:

Don't ever ignore any advice, as you can always learn something from any advice you get, and also show respect to those who offer it, but consider the source.

Wrap your head around that one!

;)

Sorry for the two-parter:

do you know functional programming? Like closures and currying?

Note: all code that is reachable is functional. I mean, pure lambda functions or any set-based/tuple-calculus-based patterns are great. But they aren’t anymore “functional” than anything else.

Closures & currying is deprecated in favor of es6 classes. And they really amount to a complex way to do inheritance on the fly. 🤢🤮

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

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).

If it works then don't touch it.

That's scary! 😨

"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.

Most