Re: RE: Re: RE: Re: RE: Re: RE: Re: RE: Re: Average speed

On 5/11/2025 7:21 PM, cyclintom wrote:

On Wed May 7 16:40:19 2025 Zen Cycle  wrote:

On 5/7/2025 4:16 PM, cyclintom wrote:

On Mon May 5 13:37:42 2025 Zen Cycle  wrote:

On 5/5/2025 1:25 PM, cyclintom wrote:

On Mon May 5 13:23:11 2025 Zen Cycle  wrote:

On 5/5/2025 1:14 PM, cyclintom wrote:

On Mon May 5 07:03:46 2025 zen cycle  wrote:

On 5/4/2025 11:47 AM, cyclintom wrote:

On Sat May 3 16:12:53 2025 Frank Krygowski  wrote:

On 5/3/2025 3:20 PM, cyclintom wrote:

The scum Flunky claimed that he averaged 20 mph on a 200 mile ride.

>
No he didn't. That idea popped out of your imagination - or perhaps some
other orifice.

>
>
>
>
Of courae, that is why he told me the average speed of an e-bike and then said "wow!"

>
I did? Please post a reference to where I ever claimed "WOW!" about a
17ish mph ebike ride.
>
I, in fact, claimed the exact opposite.

>
>
>
>
You seem to be having trouble following the conversation. When did I say that you said "Wow"?

>
*
    >> On 5/4/2025 11:47 AM, cyclintom wrote:
    >>> On Sat May 3 16:12:53 2025 Frank Krygowski  wrote:
    >>>> On 5/3/2025 3:20 PM, cyclintom wrote:
    >>>>> The scum Flunky claimed that he averaged 20 mph on a 200 mile ride.
    >>>>
    >>>> No he didn't. That idea popped out of your imagination - or
perhaps some
    >>>> other orifice.
    >>>
    >>> Of courae, that is why he told me the average speed of an e-bike
and then said "wow!"
>
*
>
This is like the time you wrote that being in the Garmin Beta program
made you a test engineer, then you denied you wrote it.

>
I forgot that I said that.

>
Right, you forgot what you wrote a mere two messages before that.
>

But the fact remains that you don't even know what a test engineer is.

>
I was originally hired here as a test engineer. I developed software and
hardware test procedures for the engineering technicians to do
engineering qualification testing, and I partially developed and then
fully maintained two manufacturing ATE fixtures (programmed in
LabWindows CVI) - since handed off and being maintained by the
manufacturing engineer.
>
I do know a test engineer is _not_ an end user who is asked to
participate in a beta program.
>
It seems to me you're the one confused over engineering niche
responsibilities.

>
So there is no reason for anyone to test a beta release. Gotcha.

>
Please point to where I wrote anything that even remotely resemble that.
>

What an ass.

>
Says the idiot who thinks I claimed there's no need for beta testing.
>

That must have been some software since you don't even know what a program is.

>
My employers - past and present - were/are quite satisfied with the
programming tasks I've been given.

    Then why don't you take a job that pays real money?

MY job pays quite well. Well enough for me to take a yearly vacation requiring a passport.

You have spent a great deal of time denying that I could ever have made as much money as I did.

I still do.

And I am still receiving offers though I don't want to go back to work for only $150,000 to $180,000.

bullshit

Abbott just sent me an offer a couple of days ago but it was someplace out in the valley and I sure as hell won't commute that far.

bullshit

Ford made me an offer and their development headquarters are over in Palo Alto It appears that what they are trying to build a large system using a bunch of embedded systems which probabiy isn't a cost effective method.

bullshit

Since you're this wonderful programmer you could get one of these $165,000/YR jobs.

Why would I take a paycut to move across the country to an area with a higher cost of living when I'm a few years from retirement?

Make up another of your dream worlds where I didn't do the jobs I said that then explain away the letters of references I have.

No make-believe necessary. Anyone who claims to be a programmer at the level you claim and doesn't understand the basics of software release methodology and process is obviously full of shit.