Reply to: I'm on fire

[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

[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

[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.

[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?

[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!!

[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.

[chef]

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

[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

[aussielong]

Hi aussielong! How's that lazy BA?

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.

[EternalOptimist]

Literally..

Thing is, if most developers were 'that' good, then it wouldn't take hiring another 1 or 2 devs to find one that can code efficiently the first time round. By my reckoning, if only 1 out of 3 writes efficient code (most likely lower), then most devs aren't worth listening to and the MDs and PMs are right to ignore

They listen to someone though, even if it is themselves.
In my case, the infrastructure guy had the MD's ear.
He is a dogmatic fellow and very inflexible. Most of what he says is true, but he was never prepared to break the rules, if the rules didnt work.
so when the performance hit the buffers, he had run out of ideas and the MD looked at me and said 'ok then , what have you got. You can have a week '

They all laughed when I said 'after a week, we will have to put a delay and an hourglass up, just so the users know the data has changed.'
well they aint laughing now

[CheeseSlice]

So listen up youse PM's and MD's

listen to the developers. they can make or break it.

Literally..

Thing is, if most developers were 'that' good, then it wouldn't take hiring another 1 or 2 devs to find one that can code efficiently the first time round. By my reckoning, if only 1 out of 3 writes efficient code (most likely lower), then most devs aren't worth listening to and the MDs and PMs are right to ignore

[Doggy Styles]

I didnt look at the ceiling or floor once. And I am giving the MD the credit for taking a punt

Only joking EO.

[EternalOptimist]

Hi aussielong! How's that lazy BA?

I didnt look at the ceiling or floor once. And I am giving the MD the credit for taking a punt

[Doggy Styles]

Hi aussielong! How's that lazy BA?

[MrMark]

Sometimes being quick isn't enough... but at least it's good news. Have a banana!