Quote:
Originally Posted by interracialtoons
And you don't see what is stupid about that do you?
Programmers give "estimated" completion times, one simple typo in a piece of executed code can delay a programming job at any time.
The reason Windows is fucked up is because it was "completed" "on time". 
You think you have a point about programmers yet the real point is that you didn't get your job done because of what you asked for. Think about that.
The programmer woud be happy to do your job in one day and fuck off for 4 days so why would they want to deliver the project late?
Bottom line: if you don't like/understand the nature of programming jobs then read a book and do it yourself. You'll have a new outlook on life after you deal with it yourself. |
good programmers should be able to give an accurate completion time if the job is explained well. they need to be aware of what delays might come up and plan for them.
i would rather be told the job will take 10 days and be delivered in 7 than to be told it will take 5 days and have it delivered in 6. i have to plan my time around what a programmer tells me.
ive read the book, i can do it myself.. i have a pretty good idea of how much time a project needs when i hire someone to do it. i also realize that there may be a day or two at the end of the project added for testing and modifications.
what bothers me the most is when a guy says "ill have it done in 5 days" and on the 5th day he/she is nowhere to be found. the least they can do is shoot me an email... "hey i expected to be done today.. im close.. i cant get blahblahblah working exactly how you wanted it yet... i need 6-8 hours to resolve it" instead they show up 3 days later with some lame excuse.
ive got a fulltime webdev guy now and i aint letting him out of the basement, i just throw down some food and mountain dew every so often.