3 ms·

Naming things well (and renaming them as new information evolves) is massively important. As important as tests.

_g0wg 1y ago
I'm on this team as well. Been trying to explain this to the guys at work (fabrication/CAD work). They argue that "we already do have a system, we put projects in the customer folder". Here is a sample folder structure (from memory, not exactly the same): /Customer/Project/: ./.190 - STEEL - QTY - 3 - CUSTOMER - PART#.dxf ./.190 STEEL - QTY 1 - CUSTOMER - PART# DO NOT ETCH BEND LINES.dxf ./LEFT SIDE BRACKET B.sldprt ./PART 3.sldprt ./PRJ001.sldprt ./PRJ002.sldprt ./PRJ401.sldprt ./ALL PARTS PUT TOGETHER.sldasm ./FINAL ASSY.sldasm ./STEPS ASSY.sldasm Keep in mind they also have a /Customer/Project REVISED - USE THIS/ folder, a /Customer/Project 4-13-24/ folder, and a /Customer/Project UPDATED/. They also have (ON PURPOSE!) a system where they have 3 sources of truth so if any of them don't match we have to stop what we're doing to double check what's actually correct :| While they didn't take my suggestions on this particular thing, my expertise has been noted for when there's a need for printer troubleshooting...
throwaway314155 1y ago
Like many comments in this thread and contrary to the question posed by OP, this is a fairly _popular_ opinion.
- bravesoul2 1y ago
  It's not that often I see a "just fix naming" pr though. People would rather put up with it in general.
  - throwaway314155 1y ago
    Yeah - it's probably a "cultural" thing (as in per-team/codebase opinions change). I see a lot of "naming things is hard" comments on HN and my first internship in college was for a Java position where verbose (perhaps overly so) naming is encouraged. I've brought that mindset with me to other jobs and found plenty of likeminded folks but I assume it's also true that there are far more people who simply don't care (as much).

I'm on this team as well. Been trying to explain this to the guys at work (fabrication/CAD work). They argue that "we already do have a system, we put projects in the customer folder". Here is a sample folder structure (from memory, not exactly the same): /Customer/Project/: ./.190 - STEEL - QTY - 3 - CUSTOMER - PART#.dxf ./.190 STEEL - QTY 1 - CUSTOMER - PART# DO NOT ETCH BEND LINES.dxf ./LEFT SIDE BRACKET B.sldprt ./PART 3.sldprt ./PRJ001.sldprt ./PRJ002.sldprt ./PRJ401.sldprt ./ALL PARTS PUT TOGETHER.sldasm ./FINAL ASSY.sldasm ./STEPS ASSY.sldasm Keep in mind they also have a /Customer/Project REVISED - USE THIS/ folder, a /Customer/Project 4-13-24/ folder, and a /Customer/Project UPDATED/. They also have (ON PURPOSE!) a system where they have 3 sources of truth so if any of them don't match we have to stop what we're doing to double check what's actually correct :| While they didn't take my suggestions on this particular thing, my expertise has been noted for when there's a need for printer troubleshooting...

throwaway314155 1y ago

Like many comments in this thread and contrary to the question posed by OP, this is a fairly _popular_ opinion.

bravesoul2 1y ago
It's not that often I see a "just fix naming" pr though. People would rather put up with it in general.
- throwaway314155 1y ago
  Yeah - it's probably a "cultural" thing (as in per-team/codebase opinions change). I see a lot of "naming things is hard" comments on HN and my first internship in college was for a Java position where verbose (perhaps overly so) naming is encouraged. I've brought that mindset with me to other jobs and found plenty of likeminded folks but I assume it's also true that there are far more people who simply don't care (as much).