![]() ![]() Simpler, cleaner code (structure, database, or architecture) is easier to maintain, less demotivating to work on, or less painful to handover. It gets the job done (together with SMART Goals). He not only gave you the authority but also the responsibility In terms of application to Developer Experience, Johnson mentions that you should Reduce reports and other paperwork to a minimum (use KISS for your agile events), and in terms of team culture, he said let managers run their programs with a minimum of interference. You will thank yourself for solutions aiming at simplicity. ![]() Don't make your code do four things at once (at the same time). ![]() If you are designing architecture, break it into parts (from monoliths to microservices) and refactor (a lot!). If you apply the KISS principle to developer work, you should split your hard problems into smaller ones and then solve them with simple solutions. The idea behind KISS is to get results cheaper sooner and better through the application of common sense to tough problems. The phrase originally comes from the Lockheed designer team and their head engineer Kelly Johnson (later founder of the Skunk Works). Simple things are more accessible, usually easier to use, and have a flatter learning curve. Some designers use KISS as their central design goal. Broadly, it tells you that things are better when they are simpler. KISS is a principle standing for Keep It Simple, Stupid (sometimes written as Keep it stupid simple or Keep it simple and straightforward). However, achieving smart simplicity is hard on all fronts. KISS is a design principle reminding you to stop overcomplicating work. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |