No, title only
No, title only
Right, but my initial comment was about article’s statement being wrong. Refactoring in the way you described will make code harder to delete which is bad according to the article.
I don’t understand too. Are you suggesting me to drop bunch of features in the product?
TLDR;
My current project has mostly easy to delete code and not easy to extend. Why? Coz shit was copy-pasted 50 times. It’s not fun to work in this project.
Post commit hook to push + always squash on merging feature branches
I mean, mom could be right. Maybe there’s a rule on router to block Fortnite servers after 21:00. She just doesn’t tell that she the one turning it off
He just applied Russians’ favorite soviet era saying “those who is not with us is against us”
After closer look I can say this is great idea. Initially I thought this messes with Lit’s lifecycle bringing React’s lifecycle drawbacks but seems like it’s not. I think at some point you should get in touch with Lit devs and see if it can become part of Lit lab or even Lit itself
Is it better than React functional components in any way? I don’t see benefit over React functional components or even Lit’s class components
Top ten comments do not mention typo. What a hell is going on. It’s Lenuks, not Linux
I like (no) how everyone knows this is about everybody’s mental health but you can only push things these days if iT iS aBoUt cHilDrEn or other touchy topic. Apparently adults can’t have mental health issues I guess, otherwise how will they do their jobs for cents
No, that means you falling into author’s bait where they misuse term “delete”. Refactoring is not equal to deleting. One can be result of another. But the truth is that extendable code needs to be modular to be extendable. And modular code is easy to refactor. Author couldn’t not name it “Write code that is easy to refactor, not easy to extend” coz it’s even more dumb