BreakPoint
Pet peeves when providing technical support: ... "your software doesn't work!"
@Ray.R wrote:
@altenbach wrote:
@RavensFan wrote:
I'm curious as to how you managed to that to a truck rin.
I am wildely guessing the wheel came off while driving and the lug studs landed on the inside of the rim, causing the hole and all the scratch marks. 😄
I'm thinking brake assembly (pads?) came loose and had a close encounter of the worst kind...
I'm pretty sure the asle neighbors I had for a while cracked the lugnuts loose when they got evicted. Nothing but problems with those people for the months they lived next door, then the next time I drive the truck after they get kicked out, this happens...
Couple of studs sheared off, no lugnuts left on the ones that were there... I check them on the truck and trailer every time I hitch up, but usually don't bother for trips around town. That's not really the sort of thing that "just comes loose" when you check it every couple months.
Without lugnuts holding the wheel on, the brake disc smashed through the rim when it slipped off the studs. Couple of revolutions around the rim, then the wheel took off into the meadow.
Picked up and threw the tire that decided to free itself into the bed of my truck, pulled a lug nut off each of the other tires, and put the spare on. Got the truck to a buddy's shop in town, he and I went to the auto parts store and picked up some studs/lugnuts, spent an hour at his place pounding out the old studs and putting on some new ones.
New rim, new hub/bearings, new brake disc later that week... but no more bad neighbors!
Just a roid-raged lunatic.
The week they moved in, we were both outside... My "Hey, how's it going?" question was met with a glare. Allright, whatever.
Weeks went by, kind of just left each other alone...
About a month later I'd open my front door and he'd be staring at me, flipping me off from his windows anytime I went outside...
Eventually he'd start yelling at me, flipping me off... then starting to pick fights with me.
Now keep in mind I'm usually wearing motorcycle gear, helmet, camera on my helmet, with a sidearm under my jacket...
There's a sidewalk that goes in front of my building, and another sidewalk that goes in front of his building. There's a small yard between the two walks. Teeing off those walks towards the street is an entry to the garage doors. I was going between my house and to the garage one day, when he comes out and starts picking a fight with me. My garage door was locked, I'm on that tee, and he's at my sidewalk... got me cornered and I'm not turning my back to him to unlock the door. Fortunately for both of us he had the sense to stand there, make a lot of racket, huff and puff, and not engage any further.... I was condition-zero code-orange ready to go.
My neighbors were already on the phone with the police, watching the drama unfold from their kitchen window. Once he backed off, I went into the garage and called the police myself.
This happened weekly. For several months I never left the house without a camera (or handgun, but I carry that anyways). Talked to a lawyer, explained the situation, showed her some videos, went over self-defense laws again, and gave her a login where I throw helmet cam videos should something happen.
The neighborhood rejoiced when they got evicted. The new renters there now are pretty cool people.
The truck thing was small-fries compared to the stress of potentially engaging with this neighbor every week.
Sled's about there. Got a box of parts, just need a solid weekend where I don't have to deal with truck/bike/photos/etc to spend some quality time in the garage with it.
Just turned my smuggy account onto pro last night, which enables commerce features... already made some $$ out of the photos I shot at the race last week. 
@EvenDeejay wrote:
I think this picture fits this topic 100%
You can't make anything idiot proof because idiots keep finding new ways to break your stuff.
Why do I feel like I'm entering a Tron debate?
I recently performed some LabVIEW work for a chap who had very little exposure to LabVIEW (although he was a bit of a programmer - his words). On a simple VI he had created he needed a way to pause a counter, and reset a latched alarm boolean. I added some simple code, it worked fine, he was happy. Two days later, the reset button was no longer selectable. Before he called me to investigate why the button was no longer working, he had enjoyed telling all his colleagues in his office that his part of the code was working great but the bit the 'Champion' added was broken. When he showed me the VI it turned out he'd moved the button label from above the control down a bit so that it was overlapping the control. Consequently, the only way to select the button was to select the edge that was visible around the label string.
Yes, in hindsight, I should have enabled Boolean text and hidden the label, but I was trying not to use certain features that might confuse him. In the end that meant I had to support him when he went to 'improve' it and ended up breaking it.
We implemented a TestStand system for one of our clients and one of the days they called me up to say that they needed to add a new User and that the admin password was not working. I remotely logged in and was able to login straight away!
I couldnt figure out what was happening, I added the user remotely and assured him we will fix it the next time we are on site.
I got a text from him later saying, "Ah forgot that I need to press the shift key for the @ symbol!"
