Studio: attack your design
Why it matters Sparring is a skill. The first time, the attacks feel either obvious or unfair. After a few rounds you start hearing them before you ask.
Studio: this is checked only for being done, not for being good.
Go back to the data model you wrote in module 11, Data models that bend (any one of its problems will do; if you skipped it, describe a model you work with). Describe it in a few lines: the tables or classes and their key fields.
The session
- Paste your description into the on-device tutor with: "Attack this data model. Give me five change requests or failure cases that would break it, most likely first. Do not suggest a new model."
- For each attack, decide: real for this situation, or not? Write one line on why.
- Ask once more: "Which of these could I survive with a small change, and which need a different model?"
- Write down what survives: the parts of your model you would keep, and the one change you would make.
Keep the pen yourself. If the tutor offers a whole new design, note the idea in one line and stay with yours.
Fill in your notes. my_model: a short description of your data model (a string). attacks: at least 3 attacks you got, each with your verdict ("real" or "not real", and why). kept: at least 1 line on what survives, or the one change you would make.
Spotted a problem in this lesson? Report it · Ask about this lesson
This exercise opens soon
Finish the lesson before it and this one unlocks. The whole course is free, no account needed, and you can read this lesson right now.
This browser is blocking cookies for learn.floati.life, so lessons you finished here cannot open in order. Allow cookies for this site and reload.