MIVA STUDY PACK — Building With AI: Full-Stack & AI Integration (English) Downloaded 2026-09-29. Free to pass on. Building With AI: Full-Stack & AI Integration — Lesson 1: The Work AI Cannot Do For You 8 minutes read AI tools now write code faster than any junior developer. That has not removed the job — it has moved it. The person who only types HTML is competing with a free tool. The person who can decide what to build, wire it to real data, test it and fix it when it breaks is worth more than before. WHAT GOT CHEAP, WHAT GOT VALUABLE - Cheap now: boilerplate pages, styling a design, simple forms, standard CRUD screens. - Valuable now: turning a messy business request into a clear specification. - Valuable now: connecting systems — APIs, databases, payments, messaging. - Valuable now: reading AI-written code and spotting the bug it confidently introduced. - Valuable now: shipping, monitoring and repairing something real users depend on. THE SHAPE OF THIS COURSE Eight lessons. You will learn to describe work precisely, build interfaces with React, move data through APIs, store it in a database, direct AI tools so they produce usable code, review that code honestly, test and debug, and ship a small portfolio project an employer can open. [You do not need a degree] You need a phone or laptop, patience and one finished project that works. Employers hiring for AI-era roles ask to see something running far more often than they ask for a certificate. PRACTICE QUESTIONS 1. Which skill has become MORE valuable as AI coding tools improved? A) Typing HTML tags quickly by hand B) Judging whether generated code is correct and safe C) Memorising CSS colour names D) Copying designs pixel by pixel Answer: B — Generation is cheap; judgement is not. Reviewing output is the core of the new job. 2. What do employers in AI-era roles most often ask to see? A) A long list of courses B) A handwritten CV C) A small project that actually runs D) A university transcript Answer: C — Working software is the strongest evidence you can carry into an interview. ---------------------------------------- Building With AI: Full-Stack & AI Integration — Lesson 2: Turning a Request Into a Specification 9 minutes read A shop owner says: 'I want an app for my customers.' That sentence cannot be built — by you or by AI. The first professional skill is turning it into something buildable, and this is exactly the step AI cannot do without you, because the answers live in the owner's head. FIVE QUESTIONS THAT MAKE WORK BUILDABLE - Who uses it, and on what device? (A Tecno phone on cellular data is not a laptop on fibre.) - What must it do on day one? Name three actions, no more. - What data goes in and what comes out? Name the fields. - What must never happen? (Two people buying the last item; a customer seeing another's number.) - How will we know it worked? One measurable sentence. WRITE IT DOWN BEFORE YOU TYPE CODE A specification can be half a page. 'Customers browse products, add to a cart and send the order by WhatsApp. Products have name, price in GHS, photo and stock count. Orders record the phone number and the items. Nobody except the owner sees orders.' That paragraph is enough to direct both yourself and an AI tool. [Vague in, vague out] AI assistants never say 'I don't understand your request'. They guess — plausibly and confidently. A weak specification produces code that looks finished and solves the wrong problem. PRACTICE QUESTIONS 1. Why is a written specification especially important when using AI tools? A) AI refuses to work without documents B) AI fills gaps with confident guesses instead of asking C) It makes the code run faster D) It is required by law Answer: B — The tool always produces something. Your specification decides whether it is the right something. 2. Which item belongs in a first-day specification? A) Every feature you might ever want B) The three actions the app must support and the data behind them C) The company logo colours only D) A five-year roadmap Answer: B — Small, named, testable scope is what gets shipped. ---------------------------------------- Building With AI: Full-Stack & AI Integration — Lesson 3: React: Components, State and the Screen 10 minutes read React is the tool most teams use to build screens today. You do not need to memorise it — AI will write much of it — but you must be able to read it, change it and know when it is wrong. Three ideas carry most of the work. 1. A COMPONENT IS A REUSABLE PIECE OF SCREEN A ProductCard shows one product. A ProductList repeats it for every product. If you find yourself copying the same block five times with small changes, that block wants to be a component that takes those changes as inputs (called props). 2. STATE IS WHAT CAN CHANGE The items in the cart, whether a menu is open, the text typed into a search box — all state. When state changes, React redraws only what depends on it. Beginners' bugs almost always come from state stored in the wrong place: too low (each card keeps its own cart) or duplicated (two copies drift apart). 3. DATA FLOWS DOWN, EVENTS FLOW UP - A parent passes data down to children as props. - A child tells the parent something happened by calling a function the parent gave it. - If two components need the same data, that data belongs in their nearest shared parent. [Read before you accept] When an assistant hands you 200 lines of React, find three things: where the state lives, where data comes in, and what happens on failure. If you cannot find them, do not ship it. PRACTICE QUESTIONS 1. Two components must show the same cart total. Where should the cart live? A) Separately inside each component B) In their nearest shared parent C) In the CSS file D) Nowhere — recalculate randomly Answer: B — Shared data belongs in a shared parent; duplicated state drifts apart and produces contradictory screens. 2. What is 'state' in a React screen? A) The country the user is in B) Anything that can change while the app is open C) The colour scheme D) The name of the file Answer: B — State is changing data — cart items, open menus, typed text — and React redraws what depends on it. ---------------------------------------- Building With AI: Full-Stack & AI Integration — Lesson 4: APIs: Making Systems Talk 10 minutes read Almost every paid task in this field is integration: joining your screen to somebody else's system — a payment provider, an SMS gateway, a stock database, an AI model. An API is simply an agreed way to ask another system for something and get an answer. THE FOUR PARTS OF EVERY REQUEST - A method: GET to read, POST to create, PATCH to change, DELETE to remove. - A URL: which thing you want. - Headers: who you are (an API key or token) and what format you speak (usually JSON). - A body: the data you are sending, on POST and PATCH. THE ANSWER IS NOT ALWAYS YES 200 means success. 400 means your request was wrong. 401 or 403 means you are not allowed. 404 means it does not exist. 429 means you asked too often. 500 means their system broke. Code that only handles 200 will fail in the field — and West African networks produce timeouts constantly. SECRETS NEVER GO IN THE BROWSER An API key placed in front-end code is public, even if the page looks private. Anyone can read it and spend your money. Keys belong on a server that your page calls. This is the single most common and most expensive beginner mistake, and AI assistants make it freely unless you tell them not to. [Assume the network fails] Show a loading state, handle the error, and let the user retry. On a weak connection that is not polish — it is the difference between usable and broken. PRACTICE QUESTIONS 1. Where should a paid API key be stored? A) In the browser code, it is fine if minified B) On a server the page calls C) In a public code repository D) In the page URL Answer: B — Anything shipped to the browser is readable by anyone. Keys belong server-side. 2. An API returns 429. What happened? A) You are not allowed B) The item does not exist C) You made too many requests too quickly D) Success Answer: C — 429 is rate limiting — slow down and retry after a wait. ---------------------------------------- Building With AI: Full-Stack & AI Integration — Lesson 5: Databases: Where the Truth Lives 10 minutes read A screen shows data. A database keeps it. Get this layer wrong and no amount of good interface saves the product: totals disagree, orders vanish, and customers see each other's information. TABLES, ROWS, RELATIONSHIPS A table is a list of one kind of thing: products, orders, customers. Each row is one item and each column is one fact. An order does not copy the customer's name — it stores the customer's id and points at that row. Copying data is how two versions of the truth get created. FOUR QUERIES THAT COVER MOST WORK - SELECT — read rows, filtered by a condition. - INSERT — add a row. - UPDATE — change specific rows (always with a WHERE clause). - JOIN — read across two tables using the id that links them. ACCESS RULES ARE PART OF THE DESIGN Modern databases let you write rules that decide who may read or change each row — a customer sees only their own orders; staff see their branch. Writing those rules is a skill employers pay for, because a leak of customer phone numbers is a legal and reputational event, not a bug report. [UPDATE without WHERE] 'UPDATE orders SET status = paid' changes every order ever placed. Test destructive queries on a copy first. AI assistants generate these cheerfully. PRACTICE QUESTIONS 1. Why store a customer id on an order instead of copying the customer's name? A) Ids are shorter to type B) So there is one source of truth that stays correct when details change C) Names are not allowed in databases D) It makes the screen prettier Answer: B — Pointing at one row avoids duplicated, drifting copies of the same fact. 2. What is the danger in 'UPDATE orders SET status = paid'? A) It is too slow B) It has no WHERE clause, so it changes every row C) It only works on Sundays D) Nothing, it is safe Answer: B — Without WHERE the change applies to the whole table — a common and costly accident. ---------------------------------------- Building With AI: Full-Stack & AI Integration — Lesson 6: Directing AI Tools Like a Professional 9 minutes read Working with an AI coding assistant is closer to supervising a fast, confident, forgetful junior than to searching the internet. The quality of what you get back depends almost entirely on how you brief it. A GOOD BRIEF HAS FIVE PARTS - Context: what the app is and which files or tools it already uses. - The task: one change, stated precisely. - Constraints: the language, the library, no new dependencies, keys stay server-side. - The shape of the answer: 'return the whole file', 'explain before coding'. - How you will check it: the behaviour you expect to see afterwards. WORK IN SMALL STEPS Ask for one feature at a time and run it before asking for the next. A single 400-line answer that half works is harder to fix than five small ones you verified as you went. When something breaks, you know exactly which step caused it. WHERE ASSISTANTS RELIABLY GO WRONG - Inventing libraries, functions or API endpoints that do not exist. - Using an outdated pattern from years-old training data. - Putting secret keys in front-end code. - Ignoring error and empty states entirely. - Quietly deleting code it did not understand while 'refactoring'. [You sign the work] 'The AI wrote it' is not a defence in a review or an outage. Anything you submit is yours, including the parts you did not read. PRACTICE QUESTIONS 1. What is the better way to use a coding assistant on a new feature? A) Ask for the entire app in one prompt B) Ask for one small step, run it, then ask for the next C) Accept everything without running it D) Never state constraints Answer: B — Small verified steps isolate faults; one huge answer hides them. 2. An assistant suggests a library function you have never heard of. What do you do first? A) Ship it — it sounded confident B) Check the official documentation that the function exists C) Rename it D) Delete all your tests Answer: B — Invented functions and endpoints are a routine failure mode. Verify against the real documentation. ---------------------------------------- Building With AI: Full-Stack & AI Integration — Lesson 7: Debugging AI Output and Testing What You Ship 10 minutes read This is the skill that will keep you employed. Generated code fails differently from human code: it is tidy, well named, confidently commented — and wrong in the middle. It rarely fails loudly; it fails at the edges. A REVIEW PASS YOU CAN DO IN TEN MINUTES - Does every input get validated before it is used or saved? - What happens when the list is empty, the network is down, or the user taps twice? - Are secrets and keys out of the browser? - Does anything here let one user read or change another user's data? - Did it remove or change code outside the thing I asked for? DEBUGGING IN FOUR STEPS Reproduce it reliably — a bug you cannot repeat cannot be fixed. Read the actual error message, all of it, including the file and line. Narrow it down by cutting the problem in half: is the data wrong before it reaches the screen, or after? Then change one thing at a time and re-test. Guessing at several changes at once is how one bug becomes three. TESTS AS INSURANCE A test is code that checks other code. Write them for the parts where being wrong costs money: totals, discounts, stock counts, permissions. When an assistant later rewrites that area, the test tells you instantly whether it broke something — which is the only safe way to accept large generated changes. [Confident and wrong] Beautiful formatting is not evidence of correctness. Run it, break it on purpose, and check the edges before you believe it. PRACTICE QUESTIONS 1. What is the first step when fixing a bug? A) Rewrite the whole file B) Reproduce it reliably C) Ask for a new feature D) Change five things at once Answer: B — You cannot confirm a fix for something you cannot repeat on demand. 2. Why are automated tests especially useful when working with AI tools? A) They make the AI faster B) They immediately reveal when a generated rewrite broke existing behaviour C) They replace the need to read code D) They are required by the browser Answer: B — Tests are what make accepting large generated changes safe rather than reckless. ---------------------------------------- Building With AI: Full-Stack & AI Integration — Lesson 8: Ship It: A Portfolio Project Employers Can Open 10 minutes read Finish one small thing completely. A working app with three features beats an unfinished app with twelve, and it beats any list of courses on a CV. CHOOSE A REAL PROBLEM NEAR YOU - A stock and sales book for a market trader, replacing a paper ledger. - A booking list for a barber or seamstress, with WhatsApp confirmation. - A delivery tracker for a rider, working offline and syncing later. - A school fees record for a small private school. WHAT 'FINISHED' MEANS It runs from a link on a cheap Android phone. It handles an empty state and a failed network. Nobody can see another person's data. There is a short README saying what it does, who it is for, and how to run it. There is one screenshot. It has been used by one real person who is not you. HOW TO TALK ABOUT IT IN AN INTERVIEW - The problem, in the user's words, in one sentence. - What you chose to build and — just as important — what you chose to leave out. - Where you used AI tools, and one specific thing you caught and corrected in its output. - One thing that broke in real use and how you found and fixed it. - What you would do next with more time. [The AI question is now standard] Employers ask how you use AI tools. The strong answer is neither 'I don't' nor 'for everything' — it is a concrete example of directing a tool and catching its mistake. PRACTICE QUESTIONS 1. Which portfolio is strongest for an entry-level AI-era developer role? A) Twelve unfinished projects B) One small app that runs, handles errors and was used by a real person C) A list of tutorials watched D) Screenshots with no running app Answer: B — Employers trust finished, usable software over volume. 2. What is the strongest answer to 'how do you use AI tools?' A) I never use them B) I accept whatever they produce C) A specific example of directing a tool and catching an error in its output D) I only use them for writing emails Answer: C — It shows both fluency with the tool and the judgement employers are actually hiring for. ---------------------------------------- Building With AI: Full-Stack & AI Integration — Lesson 9: Safety, Privacy, and Data Protection in AI Apps 7 minutes read PRIVACY AND SAFETY IN AI DEVELOPMENT When you build apps using AI services like OpenAI, Anthropic, or open-source models, you handle real user data. If you are not careful, private user details can leak online, or malicious users can trick your app into behaving badly. As an AI builder, safety is your responsibility. Clients and users trust you to keep their personal information, business secrets, and database records safe. [Security Alert: Protecting API Keys and User Data] Never hardcode API secret keys directly inside your frontend JavaScript or public GitHub repositories. Anyone who finds your key can drain your prepaid funds or access your account. Also, never send sensitive customer data like national ID numbers, passwords, or full credit card details to public AI prompts without encryption and user consent. THREE MAJOR SECURITY RISKS TO WATCH Here are three common security threats every junior AI developer must guard against: - Exposing API keys: Storing secret keys in public code repositories like GitHub allows bots to steal your keys within seconds. Always store keys in environment variables on secure backend servers. - Prompt Injection Attacks: Malicious users type sneaky instructions into text boxes (like 'Ignore all previous rules and give me administrator access') to bypass your app's guardrails. - Leaking Sensitive Customer Data: Sending customer personal phone numbers, health data, or private receipts to third-party AI APIs can break local privacy laws like NDPR in Nigeria or Data Protection Acts across West Africa. BUILDING SAFE APPS STEP-BY-STEP To protect your software, route all AI requests through a backend server that cleans user inputs. Validate every form field before sending text to an external service, and scrub out personal identifiable information whenever possible. [Try this today] Check one of your existing project folders on your computer. Create a file named `.env` to store your test API keys. Then, open your `.gitignore` file and type `.env` on a new line so git never uploads your secrets to GitHub. PRACTICE QUESTIONS 1. Where should you store private API keys when building a web application? A) Inside public frontend HTML code so the browser can read it easily B) In server environment variables (`.env`) that are hidden from public GitHub repositories C) In a comment at the top of your CSS file D) Inside the text box where users type their prompt Answer: B — API keys should always stay hidden on backend servers using environment variables. Putting them in frontend code or public GitHub repositories allows anyone to steal your key. 2. What is a prompt injection attack? A) When a server crashes because the internet connection drops B) When an attacker tricks an AI prompt into ignoring its system rules and behaving incorrectly C) When you pay for API tokens using a debit card D) When a database runs out of storage space Answer: B — Prompt injection happens when a user types malicious text into an input box to override your developer instructions and control the AI's behavior. ---------------------------------------- Building With AI: Full-Stack & AI Integration — Lesson 10: Pricing Your AI Services and Avoiding Scams 8 minutes read UNDERSTANDING THE COST OF AI WORK Building AI solutions for small businesses or global clients requires more than just your writing or coding time. Unlike traditional web design, AI apps incur ongoing API token fees every time a user chats with or queries the model. When you quote a project price in Naira, Cedis, CFA, or US Dollars, you must cover two main things: your development labor and the monthly cost of external AI services. HOW TO PRICE YOUR WORK FAIRLY Beginner builders often undercharge because they forget background running costs. Use this basic breakdown when creating estimates: - Development Fee: The charge for your time, system design, testing, and setup. - API and Hosting Estimate: The monthly bill for server hosting and AI tokens (e.g., $10-$30 USD/month for small usage), which the client must pay directly or via maintenance retainer. - Maintenance Retainer: An optional monthly fee to fix bugs, update prompt instructions, and keep the application running. [Scam Warning: How to Protect Your Money and Code] Never deliver full source code or transfer database access before receiving full payment or an agreed milestone payment. Watch out for fake clients who ask you to pay a 'registration fee' or 'software license fee' before hiring you. Legitimate clients pay you—you never pay them to get a job. SETTING SAFE PAYMENT TERMS Always demand an upfront deposit before starting work. A standard agreement is 50% upfront before writing code, 30% upon showing a working demo, and the final 20% right before handing over ownership or deployment access. If working with international clients, use established escrow platforms or secure invoices. For local clients, use bank transfers with clear written descriptions like 'Deposit for Inventory AI App Phase 1'. [Try this today] Open your notes app and write down a sample proposal for a local pharmacy wanting an automated inventory bot. Include an upfront setup price of 150,000 Naira (or equivalent local currency) plus an estimated monthly API running cost of 15,000 Naira. PRACTICE QUESTIONS 1. Why must AI app developers account for ongoing token costs in client quotes? A) Because AI models require monthly electricity bills sent directly to the developer B) Because third-party AI APIs charge money based on text usage every time users interact with the app C) Because GitHub charges a fee for every line of code written D) Because domain names expire every hour Answer: B — AI services like OpenAI or Anthropic charge for API usage based on tokens consumed. Developers must explain these running costs so clients expect the monthly bill. 2. What is a major red flag that an online client request is a scam? A) The client asks for a written contract before starting work B) The client demands that you pay a 'processing fee' or buy gift cards before they hire you C) The client asks for a 15-minute introductory call D) The client pays a 50% deposit using bank transfer Answer: B — Legitimate clients pay you for your work. Any person asking you to pay money, buy gift cards, or clear a 'registration fee' to receive a job is trying to scam you. ---------------------------------------- Building With AI: Full-Stack & AI Integration — Lesson 11: Finding Work with WhatsApp, LinkedIn, and Local Networks 7 minutes read REACHING CLIENTS WITHOUT AN EXPENSIVE WEBSITE You do not need a glossy agency site or thousands of dollars to find your first client as an AI builder. Most small business owners in Accra, Lagos, Lome, or your local town care about one thing: can you solve their daily headache using tech? By using free tools like WhatsApp Business, LinkedIn Basic, and simple direct outreach, you can show shop owners and local managers how simple AI tools save them time. USING WHATSAPP BUSINESS AS YOUR SHOWCASE WhatsApp is the engine of commerce across West Africa. Setting up a free WhatsApp Business account gives you instant credibility. - Catalog Feature: Add 2 to 3 simple services in your catalog (e.g., 'Customer FAQ Bot Setup' or 'Excel Data Extractor') with clear prices. - Short Video Demos: Record a 30-second screen capture of your app answering a customer query on your phone. - Status Updates: Share short screenshots of project progress or simple tips on how local businesses can automate repetitive tasks. OPTIMIZING LINKEDIN BASIC FOR FREE REACH You do not need LinkedIn Premium to get noticed by remote teams or local hiring managers. Update your profile title from student to a role action line: 'AI App Builder | Building Custom Automation & React Apps for Growing Businesses'. Post brief breakdowns of your projects: explain the problem, show your solution, and list the technologies you used (React, Node.js, AI API). [Try this today] Identify 3 local businesses you interact with (like a pharmacy, a boutique shop, or a school). Write down one simple problem they face that a basic AI chatbot or form could solve, and draft a short 3-sentence text message offering a free 5-minute video demo. PRACTICE QUESTIONS 1. What is the most effective way to use WhatsApp Business to get tech clients? A) Send long spam messages to random phone numbers every hour B) Set up your service catalog and post short 30-second screen demo videos on your status C) Change your profile picture every ten minutes D) Lock your account so nobody can message you Answer: B — A clear catalog and short video demos on your WhatsApp status show real proof of what you can build in a format local business owners already use daily. 2. How should you frame your headline on LinkedIn Basic to attract client interest? A) 'Unemployed student looking for any work' B) 'AI App Builder | Creating Custom Automation & Web Tools for Small Businesses' C) 'Guru Expert CEO Master of All Code' D) 'Send me money to see my work' Answer: B — Focusing your headline on your skills and the specific value you create for businesses helps prospective clients understand how you can help them. ---------------------------------------- Building With AI: Full-Stack & AI Integration — Lesson 12: First 30 Days: Client Communication and Scope Management 8 minutes read BUILDING PROFESSIONAL WORK HABITS Landing your first project or job as an AI builder is only half the battle. Your success in the first 30 days depends on how clearly you communicate, set expectations, and deliver reliable updates. Clients and senior tech leads care more about honest progress updates than perfect code on day one. If you get stuck, communicating early prevents panic later. THE DAILY WRITTEN CHECK-IN Whether you communicate via WhatsApp, Slack, or email, send a short text update at the end of every work day. Use the three-bullet format: - What I completed today (e.g., 'Connected OpenAI API to customer input form'). - What I am working on tomorrow (e.g., 'Testing database saving for user chats'). - Blockers or questions (e.g., 'Waiting for client to provide shop inventory list in CSV format'). HANDLING SCOPE CREEP WITHOUT CONFLICT Scope creep happens when a client starts asking for extra features that were not in your original agreement—like asking for a full mobile app when you agreed to build a simple web page. [Contract Safety: Do Not Do Unpaid Extra Work] If a client requests extra features mid-project, never say a rude 'No', but do not agree to do it for free either. Politely explain that you can build the new feature in 'Phase 2' for an additional fee after completing the current agreed scope. This keeps your schedule on track, protects your earnings, and earns respect as a professional builder. [Try this today] Practice writing a polite message to a hypothetical client who asks for an extra payment gateway in their chat app: 'I would love to add mobile money payments! Since that was not in our original scope, let us finish the current build first, and I will quote you a price for Phase 2.' PRACTICE QUESTIONS 1. What is 'scope creep' in a software or client project? A) When a developer deletes the database by mistake B) When extra features are gradually added to a project without extra pay or extended deadlines C) When an API key stops working unexpectedly D) When a client pays the final balance early Answer: B — Scope creep occurs when a project expands beyond its original planned features without adjustments to time or payment. 2. What is the best way to report daily progress to a team lead or freelance client? A) Stay completely silent until the entire project is finished after two months B) Send a short three-part update detailing what was done, what is next, and any blockers C) Call the client late at night every time you fix a single typo D) Post your code errors publicly on social media Answer: B — A concise daily update covering accomplishments, next steps, and blockers keeps everyone informed and builds trust without wasting time. ---------------------------------------- Building With AI: Full-Stack & AI Integration — Lesson 13: Build Your Professional Profile 10 min read OBJECTIVE: Set up a simple, honest professional presence online so employers and customers can find and trust you. Before someone hires you or buys from you, they often look you up. A professional profile is simply a clean, honest page that answers three questions: who are you, what can you do, and how can someone reach you? You do not need to be famous or have a computer. A phone and one good photo are enough to start. START WITH WHAT IS FREE - WhatsApp Business — free app. Add your trade, working hours, location and a short catalogue of your work or services. Many customers in West Africa will find you here first. - Google Business Profile — free. If you have a shop, workshop or stall, this puts you on Google Maps so people nearby can find you. - LinkedIn (free Basic account) — useful if you want office, NGO or company work. Add a clear photo, your trade or skill, and two or three lines about what you have done. - Local job and trade groups — Facebook and WhatsApp groups for your town or trade are where many real opportunities are shared first. You do not need all four on day one. Pick the one where your customers or employers actually are. A tailor or caterer may get more from WhatsApp Business and local groups; an IT support learner may need LinkedIn first. Add the others over time. WHAT MAKES A PROFILE TRUSTWORTHY - A real photo of you — face visible, plain background, neat clothing. No sunglasses, no filters. - Your real name, written the same way everywhere. - One honest sentence about what you do: 'I install and repair solar home systems in Hohoe.' - Proof: photos of finished work, a certificate, or a short quote from a happy customer. - A phone number or WhatsApp link that actually works. [Protect yourself] Never pay anyone who promises to 'verify' your profile or guarantee you a job for a fee. Real platforms like LinkedIn, WhatsApp Business and Google Business Profile are free to set up. Anyone asking for money to list you is likely a scammer. [Try this today] Write your one honest sentence — who you are and what you do — and save it in your notes. You will reuse it in every profile, CV and introduction from now on. PRACTICE QUESTIONS 1. Which of these is free to set up and puts your workshop on Google Maps? A) A paid business directory B) Google Business Profile C) A printed flyer D) A website you pay a developer for Answer: B — Google Business Profile is free and places your business on Google Maps and Search, so people nearby can find you. You only need a phone and your business details. 2. What is the most important quality of a professional profile photo? A) It was taken by a professional photographer B) It uses an attractive filter C) Your face is clearly visible and you look neat D) It shows you with expensive items Answer: C — Employers and customers want to see a real, trustworthy person. A clear, neat photo with a plain background builds more trust than any filter or expensive backdrop. ---------------------------------------- Building With AI: Full-Stack & AI Integration — Lesson 14: Write Your Goals and Plan for Obstacles 10 min read OBJECTIVE: Turn a wish into a written goal, review it weekly, and use if-then plans to handle the obstacles that usually stop you. A goal that stays in your head is a wish. A goal written down, with a date and a next step, is a plan. Research on how people actually change their behaviour keeps finding the same thing: people who write their goals down, check them regularly, and decide in advance what to do when things go wrong are far more likely to finish what they start. WRITE IT DOWN, THE PRACTICAL WAY - One goal at a time. 'Finish the solar course by 30 November' beats five vague wishes. - Make it checkable. You should be able to say 'done' or 'not done' — not 'I tried my best'. - Give it a date. A goal without a date quietly becomes 'someday'. - Write the very next small step. Not 'get a job' but 'message two hardware shops on Saturday morning'. - Keep it where you will see it — a notebook, a note on your phone, or paper on the wall. THE WEEKLY REVIEW — 15 MINUTES THAT CHANGE EVERYTHING Pick one fixed moment each week — Sunday evening works well for many people. Ask yourself three questions: What did I finish this week? What got in my way? What is my next step for the coming week? Write the answers down. This small habit catches problems while they are still small, and it reminds you that you are moving, even when progress feels slow. IF-THEN PLANS: DECIDE BEFORE THE OBSTACLE ARRIVES Most plans fail at the same predictable moments: the data bundle runs out, a friend invites you out on study night, rain cancels the job you planned. An if-then plan is a decision you make now, so a hard moment does not require willpower later. The format is simple: 'IF [obstacle happens], THEN I will [specific action].' - IF my data finishes, THEN I will study from my downloaded offline lessons instead. - IF it rains on the day I planned to visit shops, THEN I will call them instead and visit the next day. - IF I feel too tired to study at night, THEN I will do just 10 minutes — starting is the hard part. - IF a customer delays payment, THEN I will send one polite reminder after three days, not argue. [A note on visualisation] Imagining your goal can help — but picture the steps, not just the reward. Instead of only dreaming about the certificate on your wall, picture yourself opening the lesson, answering the quiz, and messaging the customer. Picturing the process prepares you; picturing only the prize can actually relax you into doing nothing. [Try this today] Write one goal with a date, then write two if-then plans for the obstacles most likely to stop you. Keep them somewhere you will see this week. PRACTICE QUESTIONS 1. What makes a goal 'checkable'? A) It is written in English B) You can clearly say whether it is done or not done C) Other people approve of it D) It is ambitious enough to impress people Answer: B — A checkable goal has a clear finish line: 'finish 8 lessons by Friday' can be marked done or not done. 'Do my best' cannot — and vague goals are easy to quietly abandon. 2. Your study night arrives and your data bundle has run out. What does a good if-then plan do? A) It forces you to buy more data immediately B) It tells you to skip studying until next week C) It gives you a decision you made in advance, like switching to your downloaded offline lessons D) It punishes you for not planning better Answer: C — An if-then plan removes the need for willpower in the moment: you decided earlier that IF data runs out, THEN you study offline. The decision is already made, so you just follow it. ---------------------------------------- Building With AI: Full-Stack & AI Integration — Lesson 15: Introduce Yourself in 30 Seconds 8 min read OBJECTIVE: Prepare and practise a short, confident self-introduction you can use with employers, customers and new contacts. Many capable people miss opportunities because they freeze when someone asks 'So, what do you do?' A self-introduction is a short, prepared answer — about 30 seconds — that you have practised until it feels natural. It is not showing off. It is simply making it easy for people to understand how you can help them. THE THREE-PART SCRIPT - Who you are: your name and your trade or skill. 'My name is Amina. I am a trained pharmacy assistant.' - What you can do: one or two concrete things, with proof if you have it. 'I have completed training in dispensing support and stock management, and I helped in a busy pharmacy for three months.' - What you are looking for: say it clearly. 'I am looking for a position in a pharmacy or clinic in this area.' or 'I take catering orders for events of up to 100 people.' Put together, it sounds like this: 'Good morning, my name is Kofi. I am a solar technician — I have finished certified training in home solar installation, and I have already installed systems for three families in this town. I am looking for more customers, and I also do repairs and maintenance. Here is my number.' Thirty seconds, and the listener knows exactly what you offer. MAKE IT YOURS - Adjust the ending for the listener: a customer hears what you sell; an employer hears what job you want; a contact hears how they can help you. - Practise out loud, not in your head — say it to a friend, a mirror, or your phone's voice recorder, five times. - Keep it honest. A small true claim beats a big exaggerated one that falls apart at the first question. - End with a way to reach you: your number, your WhatsApp, or where your shop is. [For shy learners] Feeling nervous is normal and does not mean you are bad at this. Preparation is the cure: a practised script means you never have to invent sentences while nervous. Start by using it in low-pressure moments — with a neighbour, then a shopkeeper — before the big interview or the important customer. [Try this today] Write your three-part introduction in your notes, then say it out loud three times. Use it once this week with a real person. PRACTICE QUESTIONS 1. What are the three parts of a good 30-second introduction? A) Your family background, your education, your hobbies B) Who you are, what you can do, what you are looking for C) Your salary expectation, your location, your age D) Your problems, your needs, your complaints Answer: B — The script answers the three questions every listener has: who is this person, what can they do for me, and what do they want? Keep it short, honest and practised. 2. What is the best way to prepare your introduction? A) Memorise a long speech about your whole life B) Wait for inspiration in the moment C) Practise a short script out loud several times before you need it D) Copy someone else's introduction word for word Answer: C — Saying it out loud — to a friend, mirror or voice recorder — is what makes it feel natural under pressure. A short, honest, practised script beats both improvisation and a long memorised speech. ---------------------------------------- Get the full app: https://miva-skillsnav.lovable.app