In most cases it's how the idea, modification, improvement, what ever is communicated that determines whether or not it will get off the ground. I've proposed improvements to poor security procedures that were shelved because it was not requested by a customer or there was not enough time in the schedule. Then a year later a customer finds the flaw and it immediately becomes a huge issue! Of course it's fixed then. Usually at greater cost and under high pressure. Perhaps if I'd been a prophet of doom and painted a really black picture about the calamity that would arise from this bug then I'd have had a better chance to get it done when I spotted it. Unfortunately I'm not a good prophet of doom.
I'm also pretty poor at politicing for changes like this. It's very hard for me to quantify what would be saved if this were done the right way earlier. Since making the choice means that you take a different fork in the road. Who is to say that fixing the bug earlier didn't save you a lot of pain and suffering later. I guess in the security domain the OpenBSD crew usually gets to have the last laugh when an exploit is found and they post something like - "we fixed that 8 months ago". How much scrambling and wasted effort did their proactive approach save. Impossible to estimate, but I'd rather be in their shoes.
So it's probably a complex mixture of you, your boss, company policy, time, and money that determine if they listen and whether or not they act.
I'm also pretty poor at politicing for changes like this. It's very hard for me to quantify what would be saved if this were done the right way earlier. Since making the choice means that you take a different fork in the road. Who is to say that fixing the bug earlier didn't save you a lot of pain and suffering later. I guess in the security domain the OpenBSD crew usually gets to have the last laugh when an exploit is found and they post something like - "we fixed that 8 months ago". How much scrambling and wasted effort did their proactive approach save. Impossible to estimate, but I'd rather be in their shoes.
So it's probably a complex mixture of you, your boss, company policy, time, and money that determine if they listen and whether or not they act.
@Home will not provide static IP service at my
house because they know it is a residence, even
if I pay for it. Praying for DSL.