|
A selected set of programmers always exist who are always inclined to enrage us. A friend of mine, who is working in Bangalore in a small company wanted a third party review of a bit of code. I helped him out during the previous weekend.
A very interesting observation. A developer had accessed a particular DB item from Cache. When we asked him what happens if the Cache gets NULL, he was telling the following points:
1) The cache never gets NULL.
2) When the cache item *misses out*, we have to restart the IIS or Windows so that on next attempt, cache would be replenished.
A simple automatic NULL check, cache replenish and DB call was at all required. I don't know what caused him to spin this story. I guesses are:
1) He was trying to 'cover' his blunder.
2) He was sincerely ignorant over the Web fundamentals.
3) He was of the opinion that We, the Web server administrators and program managers are just dumb cabbages who have nothing to do but just have thier asses glued to the chairs near the server monitor 365x24x7.
Any other speculations?
|
|
|
|
|
Nah, all you have to do is recycle the application worker process more frequently than the cache expiry time 
Assuming ASP.NET of course.
|
|
|
|
|
And have a whole football park full of servers to keep the website running...
I bet Bill has some cash lying around somewhere.
WM.
What about weapons of mass-construction?
"What? Its an Apple MacBook Pro. They are sexy!" - Paul Watson
My blog
|
|
|
|
|
Vasudevan Deepak Kumar wrote: dumb cabbages who have nothing to do but just have thier asses glued to the chairs
Said idiot needs to look in a mirror.
--
You have to explain to them [VB coders] what you mean by "typed". their first response is likely to be something like, "Of course my code is typed. Do you think i magically project it onto the screen with the power of my mind?" --- John Simmons / outlaw programmer
|
|
|
|
|
dan neely wrote: Said idiot needs to look in a mirror.
|
|
|
|
|
The guy who thinks that "Web server administrators and program managers are just dumb cabbages who have nothing to do but just have thier asses glued to the chairs near the server monitor 365x24x7." is a dumb cabbage...
--
You have to explain to them [VB coders] what you mean by "typed". their first response is likely to be something like, "Of course my code is typed. Do you think i magically project it onto the screen with the power of my mind?" --- John Simmons / outlaw programmer
|
|
|
|
|
Unfortunately, in this part of the world (Chennai, India) people have that base opinion. I admit and fully support you in branding them as dumb cabbages or also as smart-ass***es.
They fail to understand that our work is more critical in providing a more resilent image to the customer. A website is a 24x7 office for an enterprise. Even a little downtime costs the enterprise badly.
But how do you make the swine to understand the greatness of pearl. It is a futile exercise right? 
|
|
|
|
|
Vasudevan Deepak Kumar wrote: But how do you make the swine to understand the greatness of pearl. It is a futile exercise right?
Probably. I'd recoment the usage of large blunt objects. It won't be any more effective than other approaches, but will at least give you higher job statisfaction. 
--
You have to explain to them [VB coders] what you mean by "typed". their first response is likely to be something like, "Of course my code is typed. Do you think i magically project it onto the screen with the power of my mind?" --- John Simmons / outlaw programmer
|
|
|
|
|
Vasudevan Deepak Kumar wrote: But how do you make the swine to understand the greatness of pearl. It is a futile exercise right?
Sometimes people just need to make mistakes that cost them money/time/injury before they understand the issue. Or use the following: Now that they have the pearl, take it away from them.
Phil
|
|
|
|
|
Vasudevan Deepak Kumar wrote: He was of the opinion that Web server administrators are dumb cabbages who have nothing to do but just have thier asses glued to the chairs near the server monitor 365x24x7.
Don't you mean 24x365 ?????
365 days X 24 hours instead of 365 days x 24 hours x 7 days
Greets! Joel
|
|
|
|
|
They are glued to their chairs for periods of seven years at a time -- after which they are allowed to visit the soda machine for one hour.
|
|
|
|
|
Even worst for them jejejejeje ... I wonder how often can they go to the restroom
Greets! Joel
|
|
|
|
|
jcdevnet wrote: how often can they go to the restr
That's terrible right? You need so much of room fresheners to keep off the odour! 
|
|
|
|
|
That's what it says in the contract, but they do get free soda and diapers
I'm largely language agnostic
After a while they all bug me 
|
|
|
|
|
Still, I'm not signing for that job 
WM.
What about weapons of mass-construction?
"What? Its an Apple MacBook Pro. They are sexy!" - Paul Watson
My blog
|
|
|
|
|
No kidding. I bet it starts to smell after a short while...
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
|
|
|
|
|
MidwestLimey wrote: free soda and diapers
|
|
|
|
|
well said PhilDanger
Regards,
Satips. ![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)
Don't walk in front of me, I may not follow;
Don't walk behind me, I may not lead;
Walk beside me, and just be my friend. - Albert Camus
|
|
|
|
|
Vasudevan Deepak Kumar wrote: A very interesting observation. A developer had accessed a particular DB item from Cache. When we asked him what happens if the Cache gets NULL, he was telling the following points:
1) The cache never gets NULL.
This is precisely where you smack him upside the head with a baseball bat and ask him to repeat what happens when the Cache is empty. Repeat this process until he figures it out.
|
|
|
|
|
When the cache gets NULL the DB goes to the bank to get more?
|
|
|
|
|
He probably asked on CP and was given a link to a thread saying something like, "always hit the cache!"
|
|
|
|
|
Nah, probably more like an MSDN article!
|
|
|
|
|
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
|
|
|
|
|
Security? Security?
`Security' isn't a dirty word, Blackadder. `Crevice' is a dirty word, but `security' isn't.
Where I work there are several chiefs, but only one indian - namely me. Now these "chiefs" are all highly "experienced", so clearly what I suggest is completely without merit.
Such as when I suggested that Application Security and User Permissions should be handled in the Application, and not left to the Database's role management, this was rebutted with "in all the applications I've ever worked on, that approach has never been successful".
And when I suggested that the Application should have one, limited!, user account/role in the Database, this was laughed off, and in went the developer creating a seperate database account for each and every user.
And then, when I was reaching the end of my tether, I suggested that password security was absolutely critical, I was later surprised to find in the registry, under the application's settings a Key containing connections. Further investigation showed that each connection contained the user name and PLAIN TEXT password for each user, including the Administrator. And not just an Application Administrator, but a fully fledged SQL Server 2005 Administrator.
  ;P
|
|
|
|
|
Wow. The only way to improve on this would be to have the sa account use the same password as all the users, and for that password to be password.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
