Technical construction
Custom PHP and PDO systems, MySQL databases, CMS architecture, account systems, comments, games, tools, and long-form project planning.
About Donald
I am interested in the space between what should work and what actually happens.
That question has followed me through programming, business, parenting, education, relationships, financial pressure, housing instability, content creation, and years of trying to turn useful work into a sustainable life.
BuilderResearcherFatherLearnerSystems thinker
Deltona, Florida
Still building.
01
The public position
I do not need to claim expertise in everything to show my work honestly.
DonaldFaulknor.com establishes authority through transparent experience, documented research, technical demonstrations, clearly separated opinion, and honest limitations. Every substantial page should make it clear whether I am writing as a builder, parent, student, user of a system, researcher, observer, or person directly affected.
The goal is not to make my life look impressive. It is to make the useful parts of what I have learned available, organized, and testable.
What I bring to the platform
A range that makes more sense when you see the connections.
Lived-system analysis
Firsthand encounters with housing, assistance programs, financial pressure, family systems, entrepreneurship, and the distance between policy rules and actual survival.
Human questions
Relationships, communication, breakups, boundaries, fatherhood, identity, rebuilding, and the emotional reality hidden beneath simple advice.
Designed alternatives
Tools, frameworks, platforms, and better-system blueprints that move beyond criticism toward mechanisms that could be tested.
What readers can expect
Specific without pretending certainty. Personal without becoming a diary. Ambitious without confusing imagination for proof.
The purpose of these standards is not to make every page sound formal. It is to help readers understand what they are reading, where it came from, and how much confidence it deserves.
Know what kind of claim you are reading.
Facts, personal experience, interpretation, opinion, hypotheses, and proposals will be clearly distinguished.
Personal material should serve a public purpose.
Experience is included when it improves accuracy, empathy, context, or usefulness—not simply for exposure.
See the system, not only the conclusion.
Technical work and future proposals will explain their mechanisms, assumptions, tradeoffs, and limitations.
The unfinished parts remain visible.
Failures, revisions, uncertainty, and changing conclusions are part of the record rather than defects to hide.
Current chapter
Building a platform broad enough to hold the real range of my work.
The immediate task is to turn years of scattered writing, software, project plans, hard-earned lessons, unresolved questions, and future proposals into a useful public archive.