Hmmm. I guess I didn’t really understand the intention of my trip down here. Not surprising, given the lack of clear communication from which so many of us suffer. I was choosing to believe I was coming down here to be a major contributor on the PMIS project. Jude thought I was for the architect role, but what they want is someone to maintain (i.e. work defects) one small module of the overall dashboard backend. In fact, this module, while containing vital functionality, is very minimal in the overall scheme of things.
The sub contractor John Amason remains the architect for the changes intended for PMIS, and I agree with his design. However, and I think this is a product of the environment, I bore at the implementation strategies for developing anything in this manner. He is using tools (a.k.a. wizards) to write most of the code, which is fine and dandy, if you have people that know the tools, you want to surrender all design control to the authors of the tools, and you have lower-skilled people maintaining the code base (ref The Perils of Java School).
Maybe this is a me problem because it sure seems like this is how things are done in the business software development world.
The thing that always kills me is that whenever you use *tools* to build an app you are surrendering your control over the way things work. Doesn’t seem to bother people in this world, but it drives me freaking nuts!
When you use tools to generate your database, then more tools to generate your accesses to the database, you are losing normalization of the data. Doesn’t seem to bother people in this world, but it drives me freaking nuts!
When you use tools to generate your business objects and tools to generate your interface code, you are losing control over the OOD. Doesn’t seem to bother people in this world, but it drives me freaking nuts!
Anyway, I am not happy working in this environment, but it seems as if that is where I am stuck…