I disagree, I think deadlines are a great thing. To counter some of your points,

[b]1.Forces developer to work under pressure as fast as they can.[/b]
This isn't true, when the developer sets out their timelines to his manager they should estimate it so they have enough time to complete their work. If any big roadblocks come up they should let their manager know as soon as they come up so that the deliverables can be adjusted.

[b]2.The word basically means death of the project if the project is not finished when the deadline time is passed.[/b]
This simply isn't true, the developer set out their deliverables for a deadline/milestone and they deliver them. Sure they're going to kill the project if they deliver 0 deliverables but they should hit most of them if they planned them out properly at the beginning. If they did run into roadblocks and let their manager know then as long as the manager let the publisher know early and possibly replace them with something easier to deliver for that deadline/milestone it shouldn't be a problem.

[b]3.It is used as a way to see if workers actually do their work with sub deadlines.[/b]
Isn't that what they pay you to do?

Setting up goals/milestones/deadlines are very important to a project. They help you to map out what the scope of a project is. Without them you'd wind up with a duke nukem forever, a project that just drags on and on forever!

1. I have not had any programming work where I could have set my own timeline, if I had just had bad luck I do not know it, but for example I got work from this "comic" publisher who wanted website where they could sell their comics as digital versions. He did not want to use any existing stuff and had one of his comic artist to do the web design. I started to work right away with the designer after i had signed the employment contract. He did not say any deadlines to me, but said that i should complete it as fast as possible. So I wrote much stuff and the web design was ready, two weeks in he said to me that I have not done anything and i'm fired even though I had every day told him what i had done. Even now the "comic" publishing site is not finished and this was year ago. The reason why he fired me right after two weeks is because he tried to steal the code I had written and our contract had 2 week test period. I think he expected me to finish complex website where I needed to display images so that they could not be copied with any other way than print screen and you could only read first chapter as freebie to see if you want to buy more chapters.

2. What you say about deliverables might be true as a freelancer when you get to set how fast you work, but as I said already I have not met any managers who have let me plan my own milestones. If I run into roadblock of course I tell the manager, but I am not sure if he even understands what the actual problem is, but replacing a problem with other work is not the solution. The solution is to solve the problem which might take long time depending on the problem.

3. Yes they do pay me to work, but why the hell I should code 24*7 hours and get paid only for 8*5 hours. You know for example in sales you do not have deadline to sell something x amount in a week, because setting such deadline is basically impossible because you can not manage how many customers come in. You get paid for doing work and how much work can bee seen from the daily sales reports. I can always do similar reports for how much and what I have written code and what problems I have found instead of trying to work my ass off to meet some deadline so that I can keep my job. The employer always can watch the source control system if new source is being written and I can say I do commits quite often, basically always when I can compile and valgrind succesfully.

Sounds like you've been working for some bad companies. How's a manager supposed to plan out your tasks for a milestone when they're not programmers. A good manager will always come to the programmer for task planning and time estimates and work with the programmer to plan out a milestone.

In regards to replacing the problem with other work. Often a publisher will expect that if something is going to slide then they'll want something to replace it, so you pull back an easier task from later in the schedule and extend out the more difficult task so you do have the time to properly solve the problem. Though if you have a good relationship with the publisher then you can just explain the task is going to take longer early on and they'll be ok with it, really depends on who you're working with.

You should never work 24*7 and get paid for 8*5 if you're expected to do that again, you're at the wrong company.

Yeah well. Might be that my opinion of deadlines has been corrupted by working for wrong companies. Though once I finish my university I am going to start my own business and try to make it as comfortable working place as I can to my possible employees.