A design principle encouraging developers to avoid unnecessary complexity in code, favouring straightforward solutions over clever ones.
Often cited alongside DRY as one of the foundational principles of clean code. The name is intentionally blunt: the "stupid" is directed at the temptation to over-engineer, not at the developer. Code that follows KISS tends to be easier to read, easier to test, and less likely to surprise the next person who has to work with it. The principle is often paired with a warning that clever code might look impressive but readable code is far more valuable to a team.
Often cited alongside DRY as one of the foundational principles of clean code. The name is intentionally blunt: the "stupid" is directed at the temptation to over-engineer, not at the developer. Code that follows KISS tends to be easier to read, easier to test, and less likely to surprise the next person who has to work with it. The principle is often paired with a warning that clever code might look impressive but readable code is far more valuable to a team.
