Certifications and learning

No fake badges. Only real credentials belong here.

This page keeps the portfolio honest. I have chosen not to fill it with placeholder certificates. When certifications are added, they should be real, relevant, and verifiable.

TrustLearningVerification
Snapshot

A verification-first approach

Trust is stronger when a portfolio leaves empty space rather than filling it with claims that cannot be verified.

  • No fake badges or invented credentials
  • Project work remains the current proof of skill
  • Future certifications will be added only when earned
00Fake badges
05Project proofs
01Trust rule
Context

Current status

At the moment, this page is intentionally conservative: it reflects learning direction, not made-up achievements.

  • Real credentials only
  • Verification links when available
  • Project work still leads the story
Current position

No certifications are listed yet because I only want real ones on the site.

That choice matches the rest of the portfolio. I would rather show projects, repositories, live work, and clear explanations than fill the page with decoration that does not represent earned progress.

What belongs here later

Certifications that strengthen this profile when earned.

  • Java or backend development credentials
  • Python or automation-related credentials
  • Database and data-handling certifications
  • Deployment, cloud, or hosting fundamentals
  • API testing, documentation, or software quality topics
Rule 01

Only add credentials that are easy to verify

When a certification is eventually added, it should include the issuing body, date, and verification link when available.

Rule 02

Relevance matters more than quantity

A small number of strong, relevant certifications is better than collecting unrelated badges just to fill a page.

Rule 03

Project work still matters most

Even after certifications are added, the portfolio should still be grounded in actual software work and public proof.

Opportunities

Looking for a full stack developer with strong backend project depth and honest presentation?

I am open to full-time, internship, and part-time opportunities where Java, Python, full stack delivery, backend systems, or data-backed software work can create value.