Being clear about gaps is part of how he works.
Not yet: RAG and vector databases
Learning now; not yet built in a project.
Related strength: Claude Certified Architect – Foundations deepened his understanding of how RAG and MCP work behind the scenes.
Not yet: fine-tuning
No fine-tuning or model training yet. He plans to fine-tune Laya, a small decision-making model, for a personal project.
Related strength: He has run pre-trained models for inference, such as ONNX selfie segmentation in a video pipeline.
MCP: daily user, practice builder
Uses MCP servers daily (Azure DevOps, GitHub) but has built them only for practice, not production.
Related strength: He is researching when MCP is worth its token cost versus a ready script or CLI.
Doesn't use Figma
He prototypes with AI design tools instead: Claude Design, Stitch, and his favourite, Open Design.
Related strength: The AF Engage hackathon prototype was a UX-led journey.
Not a syntax memoriser
If a role needs exact syntax from memory, he is not the right fit. His strength is the approach, not recall.
Related strength: Once he understands a flow, he pinpoints bugs fast, even in stacks he is less fluent in.
No PM or PO certification yet
He has done product-owner and project-manager work on most of his client projects, without the formal title or certificate.
Related strength: He wants one and is deciding which would add the most value.
Not a frontend specialist
He handles frontend work, but in React he has done bug fixes in existing code rather than building whole screens.
Related strength: Angular and AngularJS are his stronger frontend tools.
Hasn't owned a budget
He feeds estimates into budgets but has not owned or managed one.
Related strength: He gives effort estimates for budgeting and client-approved scope changes.
Judgement over frameworks
He prioritises with his own judgement and understanding of the project rather than RICE or MoSCoW, and wants to learn the formal methods.
Related strength: He owned backlogs and set priorities on six projects.
No infrastructure-as-code
He designs AWS infrastructure as a developer, not a DevOps specialist, and has not used Terraform or CloudFormation.
Related strength: He has deployed with load balancing and Auto Scaling on EC2 and Lightsail.