Browse the library

Filter by series or search — every piece is written to be useful in a corridor conversation, not to chase trends.

Topics

Courses

Showing 1–30 of 30 articles

Per page

Writing Decent PHP
Chapter 2 guided practice
This lesson is intentionally hands-on. Complete all three exercises in order. Each one targets a different cluster of naming smells from this chapter. Don't change the behaviour — only the names, constants, file lay...
Read article
Writing Decent PHP
A small naming cleanup walkthrough
Putting the chapter into practice on one small file This chapter has covered a lot of ground: naming by intent, units in variables, verb prefixes on booleans and functions, collection names, class names, file layout, ...
Read article
Writing Decent PHP
Reviewing names in context
Names are cheapest to fix during review Once a name lands on main, it starts propagating. It appears in new callers, new tests, new documentation, and new conversations. Renaming later is always possible (lesson 2.12)...
Read article
Writing Decent PHP
Renaming code safely
A rename is a refactor with its own risk profile Lesson 2.11 was about why to rename when names drift. This lesson is about how to do it without breaking anything. Renaming code sounds like the safest refactor there i...
Read article
Writing Decent PHP
When old names hide new behaviour
Names become lies the moment behaviour drifts Every name you write is a promise. validateUser() promises to validate a user. getOrder() promises to fetch an order. sendEmail() promises to send an email. Code changes a...
Read article
Writing Decent PHP
Abbreviations, acronyms, and team context
Abbreviate only when the team genuinely says it out loud Abbreviations save typing, which is a tiny gain. Bad abbreviations cost reading, which is a much larger loss. The trade only works when the short form is so com...
Read article
Writing Decent PHP
Avoiding vague utility language
"Utility" usually means "I have not named this yet" Words like helper, util, common, misc, manage, process, handle, and do show up when someone could not think of a better name and shipped the plac...
Read article
Writing Decent PHP
Using domain language consistently
Pick one word per concept, then use it everywhere If your domain has a "customer", do not call them a customer in the database, a user in the controller, an account in the email service, and a member in the ...
Read article
Writing Decent PHP
File and folder naming
File and folder names are the table of contents for your codebase Before any developer reads a line of your code, they read the file tree. Folder and file names should answer two questions at a glance: "where doe...
Read article
Writing Decent PHP
Better class names
A class name should describe a single concept A class name is a noun. The reader should be able to say "an instance of this is a ___" and have a clear answer. When a class is named Manager, Helper, Util, or ...
Read article
Writing Decent PHP
Naming collections and groups
A collection name should tell you "what's in it" and "what's already been done to it" Collections (arrays, iterables, lists, maps) carry two pieces of information you usually want at a glance: what...
Read article
Writing Decent PHP
Better function names
A function name should describe the action Variable names answer "what is this?". Function names answer "what does this do?". That means a function name almost always starts with a verb, and the ve...
Read article
Writing Decent PHP
Better boolean names
A boolean name should read like a yes/no question If a variable holds true or false, the name should make that obvious. The reader should be able to look at the name alone and ask: "is this thing X? yes or no.&qu...
Read article
Writing Decent PHP
Better variable names
A name should answer "what unit is this in?" A variable called $timeout raises an immediate question: seconds? milliseconds? minutes? A variable called $weight is the same: kilograms? pounds? grams? A variab...
Read article
Writing Decent PHP
Naming by intent, not by type
A name should tell the reader what the value means in the business, not what shape it has in PHP. $arr, $data, $obj, and $item describe the type. $pendingApprovals, $signupInput, and $exp...
Read article
Writing Decent PHP
Chapter 1 guided practice
This lesson is intentionally hands-on. Complete all three sandbox exercises below in order. Exercise 1: flatten nested logic Refactor this function to use early returns so the happy path is obvious. <?php function ...
Read article
Writing Decent PHP
Build your Chapter 1 action plan
Turn Chapter 1 into an action plan You have now covered naming, clarity, code rot, verification, and trade-offs. This lesson is about turning those ideas into one practical plan for your real codebase. Step 1: pick on...
Read article
Writing Decent PHP
What each chapter is trying to achieve
How this course is structured This course is designed as a progression, not a random list of topics. Each chapter gives you one layer of practical judgement, so by the end you can write PHP that is readable, maintaina...
Read article
Writing Decent PHP
It depends: performance, cost, and context
"It depends" is often the right answer In engineering, "it depends" is not a dodge. It is usually the most honest answer when you are balancing readability, maintainability, performance, and delive...
Read article
Writing Decent PHP
Verification checks before you apply this in the wild
Readable code reduces risk, but it does not remove risk. Before merging or deploying, you still need explicit checks that prove behaviour is safe. Before: vague confidence Teams often approve changes with comments lik...
Read article
Writing Decent PHP
Preventing code rot with practical team habits
Code rot is mostly prevented through habits, not heroics. The five habits to keep repeating are: train, identify, test, document, and stay calm. 1) Train: align the team ...
Read article
Writing Decent PHP
Code rot consequences: bugs, slowdown, and morale
Code rot is not just an aesthetic problem. It affects reliability, delivery speed, and team confidence. flowchart TD unclear[Unclear or duplicated code] --> hesitat...
Read article
Writing Decent PHP
Code rot: small smells and what they look like
Code rot usually starts small Code rot usually does not arrive in one dramatic commit. It grows from small shortcuts that never get cleaned up. mindmap root((Code smells)) Unused or unreachable Unreadable conditionals...
Read article
Writing Decent PHP
Rules and invariants you can rely on
An invariant is a rule that must always be true. If those rules are vague or spread around the codebase, bugs slip through and reviews become guesswork. Before <?php function up...
Read article
Writing Decent PHP
How future you experiences code
Constraints change what "good" looks like Clean code is not one fixed shape. What is "best" depends on context: deadlines, team size, risk, and how often the code will change. We have already allud...
Read article
Writing Decent PHP
Hidden dependencies and local reasoning
Hidden dependencies break local reasoning Local reasoning means a developer can read one function and understand what it does. That falls apart when behaviour depends on globals, environment values, and helper functio...
Read article
Writing Decent PHP
Start small, then scale the refactor
What "start small" actually means Starting small does not mean avoiding real refactors. It means proving your approach on a tiny, low-risk slice first. Pick a small function where behaviour is obvious, apply...
Read article
Writing Decent PHP
Keep it as simple as you can for as long as you can
Over-engineering often starts with a reasonable-sounding sentence: "We might need this in future." Most of the time, that future never arrives, and your team inherits extra complexity for no current benefit....
Read article
Writing Decent PHP
Formatting and indentation for readability
Formatting is not cosmetic. Formatting is not cosmetic. Good indentation shows structure, makes bugs easier to spot, and lowers review effort. Before This version has inconsistent spacing and cramped structure, so the...
Read article
Writing Decent PHP
Working code is not enough
Why this course exists Most PHP courses stop at "you can build it." This course continues to "you can maintain it, change it safely, and hand it over without drama." Course standard: "It works...
Read article

If a piece lands and you want the same honesty on your own stack — book a free systems review. We'll say when build isn't the answer.

Book a free systems review Start a project

Browse the library

Topics

Courses

Chapter 2 guided practice

A small naming cleanup walkthrough

Reviewing names in context

Renaming code safely

When old names hide new behaviour

Abbreviations, acronyms, and team context

Avoiding vague utility language

Using domain language consistently

File and folder naming

Better class names

Naming collections and groups

Better function names

Better boolean names

Better variable names

Naming by intent, not by type

Chapter 1 guided practice

Build your Chapter 1 action plan

What each chapter is trying to achieve

It depends: performance, cost, and context

Verification checks before you apply this in the wild

Preventing code rot with practical team habits

Code rot consequences: bugs, slowdown, and morale

Code rot: small smells and what they look like

Rules and invariants you can rely on

How future you experiences code

Hidden dependencies and local reasoning

Start small, then scale the refactor

Keep it as simple as you can for as long as you can

Formatting and indentation for readability

Working code is not enough