Oracle Visual Builder: Applications That Outlive Their First Release · Module 2 · The workspace and your first app
Naming, and why it matters more than it should
Lesson 19 of 176 · 3 min
Identifiers appear in URLs and in generated code, and SOME CANNOT BE CHANGED LATER. A convention decided now COSTS NOTHING. This is the cheapest lesson in the course and the one with the longest consequences, because the cost of getting it wrong is paid entirely later. IDENTIFIERS ARE NOT LABELS: THEY APPEAR IN URLs, IN GENERATED CODE, AND IN EVERY EXPRESSION THAT REFERS TO THEM. A flow's name is in the address bar; a variable's name is in every binding that uses it. So renaming is not a cosmetic change — it is a change to everything that refers to the thing, and some cannot be renamed at all once created. WHICH MEANS THE FIRST WEEK'S CASUAL NAMES ARE PERMANENT. A flow called main containing something that has nothing to do with anything main. A variable called data. A page called page1 that is the most important screen in the…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.
In this module: Module 2 · The workspace and your first app
- 1The designer, and the four places you will live
- 2Applications, flows and pages
- 3Your first application, start to finish
- 4Preview, and what it is not
- 5The visual designer and the code behind it
- 6Naming, and why it matters more than it should
- 7The browser tools are your real debugger
- 8What breaks: the first-week mistakes
- 9Lab briefing · Build it, run it, break it