- java package name (com.xyz....)
- class or script name (XYZStoredProcedure.java)
- database table name (XYZ_DOCUMENTS)
- host name (prod1.xyz-internal.com)
What naming convention should you use? Use something generic like ‘App’ (com.app... , AppStoredProcedure etc.) and/or something neutral not related to a specific project like ‘Carbon’ or ‘Star’ (so you can have com.app.carbon... or com.carbon...).
Do not worry about java package clash. In my entire professional experience I am yet to find a third-party library which used the same naming in their package name as I use in mine - most of the open source projects are well-named to prevent package clashes with your code.
So when you start from scratch at your new company do yourself a favor and don’t use company name anywhere no matter how confident you are that ‘this time it will be permanent’. You will thank yourself for that decision in a couple of years.