Mike Lopez (@MikeLopez) header
Mike Lopez (@MikeLopez) profile picture

Software engineer. Songwriter. Worship leader. Building software, writing songs, leading worship, and living it all for Jesus Christ, the One True King. Serving

Philippines
Joined April 2008
Photo by Mike Lopez (@MikeLopez)Photo by Mike Lopez (@MikeLopez)Photo by Mike Lopez (@MikeLopez)Photo by Mike Lopez (@MikeLopez)Photo by Mike Lopez (@MikeLopez)Photo by Mike Lopez (@MikeLopez)Photo by Mike Lopez (@MikeLopez)Photo by Mike Lopez (@MikeLopez)Photo by Mike Lopez (@MikeLopez)Photo by Mike Lopez (@MikeLopez)
PHP folks, how many bugs can you spot before this reaches production? 😅
1
16
If your WordPress plugin changes how it stores settings, test the upgrade with data from the old version. Run the upgrade twice and check that the second run leaves the data intact. The clean install is usually the easy part.
18
Tell people when their input changed your mind.
13
Use database constraints to protect important data rules.
13
Which Psalm do you return to most often?
17
My AI coding setup gives the implementation and review to different agents. The review gets the requirements and the diff. I want a fresh read of what the code does before the author’s explanation shapes it. What do you still check by hand before merging?
11
Revisit workload when someone repeatedly works late.
28
An AI-generated refactor can be smaller in lines and larger in risk. Before merging, list the behavior callers depend on. Which of those assumptions does the test suite actually check?
18
A useful bug report gives the next developer a starting point: the smallest input that fails, the expected result, and the result you actually got. What detail do you most often have to ask for?
14
A permission check belongs on the server even when the button is hidden. For a WordPress admin action, test the request as a user who cannot see that button. The UI is not the authorization boundary.
17
Before you add another WordPress performance plugin, check whether the slow page is slow only for logged-in users. If it is, measure the uncached request. On a membership site, that’s the request your paying customers actually wait for.
2
14
Discuss observable behavior instead of assigning personality labels.
13
A small, readable function saves time every time the next person has to understand it.
12
Automate repetitive tasks once the process is understood.
6
Identify the riskiest assumption before committing to a detailed plan.
5
A status update should make the next decision easier. A long list of activity doesn’t always do that.
1
12
Coach with questions when someone can discover the answer themselves.
12
One thing I like about open source: when the documentation leaves a question unanswered, you can read the implementation. Sometimes that settles it. Sometimes you discover why the docs were vague. 😅 What project taught you something by letting you look inside?
4
For a membership product, I'd include this in the payment test plan: Payment succeeds. Access doesn't. Can support trace the payment to the account and restore access safely? The happy path gets a demo. Recovery deserves one too.
1