Writing · 2026-04-10
Learning Python Formally When You Already Live in the Terminal
If you spend your days in bash and vim—writing shell scripts, managing servers over SSH, piping data through awk and sed and jq—you already think like a programmer. You understand control flow, data manipulation, process management, error handling. You do it every day. You just do it in a language that nobody puts on a certification.
That is the gap. Not a skills gap—a credentials gap. And closing it turns out to be straightforward, cheap, and surprisingly well-timed.
The Plan
Two steps. One free, one $69.
Step 1: Python Essentials 1 is a free, self-paced course from the Python Institute, hosted on edube.org. It covers fundamentals: data types, control flow, functions, data structures. The recommended pace is 42 hours over six weeks, but if you already understand loops, conditionals, and how data moves through a pipeline, you will move faster than that. The concepts are not new. The syntax is.
Step 2: PCEP-30-02 is the Certified Entry-Level Python Programmer exam from the Python Institute. Online, proctored, $69 USD. Pass mark is 70%. The certification is industry-recognized and serves as a stepping stone to more advanced credentials (PCAP, PCPP). The current exam version retires August 31, 2026—which creates a natural deadline and a reason to start now rather than later.
Total cost: $69. Total time: a few weeks of focused evening work. The course prepares you for the exam directly—no supplementary materials needed.
Why This Makes Sense for a Shell Person
Bash is powerful but narrow. It is the right tool for gluing processes together, for cron jobs, for quick file manipulation. It is the wrong tool for anything that needs data structures more complex than an array, error handling more nuanced than set -e, or logic that someone else will need to read six months from now.
Python fills exactly that gap. It is what you reach for when a shell script outgrows itself—when you need to parse JSON properly instead of hoping jq covers your edge case, when you need to talk to an API with authentication and retries, when you need to process a log file in a way that would take forty lines of awk but ten lines of Python.
If you already run infrastructure, you have encountered this boundary. Configuration management tools are written in Python. Monitoring integrations are written in Python. Cloud provider CLIs are written in Python. The Kubernetes client library is written in Python. At some point, reading and modifying Python stops being optional and becomes part of the job.
The transition from bash to Python is also shorter than most people expect. The mental model is similar: you are still processing data, still handling control flow, still thinking about inputs and outputs. Python just gives you better tools for it—real data structures, proper exception handling, a standard library that covers most of what you would otherwise shell out to external commands for.
Why Now
Three things converged.
First, the exam has a deadline. PCEP-30-02 retires at the end of August 2026. The replacement version will likely cost the same and test the same material, but there is no reason to wait for a moving target when the current one is well-documented and the prep course maps directly to it.
Second, Python’s position in the job market is not debatable. It is the most requested language in DevOps, data, automation, and ML job postings. A certification does not replace experience, but it answers the screening question that comes before anyone looks at your experience. Recruiters and ATS systems look for keywords. PCEP is a keyword.
Third, AI tooling has made Python more relevant, not less. The tools I use daily—Claude Code, whisper.cpp pipelines, MCP servers, model orchestration—are either written in Python or have Python as their primary integration language. Building on top of these systems, rather than just using them, requires Python fluency. A formal foundation makes that transition from user to builder concrete.
What Comes After
PCEP is entry-level by design. It validates that you understand the language. The next credential is PCAP (Certified Associate in Python Programming), which goes deeper—OOP, modules, file I/O, exception hierarchies. Beyond that, PCPP covers professional-level topics.
But the real value is not the certification chain. It is what Python unlocks in the work you are already doing. Writing proper automation instead of fragile shell scripts. Building tools instead of chaining commands. Contributing to projects in the language they are written in, rather than wrapping everything in bash.
For $69 and a few weeks of structured study, that is a reasonable trade.