Two kinds of proof — public portfolio work and internal operations

It’s around 9 this morning on Day 008. I brainstormed late last night, fell asleep, woke up and brainstormed some more. Now it’s time to stop expanding the plan and start wrapping up real work.

I also want to be clearer about the two kinds of work I’m building.

Public Portfolio Work

This is work people can see and use: client websites, applications running in production, and products I ship. PrintFetti belongs here. Before I call it complete, it needs the mobile-responsive pass, final QA, a public walkthrough and a proper project case study.

For the walkthrough, I want to test an AI-assisted process without letting AI invent the product. First, inventory every real page, important state and user role. Then capture clean desktop and mobile screenshots. Give the screenshots and short purpose notes to AI so it can draft the explanation from each perspective—what the customer sees, what the shop owner or admin sees, what action each person takes and what should happen next. I still need to walk every path myself, correct the draft and remove anything private before publishing it.

Internal Operations Work

This is the private software that helps me run AlwaysCodedFresh but is never presented to a client as their product. The Lead System is the main example. It deserves an internal walkthrough because private tooling is still real engineering, even when it is not public portfolio material.

The Lead System needs to send emails, generate SMS messages that are easy to copy and paste, work well on mobile and run in production at clients.alwayscodedfresh.com. Its walkthrough can use the same screenshot-and-journey process, but it should document the operator workflow, debugging and failure states while keeping real lead data private.

Today’s work, with the weekend as the deadline

• Finish the PrintFetti mobile pass and QA, then produce the public walkthrough.
• Get the Lead System’s email, SMS drafting, mobile interface and production deployment working, then write its internal walkthrough.
• Put remote desktop access on my main machine so I can run leads and debug while away, and finish a real phone-coding setup.
• Build a resume aimed at Applied AI / AI Application Engineer work and start applying.

The job search is part of the build plan, not a retreat from it. Ideally I land an AI role within a month, but I’m applying more broadly to tech, part-time and practical income-bridge jobs too—including work I can do remotely or during quiet hours. Keeping rent, business costs and personal expenses covered gives me room to build the portfolio and deepen my AI knowledge over the next few months.

Today’s goal is to get as much of this finished as possible. The hard deadline is the end of the weekend.