4 ms·
Ugh. Every time I inherit code that someone has peppered with regions, I delete then. It's a bunch of extra noise if you expand all regions, and if they're coll
by dpark 11y ago
Ugh. Every time I inherit code that someone has peppered with regions, I delete then. It's a bunch of extra noise if you expand all regions, and if they're collapsed it's harder to see the overall structure of the code, and some functionality (specifically undo/redo, but others also) gets gimpy when collapsed regions are involved, making it hard to see what is changing.
I find regions to be useful 1% of the time, simply pointless 10% of the time, and hiding crappy code the other 89% of the time. When I open up code and see a bunch of regions, I immediately assume that the file contains way too much unrelated functionality and that the code is poorly written. This assumption is very rarely wrong.
- jameshart 11y agoca82a6d - kenjackson - 10 files changed, 34 insertions: "Added some regions" 085bb3b - dpark - 10 files changed, 34 deletions: "Removed regions" a11bef0 - kenjackson - 10 files changed, 34 insertions: "Added some regions" 2432f8e - dpark - 10 files changed, 34 deletions: "Removed regions" cbe6306 - kenjackson - 10 files changed, 34 insertions: "Added some regions" e7e1bef - dpark - 10 files changed, 34 deletions: "Removed regions" ....
- sverrirs 11y agogold, pure gold :D
- kenjackson 11y agoIn fairness though that assumption is almost always true regardless.