Module 3 · Files, tools and your own data Lesson 9 of 15
A workspace that runs, hosts and deploys what it writes — Replit Agent's own feature
The agent is not producing code for you to run elsewhere. It has the editor, the runtime, a database and hosting, so "make it work" ends with a live URL. Every iteration runs against a real application.
The concept
Because the gap for a fresher is not usually writing code — it is finishing something and putting it live. A hosted workspace removes every step where a beginner gets stuck: environments, dependencies, deployment, a place for the database.
Plan before you prompt: the data, the one screen that matters, and an explicit list of what to leave out. Approve the data model first. Then build one screen at a time and look at the result after every step. Keep a note of each request you made, because that log is what you will describe in an interview.
Here is the shape of it, in the form you will actually use:
WORKING ORDER THAT ACTUALLY FINISHES
1. DATA list the fields before any screen is built.
"students(name, roll, class), attendance(date, student, present)"
2. SCHEMA ask for the tables and the unique key. Approve them.
3. ONE SCREEN the screen that has the whole value in it. Nothing else.
4. RUN IT look at the result in the preview before the next message.
5. DEPLOY put it live, then open it on your own phone.
6. ONE FIX use it for three days, then fix the first thing that annoys you.
What NOT to do: ask for login, an admin panel, charts, exports and email
in the first message. That produces a broken application and no
understanding of what is in it.Common mistakes
The mistake is asking for the whole application at once and then not reading the code. You end up unable to change anything, which is the opposite of what a portfolio project is for.
Worked example
A working attendance form with real data in it, reachable on a phone, built and deployed in an evening.
Your practice task
Build one genuinely small tool you will use this week, deploy it, and use it on your phone for three days. Then fix the first thing that annoys you.
Do this before moving on. Reading a solution teaches the shape of it; typing it teaches you.
Key takeaway
Because the gap for a fresher is not usually writing code — it is finishing something and putting it live.
Keep your place in this course
A free account saves which lessons you have finished and unlocks the certificate. The lesson itself stays free to read.
Create free account or sign inCourse complete
You finished every lesson.
Your certificate is ready, and the projects you built are the proof to attach to an application.
Almost there
15 lessons left of 15
Finish every lesson to unlock the certificate. Each one ends in a practice task — do them and the final project brief writes itself.