3 ms·
After doing it for years, I've realized that clean code isn't really a good end goal, so I'm not sure if it "steps up your game" That said, The Pragmatic Progr
by muzani 7y ago
After doing it for years, I've realized that clean code isn't really a good end goal, so I'm not sure if it "steps up your game"
That said, The Pragmatic Programmer is my favorite resource for it. https://refactoring.guru/ https://refactoring.guru/ is also a nice reference point, in an easy problem-solution format.
- panosfilianos 7y agoSo what would you say is an appropriate end goal to max out productivity, collaboration and reusability of/on code?
- muzani 7y agoDeliberate practice. Find what you're weak at and work on that. Clean code is great, and it's definitely someone's weakness, but it doesn't sound like yours. Find out what's making you procrastinate or hesitate, and focus on that instead. If you're procrastinating because your code is a mess, then you probably want to learn clean coding. But at some point it will have diminishing gains, like learning to type fast. The little things that have greatly improved my productivity recently: ES6 literacy, zsh aliasing, knowing array methods by heart, IDE shortcuts, CSS animation. Ideal productivity is not at 100% clean code & architecture, but somewhere between 40%-80%, I'd say. The more confident you are of a feature and the more confident you are in the architecture, the more you can invest in it. There's an anti-pattern on refactoring as well. Many times you want to put a constant or config in the code itself. Sometimes you even want to ignore DRY and copy code. I also use god objects as a dumping ground for methods and then refactor parts of them into a class much later, when a pattern emerges.