Stage 5 of 8 · 7 lessons · ~3 months

Proof without a CS degree

Build evidence a stranger can check: projects that solve problems from your old field, a first open source contribution, short write-ups and certificates used sensibly.

Start: Proof over credentials

Lessons· one lesson for each topic, in this order

Do this

List three problems from your old field that software or data could help with.
Write a three-line version one scope before building.
Finish and deploy or publish your first project with fake data.
Write a one-page case study for it.
Make one open source contribution or publish two short write-ups.
Only pay for a certificate if postings in your market ask for it.
Finish a second project that matches your target role.

Start with

BookFree
Automate the Boring Stuff with Python
Al Sweigart · Beginner
Free book on automating spreadsheets, files and reports: ideal for projects from your old job

Practise

First Contributions
A guided first pull request, so your first real contribution is not your first time using Git
Good First Issue
Beginner-friendly issues in active projects once you have done a practice pull request

Keep handy

Kaggle Datasets
Public datasets from many industries, often including the field you came from
Hashnode
A free developer blog for your write-ups and case studies

Also worth your time

Learn In PublicRead
The short essay behind learning in public, and why it keeps paying off

Before moving on: Two finished projects, at least one solving a problem from your old field, each with a one-page case study and a live link or report; plus one open source contribution or two public write-ups.

Tauseef's advice

Without a degree, proof carries your whole application, so treat it seriously. Two finished projects with real users or real data, a merged pull request and a few honest write-ups will say more than any list of courses.