D. James Poer
Rigby: feed, pause or dismiss
Pardon the dust.
I’m D. James Poer, a Senior UX Engineer and Front-End Architect. I build Angular and TypeScript interfaces for enterprise applications, connecting UX research, design engineering and accessibility work grounded in WCAG and Section 508. About my approach · Explore the engineering evidence · Explore the accessibility evidence
You're standing in the middle of a working construction site. On purpose.
Most portfolios show you the finished house after the tools, sawdust, mistakes, experiments, and bad ideas have been swept away.
I'm doing the opposite.
djamespoer.com is being designed and built in public. The unfinished pieces are part of the portfolio: UX decisions, accessibility work, Angular architecture, experiments, failures, fixes, testing, AI-assisted development—and the occasional spectacularly bad idea that gets replaced by a better one.
Some rooms are finished. Some still have studs showing. Some may change while you're standing in them.
That's the point. You're not just looking at what I built. You're watching how I build.
Executive Scrum Brief —
Recently shipped
The Blognostisphere published “Software Development Is Never Done — Just Done Enough for Now,” preserving the approved title, subtitle and complete manuscript. Working links connect the argument to Creative Town, Thingamajob and Shady White Van, making the article another entry point into the portfolio’s project evidence.
Article discovery now follows publication dates across the menu, index and related-article lists. Existing content bindings use stable slugs so reordering cannot attach the wrong manuscript to an article. This morning’s follow-up also added the new article to Rigby’s existing cookie trail without changing its prose or telemetry.
Validated / learned
The article release passed focused discoverability and component tests, a production build and live desktop and mobile checks. Verification covered all 139 approved content blocks, navigation order, internal links, metadata and sitemap inclusion, with no overflow, page errors or violations in the scoped automated accessibility rules. Keyboard navigation and the article heading’s presence in the accessibility tree were checked; a manual spoken-screen-reader session and a new performance benchmark were not claimed.
The cookie-trail addition passed six focused tests and a build, then production HTTP read-back confirmed the new cookie marker in the rendered article. That follow-up did not repeat browser interaction acceptance. Existing nonfatal stylesheet warnings remain.
Current focus
The new article and its cookie follow-up are released, and the publication story is closed. The résumé selector, maintained long-form résumé and paired Thingamajob telemetry continuation remain review work in the latest inspected record. There is no new evidence that those local changes have reached production.
Next
Review and integrate the accepted résumé experience through the existing release path, and assess the frontend and backend telemetry patches together before release. Preserve the distinction between implemented event collection and verified reporting outcomes, and carry the maintained career evidence into downstream surfaces with its scope and provenance intact.
Buildometer
How far has this project come?
Explore project progress, shipping and quality.
View the full dashboard Known-scope estimate · observedEstimated project complete
38.5%
152 / 395 known story points shipped
Production deployments
Deployment history loads when this section is in view.