The company I work at now doesn't make the distinction and has plenty of coders who "do both." I also do both. "Creative" is still a bad name. When your appl

The company I work at now doesn't make the distinction and has plenty of coders who "do both." I also do both. "Creative" is still a bad name. When your application evolves and the names of your services no longer match their business purposes, it's a good practice to update the naming to increase clarity. The same should be true of your departments and job descriptions. Keeping a name even though it doesn't make sense just because it's traditional and an industry standard is pretty lame. I doubt you'd find much support for that kind of thinking here.