What exactly is the problem with someone padding their estimates knowing there is a risk of being stuck creatively? When it happens, the estimates stand, when i

What exactly is the problem with someone padding their estimates knowing there is a risk of being stuck creatively? When it happens, the estimates stand, when it doesn't, work is done faster than expected. If the parent is unfortunate enough to have to report their progress constantly, what are they supposed to do instead of bullshitting? To me that seems like a problem with their organization. What's important in terms of professionalism beyond getting work done in the time estimated? I find it bewildering that anyone would consider a completely understandable, honest testimony shameful and unethical. I'm quite happy the parent shared this as a lot of developers feel quite a bit of pressure when slumps happen, thinking that it's abnormal when it's really quite common (and really for any type of creative work).