Thought of the day

OriginalGriff

If debugging is the process of removing bugs, is programming the process of putting them in?

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...

Afzaal Ahmad Zeeshan

Nope, both of these are not concerned with any bug at all. Bug is something we don't like, and want to remove it. You can say it like, if Google would get results of the stored password then it is a bug, otherwise Google knows everything and gives results to every query. :)

The shit I complain about It's like there ain't a cloud in the sky and it's raining out - Eminem ~! Firewall !~

Simon_Whale

OriginalGriff wrote:

is programming project management the process of putting them in?

FTFY

Every day, thousands of innocent plants are killed by vegetarians. Help end the violence EAT BACON

Kenneth Haugland

You're saying that it should be called con-gramming?

Kornfeld Eliyahu Peter

Not exactly - the bugs are there, you put code around (like the cheese with the hole in it...)

Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.

OriginalGriff

So you are saying that bugs are the basic unit of computing, without which you can't have applications? I think this says a lot about your code quality! How much to not tell your boss? :laugh:

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...

Kornfeld Eliyahu Peter

I always tell my boss, that if I do not include some bugs in my code I will not have any job tomorrow :laugh:

Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.

Gary Wheeler

For project management, the process is actually called enbuggering (short for buggering engineering).

Software Zen: delete this;

CPallini

Exactly! And it was a mission for one of my former work mates.

Nelek

OriginalGriff wrote:

If debugging debugger is the process of person removing bugs, is programming "monkey_liking_spaggetti_code" (a.k.a. only 1 neuron working at a time moron) the process of #§$%& putting them in?

FTFY

M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.

W Balboos GHB

Kland surbign etrognet savin! (soareye - steams to bee a burg on may spull chucker).

"The difference between genius and stupidity is that genius has its limits." - Albert Einstein

"As far as we know, our computer has never had an undetected error." - Weisert

"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010

Bergholt Stuttley Johnson

and to think I spent so much effort in my programming to avoid bugs and now you tell me that the Idea is to put them in, I wish people would make up their minds I can do that a lot quicker

You cant outrun the world, but there is no harm in getting a head start Real stupidity beats artificial intelligence every time.

Revon

I read somewhere that professionally written code has 1 bug every 10 lines, so I make a point of deliberately putting in 1 bug every 10 lines. It makes it much easier to find when debugging.

Bergholt Stuttley Johnson

does that apply to VB jockeys? as the last time I debugged some VB code I think it was closer to 10 bugs per line

You cant outrun the world, but there is no harm in getting a head start Real stupidity beats artificial intelligence every time.

Stefan_Lang

I always thought programming is the process of putting on weight? :~

GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)