- Problem
- A skill list is an assertion. A technical transition gets credible when coursework, credentials, maps, dashboards, and lab notes become checkable public proof.
- Role
- Learner, builder, documentation owner, proof curator
- Date
- 2026
- Tools
- ArcGIS Pro, ESRI tools, Linux, SQL, Python, HTML, CSS, Java, Cybersecurity coursework
GIS and Cybersecurity Skill Track
The technical transition, documented: GIS, ArcGIS, web mapping, cybersecurity fundamentals, network security, Linux, SQL, Python, and full-stack development — turned into proof, one cleared artifact at a time.
Claim: the skill claims on this site are checkable.
Receipt: 10 verified credentials — Google Cybersecurity track, Linux, SQL, networking — linked on the profile board, with the rest of the record held at Under Review until each one clears.
Status honesty: In Progress means in progress. Maps, dashboards, lab notes, and course artifacts publish as they clear review, not before. The track is graded on artifacts, because a skill list without them is just a list.
Receipts
Outcomes and lessons.
Outcomes
- Public track defined for cleared credentials, maps, dashboards, lab notes, and course artifacts.
- Keeps the next technical chapter visible without claiming every proof artifact is ready.
- Verified public evidence stays separated from private or still-under-review material.
Lessons
- A learning track needs visible artifacts, not only a skill list.
- Career-transition proof is stronger when each claim has a cleared source.
This track turns active learning into a public proof archive. It grows with confirmed coursework, ArcGIS work, screenshots, lab notes, maps, dashboards, and short writeups — each one added when it's cleared, and not a day sooner.