|
Nagy Vilmos wrote: Malaysia was an easy drive;
Did you drive in Kuala Lumpur ? 
|
|
|
|
|
Not the far up, just from Singapore up as far as Mallaka.
veni bibi saltavi
|
|
|
|
|
Then you have no right of speaking  melaka to Singapore is mostly highway if I recall .
(Although I have a nice highway story as well  )
|
|
|
|
|
Nagy Vilmos wrote: Egypt can offer some interesting challenges
Please not as interesting as driving in India. I always need a day or two to orient myself and mentally preapred when I go in for my annual vaction to India and come back to germany
cheers,
Super
------------------------------------------
Too much of good is bad,mix some evil in it
|
|
|
|
|
I find the worse drivers are those who aint concentrating because they're to busy compiling lists of the worst drivers.
|
|
|
|
|
Nagy Vilmos wrote: Belgium needs to stop driving.
Hahahahahahahaha - they're filthy casuals by Middle Eastern standards. Hell, Italian driving (the worst I've seen in Yurp) is casual by Middle Eastern
|
|
|
|
|
I see you're using DENSE_RANK[^] instead of RANK[^].
Normally, you would count the number of items that are ranked higher - if two makes are joint second, the next should be fourth, not third.
You also forgot to start the list at 0.
4. Merc
3. BMW [a rare drop from the top]
1=. VW
1=. Skoda
0. Audi
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Nagy Vilmos wrote: If I hadn't I, along with my family and the kunt in the other car, would be dead.
I have had a couple of situations like that, with my family. Someone was watching out for you and your family, and it sure wasn't Dave.
|
|
|
|
|
Several years ago after receiving a speeding ticket, I decided that would be the last one and now refuse to go any faster than the posted limit. As for those rude, impatient drivers who flash their lights, honk their horns, or get so close that you can't even see their headlights, I have four words for 'em. Have a nice day! 
There are benefits, besides no tickets, for not speeding...the wife can't stand it and insists that you are allowed 7 mph over the posted limit, so she does most of the driving!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Spooner's masculine condition has reached an impasse (9)
Good luck!
You have just been Sharapova'd.
|
|
|
|
|
Stalemate?
Spoonerism of Male [masculine] and state [condition].
veni bibi saltavi
|
|
|
|
|
You are up tomorrow.
You have just been Sharapova'd.
|
|
|
|
|
It will be a pleasure to think of a clue. It may possibly be offensive to the entire country of Belgium.
veni bibi saltavi
|
|
|
|
|
They do deserve it: they named the whole country after the rudest word in the entire universe.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Prejudice[^] 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
"...and our first contestant is a hairdresser from *BANG*"
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Message Closed
modified 13-Apr-15 3:58am.
|
|
|
|
|
I heard this phrase recently and it struck a chord. As software developers we are passionate about what we do, trying to build the best solutions we can with the tools at our disposal. We try to employ good software practices through the use of design patterns, abstractions, re-usability, loose coupling etc. We try to come up with the best design we can to fit the problem at hand.
When we blindly implement whatever can of spaghetti is asked of us, then we have reached the point of software bankruptcy. Anything goes, no matter how much of a maintenance nightmare it might produce, no matter how big the ball of mud it will create.
Pressure from the business to meet a deadline is often the trigger for bankrupt software. But equally, we need to stand firm and make a stand for quality. If we fail in that task, can we really call ourselves professionals?
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Dominic Burford wrote: If we fail in that task, can we really call ourselves professionals
Yes, the fact that you have made the effort to inform management of the problems with building bankrupt code to meet a deadline is a professionals job, building the best application they can WITHIN the constraints of the business is also his job.
Management has different priorities to a developer and they are the ultimate authority on a decision, they hold the pay packet after all.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
If you escalate the issue (with required evidence) you'd be surprised how flexible the priorities of your management can turn out to be
|
|
|
|
|
Duncan Edwards Jones wrote: you'd be surprised how flexible the priorities
Not if they are a half competent management team!
I got to admit I negotiate for the longest deadlines I can get them to agree to then ignore them. I find delivering reasonably elegant code generally takes less time than spaghetti anyway. I will also refactor instantly when I identify a bad design.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
If a team of civil engineers proceeded ahead and built a bridge that they knew was of insufficient quality due to its poor design and materials, and that the bridge therefore risked failing (and posing a potential risk to public safety). Do they get off the hook simply because "they were told to do so" by their paymasters?
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
You point out the risk to management and depending on your level of responsibility you make a stand, if you identify it as a public safety risk you make a stronger stand!
Most of us do not work on applications where "public safety" is an issue, I certainly don't, so it is not an argument I have ever had to consider (I sound like a weasely politician bleh).
I have refused and quit when I considered the management requirements too outrageous, but never because there was any threat to life and limb.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Ha, of course not. You know how responsibility works, right?
The Fall Guy will be selected from the bottom of the chain of command, never the top.
|
|
|
|
|
In reality there are cases when the management makes decisions (mostly not proved to be right after then) that this specific feature must be developed immediately! In such cases the only thing you can do is inform them - in written form - about all the mess it involves, then done it...But that makes you no non-professional...The fact that you see the problems points out that you are a professional...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
