LOCKEDIN / FORWARD-DEPLOYED ENGINEERING 101
Understand it.
Then build it.
You can be an experienced engineer and still be new to agents. Start with what each thing is and how it helps a person do useful work. Explore 48 original introductions across software, agents, cloud, security and delivery. Start here without a model key; each topic connects to deeper instruction and practice.
- 101UnderstandPlain language, visual walkthrough, vocabulary
- 102Build with guidanceOriginal lessons, examples and knowledge checks
- 103Practise and explainRunnable labs, failure cases and handover
- 01Orient
- 02Make one change
- 03Verify and hand over
An agentic coding tool
What is Claude Code?
Claude Code is a coding tool from Anthropic that can read a project, help explain it, propose edits and run development commands when permitted. Its terminal interface lets you work with it from a command line. Claude is the model family; Claude Code is a tool built around models for software work.
An FDE often enters an unfamiliar codebase. A coding agent can help you navigate and implement a change, but you still need to understand the code, inspect the diff and prove the behavior with tests.
CONNECT IT TO WHAT YOU KNOW
Start with something familiar.
A coding agent works alongside your editor and command-line tools. It can propose a sequence of engineering actions; you still inspect what changed and what the checks actually prove.
Claude Code helps develop an application. It is separate from a runtime agent that serves your customers. Keep their credentials, permissions and responsibilities separate.
Words worth knowing
- CLI
- Command-line interface: using text commands in a terminal.
- Repository
- The project's files and version history.
- Diff
- A view of what changed between two versions of the files.
- Test
- An executable check of the behavior the software should provide.
ONE EXAMPLE / FICTIONAL CASE
Watch the work take shape.
A ticket-triage project routes a request incorrectly. Ask the coding tool to explain the routing function, reproduce the failure and propose a small correction. Review the actual change before accepting it.
- 01Orient
- 02Make one change
- 03Verify and hand over
Orient
Open the repository, read the project instructions and identify how to run its tests. A repository is the project's files and recorded version history.
An explanation of the existing behaviorFROM RECOGNITION TO REASONING
Write a bounded request to a coding assistant.
- 01
Ask it to explain the existing behavior before editing.
- 02
Name one allowed change and one behavior that must remain unchanged.
- 03
Specify the test and diff evidence you will inspect.
A task request that another engineer can review.
Compare your reasoning when you are ready
A useful request has a stopping point and observable acceptance evidence. 'Improve everything' gives neither the agent nor the reviewer a clear boundary.
Keep notes in your own working copy. Moving through these cards does not record completion.
TURN THE IDEA INTO USEFUL WORK
You can now go deeper.
Use a coding agent to help with engineering work. Understanding, permission and verification remain part of your job.
Academy lessons use your existing training access. Free guides stay open.
Learn with the original creators
Use the introductory workflow lessons to see a coding assistant in context, then reproduce the method with our starter project.