- PostgreSQL
- SQLite
- MongoDB
- https://medium.com/@jonatisokon/a-framework-for-user-stories-bc3dc323eca9
- Feature-complete
- Decide what your "A-ha" moment is
- Demo on localhost:3000?
- Deploy to Heroku
- Buy a domain, put on AWS or DigitalOcean?
- If you're not going to demo a feature, do you need to build it? If you're launching it, yes you do.
- ERD
- Tables/Collections
- Fields
- Nouns
- Sinatra
- Rails
- Node
- Node w/ Express
- If models are nouns, these are verbs
- RESTful
- Each action that your models need to do
- Based on user flow from user stories
- A wireframe for EVERY page of your app
- Be specific about data points on the page
- Storyboard the user workflow
- Bootstrap
- Foundation
- Pure
- Bourbon
- Black Hole
- Skeleton
- RESPONSIVE?
- Re-wireframe a mobile/responsive version
- Do you need a mobile & web scenario in your User Stories?
- Angular
- Ember
- Backbone
- Knockout
- React
- Meteor
- Why do you want this?
- Because it's "cool"
- Because you want the skill for a job
- Because you read a tutorial on it
- Don't code on master
- Pick a workflow - git or github
- Code on a feature or bugfix branch, always
- Switch to master
- Merge
- Delete old branch...ONLY WHEN YOU ARE SURE MASTER WORKS
- Make new branches for each feature or bugfix that you're working on
- DO NOT MERGE TEN MINUTES BEFORE THE DEMO
- Download all resources you will need
- Figure out how to install them
- Are you going to use a generator?
- MAKE SURE IT WORKS FOR YOU!
- Gulp vs. Grunt - Yeoman vs. Slush
- Bower
- Webpack
- Back-end or front-end - where to start?
- Build static pages first
- Get the CSS to work
- Decide on ID's and classes
- If building responsively, make sure it works here
- Responsive images?
- Start with models
- All database validations
- Figure out your callbacks
- Use as many helper methods (code atomically) as you can
- Set due dates
- Set development targets
- MEET THEM
- USE TRELLO
- Specific
- Measurable
- Achievable
- Relevant
- Time-based
- Slack
- Telegram
- Trello
- SMS