The senior programmer, a guy who worked on the other app, quit on Monday. Tuesday the director came by our work area to point out that we were not using the infragistics data grid consistently and that we should create a template and use that. (He said the same thing 5 times. No joke. When he says something he will say it over and over. Someone came in late on a Friday, (which was expected because she had been there until 10 the previous night doing testing on an upcoming release), and brought donuts. Director came by to get a donut and said, 'If you come in late on Friday, you have to bring donuts'. He seemed to think that very witty and said it multiple times. Not sure what to make of that. It wasn't funny to me, it was a lame comment and the repetition was more disturbing than anything else.)
The point about us not using the infragistics grid correctly was a concern for me. We are talking about a 3rd party UI tool which can look nice but isn't going to replace all our other UI work, at least not easily or in a straight-forward manner. But, we, as in the director, seem to think it's going to deftly address a multitude of development issues. Whereas I do not. We were given a week to get the datagrid template where it could be used as a foundation for our system. Luckily for me, the other 2 guys on my team are leading the way on that. I had other issues in my queue and I a haven't been out front on the infragistics thing.
This stuff has been making me wonder a couple of things. Our project is better than failing, but it's not a great success, so, considering that I think we are going to be creating new bugs and missing deadlines (which has already happened), how far in the wrong direction are we going to go? We are re-architecting the app and I think it might be doing more harm than good, and even if the re-architecture did go well, it will be a long while before we see the benefits of it and I think management is under the impression that the director found some new way to do things that will make our jobs so much easier and thus quicker. And in this situation, how long can I last at this place?
There are a couple of other enhancements coming up that don't sound to prosperous to me, but who knows, they could turn out well enough. I like the fact that the team lead on this project is someone other than me, and that our project manager is an intelligent rational person, so I should be well enough under the radar when things don't go as well as planned. (Though I can contribute to the success, so far as we have it, by fixing some of the plethora of bugs we have already and making relevant enhancements as it becomes possible.)
My overall opinion is that software projects just like to fail a lot of the time. In my opinion, we should be doing other things than we are to make our project a winner, but management doesn't understand the problems that it's decisions are causing. I'd like to stick around at this place for a while, (I am thinking in terms of like months to a year), and see how things go, and I think that if I was looking for a new job in software development, there is a good chance I'd end up in another fucked up situation. (One of the guys who left our team a little over a year ago spent some time at a place where they wanted the programmers to work 14 hour days cause they were in a rush to update their old, out-dated app. Not something I want to deal with.)
When I started at this company a couple of years ago I told my homie that I was hoping to last a year. I don't know if I'll last another year. I guess I'd give the odd's at 50/50 that I'll make it till next August.