KISS principal

conception_native_0123

Well-known member
Local time
Today, 12:17
Joined
Mar 13, 2021
Messages
1,923
i saw this when i look something up on wikipedia today and doc man once told me something about us navy. i thought it was interesting because it say that us navy invented it in 1960

 
It is an excellent approach to your coding. I note that some programmers seem to think if their code looks complicated then it's better. I've never been able to understand this! One piece of code which pops up frequently on Access World Forums, a piece of code that causes people no end of problems is the Insert INTO SQL Statement. It used to cause me problems until I broke it up into smaller bits, rebuilt the bits to make the finished SQL Statement. It's much easier to handle in smaller bits. Easier to spot errors, and to my mind it's quicker, even though there's more code. The main reason it's quicker is I have a standard template which I just drop into my database, then modify that to build the insert into SQL statement.
 
I have seen people of ALL ages write ... how shall I say this politely? ... inelegant code. Age has no monopoly on bad code.

As to writing a string of negations, it occurs most often because people either didn't take as much as an overview course in basic logic operations or they did take the course but forgot it when the course (and exam) were over.

The KISS principle applies to all sorts of things. Even to lies. When someone tells a lie and it gets complex, they will stumble all over themselves. For instance, it is one way police decide when someone is lying. If the suspect can't keep their story straight, it is because they were making it up as they spoke.

Then of course there are the simplest lies of all to detect, and the test is incredibly simple: How do you know if a politician is lying? His lips are moving. See? Nothing could be simpler.
 
How do you know if a politician is lying? His lips are moving. See? Nothing could be simpler.

when your job is cover up the truth of "this world is not my fault", lying is necessary. you get shot otherwise. sad thing thouggh....politicians are the basic cause of world the way it is.
 
Lying is a very necessary social tool to grease the wheels.

The age old question, does my bum look big in this?

The answer wether yes or no is based on perspective. We are all individuals and we see things differently so the answer, negative or positive are both equally true depending.

So one person will hear the politician lying and another person will hear the politician telling the truth.
 
KISS has similarities with Occam's Razor.
 
When I was learning to write in PAL (Paradox Application Language), all the books I read (the internet was not for us common folks yet) advocated LAW over KISS. LAW = Least Amount of Work.

With the DOS OS limitations, system resources were precious and the less strain you put on it, the better.

When I started dabbling with Access/VBA, the world had moved on and LAW was not a consideration anymore.
 
I assume you mean Least Amount of Work for the computer, not the programmer?
 
easy on the schmuck writing code too!

Coding becomes easier once you understand that there are many rabbits holes you can fall in to.

You must take a step back, look at what you have done and are doing, are you really going in the right direction? Should you stop and start again? That's the hardest thing to make yourself do, but it is generally the best thing.
 
One of my personal KISS idiosyncrasies is the "IF" statement. I minimize my use of the "IF" statement to the simple structure of "if this, else ..". Anything more complex, I move to using the "CASE" statement.
 
Regarding "Least Amount of Work" philosophy: It should still be alive and well. If it is not, you are working too hard and wasting your effort. Using L.A.W. methodology on the micro levels means you get more of those "micro" things done sooner and can thus turn in your project sooner.

Yes, it might APPEAR that you are working harder. But our mantra when I was with the U.S. Navy as a contractor was "Work smarter, not harder." When you can identify things to do and things to avoid doing (for efficiency's sake) then you are becoming a software engineer, the person who understands the fine art of the possible. Then you get more done and yet (when you have tossed in your smart-factor) you really aren't working any harder. (After all, it's not like you personally loaded a few extra Terabytes into your wheelbarrow to go fill another bit-bucket, right?) Your throughput has increased but at the end of the day, you sat at the same desk typing and maybe making a diagram or two, just like you did before you applied the smarts.

Here's the personal benefit: When your production goes up and your boss sees it, guess who gets first in line for the annual review and gets favorable ratings (and maybe a step-raise in pay). Hint: It ain't the slacker.
 
Related to KISS, in self-learning HTML, I had one of those "Duh, you are an idiot" Eureka moments. I was having extreme difficulties in getting elements positioned on a local LAN webpage. One day it occurred to me to temporarily colorize and add a border to an element so that it could be easily seen on the page and the effects of changing various element properties could also be easily observed. One of those techniques you only seem to learn through actually banging your head against the proverbial wall.
 
So one person will hear the politician lying and another person will hear the politician telling the truth.

i have trouble believing this. i know many people naive. they are terrible. no politician i listen to ever has told truth. probably because they make the world so complex that they dont know what to do anymore.
 
someone here post something funny and here is link


yesterday i saw something else that i found from looking at that article. i took snipping of it in windows 10. wow i did not know this was so bad with coders

articlepostlink.jpg
 

Users who are viewing this thread

Back
Top Bottom