I'm on fire

[EternalOptimist]

I'm pretty good to the BA and PM. Truth is I believe they should be sacked.

I'm always punting at the level of over achievement. You can't keep a good man down. But liars and chancers dilute progress to everyone's detriment. Keep doing this and we have to let Bob in.

Grasping the problems at a fundamental level, seeing the big picture and the detail, understanding the application top to bottom and being able to effect large scale change with minimal or no collateral damage, is top MO. Most devs cannot do this in a nontrivial app. This is my main skill.

nearly a good point, nearly well made

[chef]

I thought this was going to be about having a wank after chopping chillies

[Lockhouse]

I'm pretty good to the BA and PM. Truth is I believe they should be sacked.

I'm always punting at the level of over achievement. You can't keep a good man down. But liars and chancers dilute progress to everyone's detriment. Keep doing this and we have to let Bob in.

Grasping the problems at a fundamental level, seeing the big picture and the detail, understanding the application top to bottom and being able to effect large scale change with minimal or no collateral damage, is top MO. Most devs cannot do this in a nontrivial app. This is my main skill.

[shaunbhoy]

I'm always panting at the level of over achievement. You can't keep a good man down. This is my main skill.

ftfy

Fnarr Fnarr!!

[doomage]

I have increased the performance of the main navigation from 4 seconds to .2 of a second AND made it future proof.

How'd you do it EO? Caching? Refactoring? Reducing calls to DB? Increasing calls to to DB?

Or did you do that trick of putting a sneaky sleep() method call in and then removing it?

[BrilloPad]

Sounds like Human Spontaneous Combustion.

Call the Fire Brigade, quick.

If only EO had not been wearing nylon underwear. This is why one should wear silk.

[EternalOptimist]

How'd you do it EO? Caching? Refactoring? Reducing calls to DB? Increasing calls to to DB?

Or did you do that trick of putting a sneaky sleep() method call in and then removing it?

'Slivers'
copyright EO 2012

calls to alien db taking 250 ms each, accumulating to a horrendous performance, and me having no control over that db.
So I check the timestamp on the 'sliver' that I am focussed on, if its changed , I grab that data only which takes 1500 ms, other wise I do nothing. Then I grab the whole lot overnight.

I know its not rocket science, but the point is... they let me have a shot and do it my way

[FiveTimes]

'Slivers'
copyright EO 2012

calls to alien db taking 250 ms each, accumulating to a horrendous performance, and me having no control over that db.
So I check the timestamp on the 'sliver' that I am focussed on, if its changed , I grab that data only which takes 1500 ms, other wise I do nothing. Then I grab the whole lot overnight.

I know its not rocket science, but the point is... they let me have a shot and do it my way

You da man