Cosi 165a - IT Entrepreneurship
Database Migration
“If you don’t know the schema of your app, you don’t know your app” - Said one of our outside reviewers over lunch today
ORM means we have to keep the database and the Objects “in sync”
What happens if in release 2 I have to modify the database?
Migration
When you discover you need a new column or table, you can modify the database
E.g.break the “name” field into a “first name” and “last name”
Data Migration
How do I move over all the user records that were already there?
Logic Migration
What has to change in the server code to accomodate this change?
Does this mean that migration is bad?
It’s not good nor bad: it’s unavoidable
It’s much more painful when you are ‘in production’
Was this helpful!?
yes
/
no
Welcome
Term Overview
List of lectures
Guide to this site
Entrepreneurial Projects
Lectures
Lean Startup Immersion
Welcome!!
Intro to Lean Startup
Hypotheses/Assumptions
Minimum Viable Product
Review and practice
Metrics & Growth Engine
Pivot and Grow
Pilot Project Conclusion
Frame 1
Term project Kickoff
Market segments/Value Prop
Quant and Qual Testing
Mockups and Prototypes
Business Models
Frame 1 Conclusion
Frame 2
UI and UX Basics
User Experience Flow
Product Architecture
Client and the server data models
Frame 2 Review
Frame 3
Pricing Models
Finance for Geeks
Growth Hacking
Real World Survival Kit
Intellectual Property [IANAL]
Marketing for Entrepreneurs
Pizza Party?!
Background
Learning Objectives
Homework info
FAQ for Pito Salas
Grading
Teachers
Lexicon
Interesting links
Credits and acknowledgements
Catalog of Topics