Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If your workflow is dependant on many files, and with that naming convention because of it - there’s a good chance the workflow could be cleaned / simplified greatly. Wether it’s worth the effort or not, I don’t know - but lots of tools / freedoms / restrictions make certain processes possible and it’s always worth revisiting.


The naming conventions that require >38 characters come from a vast number of business entities that I have worked with through the years: Customer_Project_Subtask_Blaa How does anyone in the real working world not have this issue?


There's already a sibling comment that suggests this, but to elaborate, this is how I would typically organize something like that:

    /home/my_user/
      Customer/
        Project/
          Subtask/
            Foo.txt
            Bar.txt
Is there a reason why you can't just use nested folders?


...folders?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: