Saturday, August 14, 2010

Project Execution

When I first begun hobby coding; I quickly learned that creating a solid project is hard to do.

I learned this in my second year of programming when I was writing a VB--racing game. The core of the game and the level-editor were complete. I had about three weeks before I had to hand it in. I thought it'd only take a day or two to create the 'save' functionality. It took about two weeks. This was when I was taking other courses too like Calculus and Algeo ... not purely programming :P.

I think that when I begun doing contracting I realized the issue with scope creep. Most of the time it had to do with UX issues. With me not being a UX guy it was pretty hard to make these types of changes.

...

Now to the professional world of programming. Not much has fucking changed. Multiple the end users and the levels of bureaucracy and you have the professional world.

I find myself having a shorter temper for unprofessionalism. The company I work for prides itself on being able deliver in a short amount of time. That means stressing developers and UX designers at times. I'm not a big fan of this type of development style. It's a bit ridiculous. They're wondering about putting us into training. But they don't know what we know. So what are we going to be training on? Most of the training sessions have been big wastes of my time. Scratch that. Every single training session has been. They pride themselves on being able to do this. They have nothing to be proud of. If you don't know anything about it; then you're going to be bombarded with information at a high-pace. If you know the topic, you realize that they're not going granular enough. You need a decenta mount of hands-on training to get people to hit the ground running right.

So my coworkers aren't trained in the domain. I simply can't code because I'm waiting for the architect. The architect can't give me specs because they haven't finished BA-ing. Great. So I'm behind and they're trying to pressure us. So I have no requirements. Not even vague requirements. I have no requirements. I have a freaked out project manager. I can't do any work. I'm so sick of hearing from my architect that I can't do it.

This is not the way to produce quality code. This is also a fixed-price project. So guess what, the project end date is already set. There are no specifications. So this means they want us to work long hours.

What. The. Fuck.

No comments: