Learn the foundations. Build useful software.
Deliver it where the work happens.
A hands-on path from your first Python script to integrations, AI evaluation, and customer delivery. Start small, test the failures, and leave work someone else can operate.
Begin with the skills you can demonstrate today. Build the next useful piece from there.
Learn Python, JSON, SQL, and HTTP through one real-data exercise. Then explore retrieval, tests, and handover.
Bring your software, data, ML, solutions, or consulting experience. Focus on the delivery responsibility you want to strengthen.
Demonstrate independent evaluation, authenticated authority, recovery, and the economics of operating a system.
git clone https://github.com/AdilShamim8/FDE-Field-Guide.git
cd FDE-Field-Guide
python3 learning-paths/foundations/code/complaint_pipeline.pyAlready have the checkout? Run the last command from its root. Expect five retained records dated 2026-10-09. This first exercise uses only the standard library.
Follow the example, attempt your own version, then explain what happens when it fails.
Find your terminal, create an environment, and run a script.
Read JSON, write a function, and count actual records.
Store facts, query rows, and replay without duplicates.
Send requests and understand success, rejection, and conflict.
Inspect evidence and explain when a model would help.
Test a failure and leave instructions someone can follow.
From integration fundamentals to deployment decisions. Pick a gap and apply what you learn.
14 topic sections
Understand what an FDE does and where the role fits.
Programming, discovery, communication, and prioritization.
APIs, data pipelines, infrastructure, and security.
Find the problem, define the scope, and manage expectations.
Retrieval, tool use, evaluation, and model-system reliability.
Release readiness, rollout, and operational ownership.
Design within constraints and explain your trade-offs.
Debug systems and practice failure containment and recovery.
Investigate source-backed findings and review evidence limits.
Interpret dated observations, role requirements, and compensation.
Choose a foundation, background route, or expert practicum.
Work through coding, design, and customer scenarios.
Select a project and present evidence of what you built.
Find tools, reading, and communities for your next question.
No topics match. Try a broader term or view all topics.
Trace where the data came from, read the implementation, and understand what a passing check proves.
The foundation exercise uses five actual complaint metadata records to teach counting, SQL, and repeat imports.
Use the ETISE ticket API to practice request validation, replay, policy retrieval, and routing to human review.
Return to a resource when it helps you make a decision, debug a failure, or explain a result.
Start with one command. Keep one result. Take the next small step.