Programmers, please read...

Hell Puppy · 03-24-2005

Oh, I have opinions on all this all right. But I wont be a jackass. And Sarettah already covered about as much Project Management 101 as I'm inclined to type up at the moment...

Short version... "Part time programmer" usually means you're gonna get a program that works part of the time as well.

I appreciate Ryan's problem. He has 1 programmer on staff, he has enough work for more than 1 programmer, but not quite enough work or budget to hire a second fulltime.

That's a tough one...and here's why....

First off, you're asking the second programmer to "jump in" on ongoing projects as needed when he wasn't around to contribute to the design phase. Furthermore he's not involved in the day to day, he may not even comprehend WHY he's being ask to do what he's doing and the business reasons behind it. That makes for code that doesn't often meet customer expectations.

Now, to make it worse, you're telling me that WHEN the shit breaks, you'd like this guy to throw down whatever else he's doing and go head down til it's fixed even if he has to work 36 hours straight. If he can promise that, he's not in demand, and there's likely a reason why.

I'm also working on the assumption that there probably are no functional specs for whatever projects are being worked. You've only got one programmer, so I'm sure someone described to him what they wanted and he sat down and started coding it. Pity the poor bastard that has to try to go in behind him and figure out what the hell he's doing.

I've seen way too many products in this industry in particular where someone has a great idea, they hire someone to code it, but dont keep them around. They need enhancements and grab someone else. Still no functional spec, you're just hacking code. You end up with an unreliable piece of shit that no one worth their salt will touch with a 10 foot pole.

Damn, and I said I was gonna keep this short and not go into it...

You bastards!

03-24-2005	#12
Hell Puppy Fat Fucking Nobody Want to see your own Advertising Here! Join Date: Oct 2002 Posts: 6,523	Oh, I have opinions on all this all right. But I wont be a jackass. And Sarettah already covered about as much Project Management 101 as I'm inclined to type up at the moment... Short version... "Part time programmer" usually means you're gonna get a program that works part of the time as well. I appreciate Ryan's problem. He has 1 programmer on staff, he has enough work for more than 1 programmer, but not quite enough work or budget to hire a second fulltime. That's a tough one...and here's why.... First off, you're asking the second programmer to "jump in" on ongoing projects as needed when he wasn't around to contribute to the design phase. Furthermore he's not involved in the day to day, he may not even comprehend WHY he's being ask to do what he's doing and the business reasons behind it. That makes for code that doesn't often meet customer expectations. Now, to make it worse, you're telling me that WHEN the shit breaks, you'd like this guy to throw down whatever else he's doing and go head down til it's fixed even if he has to work 36 hours straight. If he can promise that, he's not in demand, and there's likely a reason why. I'm also working on the assumption that there probably are no functional specs for whatever projects are being worked. You've only got one programmer, so I'm sure someone described to him what they wanted and he sat down and started coding it. Pity the poor bastard that has to try to go in behind him and figure out what the hell he's doing. I've seen way too many products in this industry in particular where someone has a great idea, they hire someone to code it, but dont keep them around. They need enhancements and grab someone else. Still no functional spec, you're just hacking code. You end up with an unreliable piece of shit that no one worth their salt will touch with a 10 foot pole. Damn, and I said I was gonna keep this short and not go into it... You bastards!