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)
AI wrote the code. Great. Who checked it? I built BORK: 8 AI skills for GitHub issues, draft PRs, reviews, fixes, and E2E/browser checks. Because “looks good to me” needs evidence. Especially from a robot. github.com/easterncoder/bork…
27
Spot the PHP bug. $enabled = (bool) ($settings['enabled'] ?? true); The settings API sends "false" as a string. What value does $enabled get, and where would you fix it?
48
Keep local development setup documented and repeatable.
11
What’s one thing you wish every handoff included?
6
If an agent keeps fixing the wrong thing, give it one real input, the output you got, and the output you expected. Then ask it to explain the gap before editing. That example often does more work than another paragraph of instructions.
11
Define escalation triggers before a project gets into trouble.
10
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.
21
Tell people when their input changed your mind.
15
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
16
Discuss observable behavior instead of assigning personality labels.
13
PHP folks, how many bugs can you spot before this reaches production? 😅
1
19
A small, readable function saves time every time the next person has to understand it.
12