On 25/10/2011 05:00 PM, Darren New wrote:
> On 10/24/2011 0:58, Invisible wrote:
>>>> Why did you even apply?!" I'd feel like I wasted everybody's time.
>>>
>>> What if they said "We'll give you $150,000 more each year to move to
>>> London"?
>>
>> That's almost a hundred grand in UK currency. Nobody earns that much.
>
> I earn more, and I'm at the low end of the scale for what I do. No, you
> probably won't earn that much because you don't have the experience, but
> maybe you'll get something more significant than what you have now.

I'm sure very few places pay *less* than what I'm earning now. Back when 
I was actually having agents contact me, I was asking for roughly twice 
what I currently earn - and nobody seemed that surprised by such a 
figure. But ten times? That seems a stretch.

>> AFAIK, London is their only UK presence. (Although obviously they
>> themselves would have a better idea than I do.)
>
> Indeed. There are lots of companies that have offices where you wouldn't
> have thought they have an office. Like, the office I'm in now. They
> don't really advertise where they have offices.

Korg's UK headquarters are just down the road from me, in fact.

It's a 1-room office. I've been there.

>> And it's not that I don't ever want to come to London, just that I don't
>> want to do so with any great frequency. Once per month wouldn't be so
>> bad. Once per day would be.
>
> How far away is it? Get a place in London, come home on the weekends, or
> for dancing.

I'm not sure how far it is to central London. I know that my 
grandparents live just on the outskirts. It's 40 miles in distance, and 
yet it takes between 1.5 and 2 hours to drive there. (!!) I also know 
that a train trip is about an hour. (Once you've waited an hour for a 
train to actually show up...)

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

On Tue, 25 Oct 2011 20:58:41 +0100, Stephen wrote:

> On 25/10/2011 6:59 PM, Jim Henderson wrote:
> 
>>>> Indeed that's a "problem" with living in a country that has a long
>>>> history.
>>>
>>> Or an advantage if you are that way inclined. I lived in a new town
>>> for four years. To me it was soulless and boring beyond belief, I was
>>> even glad to move to Aberdeen. It is just a point of view.
>> Well, that's why I said "problem" instead of *problem*. ;)
> 
> Tell an old man what the difference is between
> 
> "problem" instead of *problem* ?

"problem" is with 'air quotes'.  *problem* is emphasized.  I guess what 
I'm trying to convey is that the two statements:

Indeed, that's a "problem" with living in a country that has a long 
history.

Indeed, that's a problem with living in a country that has a long history.

The first uses "problem" in a non-literal sense, almost an ironic sense.  
As if to say "some might think it's a problem, but I don't consider it 
so".

Clearer? ;)

>> I tend to agree, I like having older buildings around.  However, having
>> lived in a somewhat older house (by US standards), I think the decision
>> to go for something more modern in the next place (a flat, no less) is
>> right for us. :)
>>
>>
> I like living in flats, I've never lived in a house with a garden.

It's a lot of work. :)

Jim

Post a reply to this message

On 25/10/2011 11:44 PM, Jim Henderson wrote:
> "problem" is with 'air quotes'.*problem*  is emphasized.
Just checking that the language hasn't changed again. :-)

-- 
Regards
     Stephen

Post a reply to this message

On Wed, 26 Oct 2011 11:12:07 +0100, Stephen wrote:

> On 25/10/2011 11:44 PM, Jim Henderson wrote:
>> "problem" is with 'air quotes'.*problem*  is emphasized.
> Just checking that the language hasn't changed again. :-)

We need an 'inotify' for the langauge, don't we? ;)

Jim

Post a reply to this message

On 10/25/2011 10:17, Orchid XP v8 wrote:
> But every other city I've ever seen just look old and run-down.

Move to the west coast of the USA.  "Hey, we have this really old cathedral. 
It was built even before WWII, can you believe it?" ;-)

-- 
Darren New, San Diego CA, USA (PST)
   People tell me I am the counter-example.

Post a reply to this message

On 10/25/2011 9:23, Jim Henderson wrote:
> It's been my experience that in far more cases with Windows admins than
> with those of other systems, "reboot the system" becomes the "fix" rather
> than trying to troubleshoot it.

Well, yes. I'll grant you that.

> Once upon a time, I worked for a Fortune 50 company with several thousand
> Windows servers.  Informix was running on them, and there was a memory
> leak.  "Reboot the system" was the "fix", to the extent that the reboot
> was scripted and scheduled to run nightly.

Same with Linux set-top boxes I was working on. Because we didn't have the 
source to the code that was leaking the memory.

And indeed, I was working on one Linux server system where they were 
catching sigsegv's and outputting "caught a signal!" to stdout, but then not 
actually recovering. So I had to pipe the output into a second process *I* 
wrote that would grep for that string and send a kill -9 and restart it when 
it got stuck.

It's not Windows per se, but proprietary software that you can't fix.

> Now, part of the reason for that was that Informix was taking their time
> fixing the problem

There ya go. :-)


-- 
Darren New, San Diego CA, USA (PST)
   People tell me I am the counter-example.

Post a reply to this message

On Wed, 26 Oct 2011 13:43:47 -0700, Darren New wrote:

>> Once upon a time, I worked for a Fortune 50 company with several
>> thousand Windows servers.  Informix was running on them, and there was
>> a memory leak.  "Reboot the system" was the "fix", to the extent that
>> the reboot was scripted and scheduled to run nightly.
> 
> Same with Linux set-top boxes I was working on. Because we didn't have
> the source to the code that was leaking the memory.
> 
> And indeed, I was working on one Linux server system where they were
> catching sigsegv's and outputting "caught a signal!" to stdout, but then
> not actually recovering. So I had to pipe the output into a second
> process *I* wrote that would grep for that string and send a kill -9 and
> restart it when it got stuck.
> 
> It's not Windows per se, but proprietary software that you can't fix.

Exactly. :)

>> Now, part of the reason for that was that Informix was taking their
>> time fixing the problem
> 
> There ya go. :-)

Yep.

Jim

Post a reply to this message

On 26/10/2011 09:43 PM, Darren New wrote:
> On 10/25/2011 9:23, Jim Henderson wrote:
>> It's been my experience that in far more cases with Windows admins than
>> with those of other systems, "reboot the system" becomes the "fix" rather
>> than trying to troubleshoot it.
>
> Well, yes. I'll grant you that.
>
>> Once upon a time, I worked for a Fortune 50 company with several thousand
>> Windows servers. Informix was running on them, and there was a memory
>> leak. "Reboot the system" was the "fix", to the extent that the reboot
>> was scripted and scheduled to run nightly.
>
> Same with Linux set-top boxes I was working on. Because we didn't have
> the source to the code that was leaking the memory.

> It's not Windows per se, but proprietary software that you can't fix.

One of our production systems is a crappy little thing written in VB. 
Roughly once a week somebody over in the USA files a helpdesk ticket 
saying "please reboot it". Apparently it leaks memory until it stops 
working. Reboot the server and it works again.

(What I can't figure out is why just restarting the program itself 
wouldn't fix that...)

Post a reply to this message

On 10/27/2011 1:13, Invisible wrote:
> (What I can't figure out is why just restarting the program itself wouldn't
> fix that...)

It probably would, unless it's a service that's leaking memory, in which 
case restarting the service *should* work.

-- 
Darren New, San Diego CA, USA (PST)
   People tell me I am the counter-example.

Post a reply to this message

On 27/10/2011 05:15 PM, Darren New wrote:
> On 10/27/2011 1:13, Invisible wrote:
>> (What I can't figure out is why just restarting the program itself
>> wouldn't
>> fix that...)
>
> It probably would, unless it's a service that's leaking memory, in which
> case restarting the service *should* work.

As best as I know, it's a user GUI application. I'm not sure why the 
hell just logging out and logging back in again doesn't fix it, but 
anyway...

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message