What File Access Unlocks¶
From Fiction to Reality¶
Remember your Challenge 1 prototype? It looked real, but you likely hit some friction points. The data may have been hardcoded text you typed into the prompt. Your team couldn't collaborate together on it. It was a great prototype, but it wasn't connected to the real world.
Now that you're working in a real development environment, here's what becomes possible that wasn't before.
Live Data¶
There are free services on the internet that publish real federal contracting data. USAspending.gov tracks every federal contract, grant, and loan, over $6.75 trillion annually. SAM.gov holds registration records for 2.68 million entities and 167,000+ exclusion records. Your project can use this data to show real vendor profiles instead of hardcoded samples.
That means your Federal Vendor Intelligence Tool can show Lockheed Martin's actual $49.9 billion in federal awards, their real top agencies (DoD, NASA, Commerce), their actual NAICS codes (Aircraft Manufacturing, Guided Missiles), and their real business type and UEI, not data you made up in a prompt. You will connect to these data sources in Challenge 2.
Real Complexity¶
In chat, you built one thing at a time. In a real project, your app can span dozens or even thousands of files: a home page, a dashboard page, a detail page, all with navigation between them. Your AI coding assistant can manage that complexity for you, adding features, connecting pages, and keeping everything organized. What comes out is a real application with real depth, not a single output.
User Accounts and Stored Data¶
Want people to be able to save their preferences? Track their progress? Log in and see personalized content? When you're working with real files, you can build features that remember things about the people using your app.
Work That Persists¶
Come back tomorrow and pick up where you left off. Your AI coding assistant can read what's already there and continue building. No need to re-explain what you've already done.
Team Collaboration¶
Your whole team can contribute to the same project, like editing a shared Google Doc. Two people can work in the same file just fine, as long as they aren't trying to write the same sentence in the same section at the same time. If they do, their changes can collide and overwrite each other.
The trick is clear swim lanes: one person works on the dashboard while another builds the detail page, just like one person writes Section A of a document while a coworker writes Section B. When the work is divided cleanly, everything merges together smoothly.
If your team is just getting started and doesn't have clear swim lanes yet, mob first: everyone around one screen, one person driving, building the foundation together. Once the project has distinct sections to work on, your team can divide and conquer. Think of mobbing as writing the outline together before splitting up to draft individual sections.
Imagine the Upgrade
Mob Session | ~3 minutes total | Gather around one screen. One person opens a notes app: Notes on Mac, Notepad on Windows (not the AI coding assistant).
Think back to your Federal Vendor Intelligence Tool from Challenge 1. As a team, come up with two things you wish your tool could do that were not possible in chat. Write them as user stories using the format you learned in Lesson 1.
For example:
As a contracting officer researching Lockheed Martin,
I want the tool to show their **real total federal award amount** from USAspending.gov,
So that the profile reflects actual contracting data, not hardcoded samples.
Write your two stories in your notes app. Hold onto them. You will use these as your first real tasks in Challenge 2.
Discuss: Which of the two would have the biggest impact on someone doing vendor due diligence?
Key Insight
Moving from chat to a real development environment is what turns a clever prototype into real software. Live data instead of made-up text. Real complexity instead of a single output. Persistent work you can build on over time. Team collaboration with clear swim lanes instead of one person prompting. The prompting skills you learned in Lesson 1 are the same; what changes is what becomes possible.