|
lopatir wrote: all will be fine, happy and good until the day you need to make a claim.
A couple of supporting stories:
1. My mom was sitting in her car in a parking lot one time. She hadn't even put the keys in the car. A wild-driving kid raced up fast into the parking space behind her and didn't stop in time and bumped her. She got out and talked to the kid and there was no damage at all. She let the kid go, not trying to make a big deal of it. But then after he left she thought, "what if he says I hit him or something?" She called her insurance company just to ask about it.
3 weeks later her rates went up. She called and asked why and they mentioned the parking lot incident. Monsters! 
2. My son was driving on a street with no stops signs or lights or reasons to stop. A guy in a large truck, waiting in a parking lot, pulled out in front of my son. He slammed on brakes and slid and almost missed the guy, but he just touched the guy's truck.
The guy went crazy saying that my son hit him. My son said, "there's not damage and I'm in a hurry to work, why even get police involved?"
The guy went nuts.
Police came and the guy was arguing and yelling. Policeman said, "there's no damage and you pulled out in front of him." Guy kept yelling.
The policeman came to my son and sheepishly said, "I'm not going to cite anyone, just to get him to calm down."
Days later our insurance called us and said, "Hey, your son had a wreck."
The other guy had reported it to his company -- it was their truck and he was late to work and needed an excuse. Company called police and got report and reported it to insurance.
No one was cited. Because the other company reported it our insurance company said he was involved in a wreck. Rates went up. Monsters!!
We should've fought to have the other guy cited. But we were being nice to the policeman trying to help him get the guy calmed down. Terrible!
|
|
|
|
|
I feel your pain...
Years ago I parked near a customer workshop, the car was parked near a tall wall (10 meters +/-) on top of that wall there was a house where two old persons lived.
I went to work and after some hours I left.
When I entered the car I started it and I heard a super loud noise when I started to move... Of course I step down the car and went the other side (the side near the wall).
I saw all the car side completely devastated... no side mirror, my rear bumper touching the floor and the front bumper under the front wheel...
That day there was a lot of wind and those lovely couple had a big bar "fixing" a provisional roof... With the wind the roof flew and the bar fell down against my car... bouncing several times between the wall and the car...
Of course I went to those old people house and told them what happened.
They were super worried and scared and gave me their insurance contact and details.
They called their insurance to explain what happened.
I called them a couple of days after.
They told me unless I would denounce them they wouldn't move a finger...
After 4 years, my insurance called me to ask my bank account to send me the money of that accident.
I got the money, but it was terrible to see how they made those old people suffering for nothing...
They are not monsters... that is not close enough of what they really are...
|
|
|
|
|
sames can apply to internet providers too
New customer... big deals.
Old customer... screw you.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
This applies to any large subscription model, existing customers you slowly (or not) creep up the premium/renewal cost. New customers get an introductory price, it's all about expanding the subscription base and a large % of customers just renew without any research.
As for the comparison sites they are not always good. Recently renewed our house insurance and the comparisons were 40% higher than my current premium. I rang up and bitched at them anyway and got it reduced by over $700.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
I went off road, unintentionally a couple of weeks ago. My car was valued for insurance (based on their evaluation) at £2400, but its list price magically changed to £1050 when they came to pay me for it being written off. I don't quite know how the system works but I've also been getting lots of calls from companies claiming they have been authorised by my insurers to get money back from the other parties involved in the incident; which is odd as the insurers know that there were no other parties. These other companies then have the gall to ask about other occupants in the car (so they can get them to make claims against me), even though the insurers know that I was the sole occupant. [Just in case anyone cares: The car was a write-off, but I walked out unscathed (I had to clamber over to the back seats to get out as both front doors were too smashed up to open)].
|
|
|
|
|
It's funny how that works, isn't it?
They are perfectly happy to accept your estimate of value when quoting you for cover, but only accept theirs when it's time to pay up ... I've noticed that a couple of times with motorcycle thefts. 
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
So, I'm tripping through an older (written circa 2011) command line utility program written in C and developed under MSVC (I think, because all I got was the source code but there were some variables and defines that looked like that might have been the environment) and I get the compile error message "c1061 compiler limit blocks nested too deeply".
This is a new one on me! So, I started digging into the code and it turns out that the original developer had written his code for command line option processing as:
for (;;) {
if(..) {
}
else
if (...) { // Occasional do while/until loops inside the if
}
else
if (...)
.... 187 TIMES!!!
}
}
MSVC 2017 has a hard coded limit of 128 nested blocks!
My question: How can someone produce that kind code and still call themselves a professional developer?
It's scary that maybe this individual might now be developing code for a self-driving car.
|
|
|
|
|
rjmoses wrote: .... 187 TIMES!!!
...
My question: How can someone produce that kind code and still call themselves a professional developer?
you think an amateur could do it that many times without making a mistake?
old days people put pride in their work and crafted thing by hand,
now it's all mass produced by machines.
"professional" does no justice, artisan, master ....
Message Signature
(Click to edit ->)
|
|
|
|
|
|
As I overheard from one who used to put out oil well fires: “if you think it’s expensive to hire a professional to do the job, wait until you hire an amateur.”
modified 5-Jul-19 1:59am.
|
|
|
|
|
rjmoses wrote: How can someone produce that kind code and still call themselves a professional developer?
Because the code compiles? 
|
|
|
|
|
Not anymore (until I changed it.)
|
|
|
|
|
rjmoses wrote: It's scary that maybe this individual might now be developing code for a self-driving car.
If that's the sort of code it's running, then don't worry - that car won't be driving itself for too long. It'll probably drive itself into a phone pole at high speed before long. Intentionally.
|
|
|
|
|
If I was a car running that kind of code, I WOULD drive myself into a tree.
|
|
|
|
|
If you were a car running that kind of code, you'd miss!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
187 TIMES
Achievement Unlocked
|
|
|
|
|
It's good to know someone else experienced my pain. But mine was way back in the mid 1990's with the Microsoft C 5.1 compiler. You'd think they would have fixed that since then.
|
|
|
|
|
for(try to drive)
if tree brake
if chimney fly
if fire hydrant brake
if human brake
if cat go to did no see
if bird
try
catch
else
throw error
call horn
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Nah.
The whole thing is probably:
On error Resume Next
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Lol! I'd prefer a bunch of GOTO statements in this predicament.
|
|
|
|
|
I saw something akin to this once:
for (int x = 0; x < 5; x++)
{
if (x == 0)
;
else if (x == 1)
;
else if (x == 2)
;
else if (x == 3)
;
else if (x == 4)
;
}I went home early because it scared me.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
rjmoses wrote: .... 187 TIMES!!!
Who uses an odd number? At least use 192.
|
|
|
|
|
Who says this guy (or girl) doesn't have a Bachelor's (or Master's) degree in programming?
It wouldn't be the first time I see a "licensed" programmer producing code like that 
I once worked with someone who was certified and expensive and wrote a separate service that was so bad it negated future development.
Like literally, we added some fields to the database, filled them with data, and half an hour later that service would set the fields to NULL again.
Took me a while to find that one
You can imagine that wasn't the only WTF in that code base...
Then there's this guy who was equally certified, full of himself, called me "a little man", and then made an unsolicited code change that broke production 
The reason he made the change is because I had wrote a function containing something like 30 lines of code (including white lines and curly braces), which he thought was bad practice.
After he "refactored" it he took out the "usings" because ".NET handles that for you".
He also somehow added an additional database call and discarded the results, which actually broke it.
And then we had the fourth year application developer intern who literally couldn't declare a variable because "he forgot the syntax".
Needless to say we failed him, but somehow he passed his next internship and a year after he couldn't declare a variable he was applying for a job at some big company 
Don't speak to me about "professional licensing", people are bunglers and no amount of licensing can fix that
|
|
|
|
|
You speak the truth. University degrees, licensing and certifications don't guarantee competence. I think that any of us including all of the people in this post would be surprised at what another programmer would find to criticize and complain about in his or her code.
Also, anyone that would get in a self-driving vehicle deserves to run into a tree, in my opinion. 
Hard work and common sense will overcome in every situation, every time.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
