MugUp logoMugUp
HomeBrowsePricingAboutBlogContact
LoginSign Up
© 2026 MugUp. All rights reserved.
HomeAboutDeck LibraryBlogChangelogContactFeature RequestsDeck Requests
Terms of ServicePrivacy PolicyCookie Policy
  1. Browse decks
  2. Clean Code & Software Engineering Principles
Public deck

Clean Code & Software Engineering Principles

The language-agnostic foundation deck for engineers: SOLID, design heuristics, naming, functions, code smells and refactoring moves — the vocabulary that code review assumes you already have.

Engineering
AShared by Alex Chen
1PlaySign in to clone

You’re reading a free preview. Sign up to see every topic and question — and to play this deck as games.

See the whole deck

Suggested order

Arrows point from what to learn first. Topics side by side can be studied in any order — and cloning the deck brings this order with it.

Topics

Open a topic to read through its content, then play just that topic.

SOLID Principles, One by One
The five principles collected under the SOLID acronym, stated precisely — including the two that are most often misquoted.
MCQ: 10
Fill-in: 8
Flashcards: 14
Pair match: 10
42 total questions
DRY, KISS, YAGNI and Design Heuristics
The design maxims every reviewer quotes — what each actually claims, and the ways each is routinely misapplied.
MCQ: 10
Fill-in: 8
Flashcards: 13
Pair match: 10
41 total questions
Naming: Variables, Functions, Types and Files
Why names carry most of the readability budget, and the specific habits that make them earn it.
MCQ: 10
Fill-in: 8
Flashcards: 13
Pair match: 10
Locked · 41 questions inside
Functions: Size, Arity and Side Effects
What makes a function easy to call, easy to test and safe to reason about — and where the advice to extract stops paying.
MCQ: 10
Fill-in: 8
Flashcards: 13
Pair match: 10
Locked · 41 questions inside
Code Smells and Their Names
The catalogue of named smells — so you can say what is wrong in review instead of gesturing at it.
MCQ: 10
Fill-in: 8
Flashcards: 14
Pair match: 10
Locked · 42 questions inside
Refactoring Moves and When to Reach for Each
Named refactorings, the conditions that call for them, and the discipline that makes them safe.
MCQ: 10
Fill-in: 8
Flashcards: 14
Pair match: 10
Locked · 42 questions inside
Comments and Documentation
What to write, what to delete, and why a comment is usually the second-best fix for unclear code.
MCQ: 10
Fill-in: 8
Flashcards: 14
Pair match: 10
Locked · 42 questions inside
Testing: The Pyramid, Test Doubles and Good Tests
How a test suite should be shaped, what the five test doubles actually mean, and what separates a test that helps from one that gets in the way.
MCQ: 10
Fill-in: 8
Flashcards: 14
Pair match: 10
Locked · 42 questions inside
Version Control Hygiene and Code Review
Commits and branches that keep history usable, and reviews that catch what only a human can catch.
MCQ: 10
Fill-in: 8
Flashcards: 14
Pair match: 10
Locked · 42 questions inside
7 more topics in this deck

Create a free account to open every topic — and play the whole deck without copying it.

Sign up freeLog in