You shouldn't have too much time for doing it | Hacker News Reader

You shouldn't have too much time for doing it

blog.karolzielinski.com

I couldn't quite understand the message due to all the extraneous commas, but it seems to be the same one Ferris talks about in 4 Hour Work Week.

Also, it mentions unexpected crap popping up but not how to deal with that. It's like, OK, let's add some more time to our project schedule. But wait! We gotta take some off due to Parkinson's! You end up with the same damn schedule.

I really think this piece would be a lot better if it had been thought about/revised more, 'cause as it stands it can only serve to reinforce whatever point the reader -thinks- it's about.

I can't agree with you. It's not like "OK, let's add some more time to our project schedule. But wait! We gotta take some off due to Parkinson's! You end up with the same damn schedule." because we are not talking about schedules of external projects. We are talking about our own projects or tasks from our lifes. We are talking about being productive and not wasting a time for unnecessary works.

When you are working on external projects (however not only) you put more time to schedule, because you are afraid about the unpredictable things. All of that is because all delays cost you lots of money. However in many cases you don't need to do it. In many cases finishing tasks as soon, as it possible is much more important than having some time, which was scheduled for something unpredictable. Especially when you are working on your own projects.

That's the point of Parkinson's Law.

I'm sorry, I still can't quite understand what you're saying. However, I now know that you're not a native speaker, so I can't really hold it against you.

But your blog still can't be popular among people who can't understand it. Do you know any native speakers you could converse with to try to improve your knowledge of the language?

Reply on news.ycombinator.com