Originally posted by Nicodemus Chan:
I am not the Chief Architect. Just a senior software developer.
What should I do to change things?
I would politely and respectfully bringing up the topic. For example ask, "I've noticed there's no standard directory structure for projects, I'm wondering if that's something we might would find helpful; I've seen it used successfully elsewhere. Has anyone looked into this before?" You can start with a peer if you don'tyet want to address the issue with an architect or more senior person.
Remember that successful people don't simply point out problems, they uncover a problem, and bring it to the attention of the appropriate parties along with a solution they are willing to actively participate in. E.g. don't say "
you should use an automated build system," but rather, "I think an automated build system might help for the following reasons... I would be happy to investigate options and come back with some concrete proposals for systems that you can use to make an informed decision" or maybe "...I'd be happy to set one up on a small project that we could use as a trial project." Of course, remember that even though you need to do some prep work to have a solution ready, you still must be prepared for them to say "no thanks" despite your efforts.
--Mark