We'll go first >
"Good code is self-documenting"
What would you add?
For further actions, you may consider blocking this person and/or reporting abuse
We'll go first >
"Good code is self-documenting"
What would you add?
For further actions, you may consider blocking this person and/or reporting abuse
Antonio | CEO at Litlyx.com -
Madza -
Dokyun Claire Lim -
balrajOla -
Top comments (29)
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.
"Smallness" is definitely not the proper litmus test.
And if you don't want that small change to break later, a regression test couldn't possibly hurt, right?
Yeah, absolutely!!
Yes same lol! for example if I'm making scripts in python and I change to add a print statement with colour I always run the program to make sure it works as I want it to.
"X is dead. You should probably find a hot new thing to learn."
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.
The "good code" can definitely be self-documenting to some extent. There can be exceptions of course.
Seriously. I find most projects built with TS are pretty much self documenting. There are obviously more factors, but a well typed project will get you 90% of the way.
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.
Dogma which is complemented by dogmatic backlashes to the original dogma: A software story.
"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.
Advice to ignore:
Wrap your head around that one!
;)
Wrap your head around that one!, I cannot!
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).
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…