week 32 | team project onboarding
Around this time, if the requirements are met, you will be reached out to about being part of the Team Project to complete some prework.
weeks 33 - 42 | entrepreneur project
The Entrepreneur project is for students who want to launch their own web application idea. Start with wireframing, designing the core application infrastructure, and shipping new features consistently. React to user feedback and consistently improve your application with help from weekly 1-on-1 mentor sessions.
week 34 | agile team project, kick-off call
Meet your team members and team lead "face-to-face" and get to know each other. You will be introduced to new tools and given the first tasks to execute for your chess application.
week 35 | agile team project, weekly check-in #1
Weekly Agile team meeting to review code, look at issues and set development goals for the following week.
- Designing the database architecture, building views and setting up the development team infrastructure
week 36 | agile team project, weekly check-in #2
Weekly Agile team meeting to review code, look at issues and set development goals for the following week.
- Work on chess logic and finalize the database layout.
week 37 | agile team project, weekly check-in #3
Weekly Agile team meeting to review code, look at issues and set development goals for the following week.
- Figuring out the logic for moving pieces and implementing javascript to support it.
week 38 | agile team project, weekly check-in #4
Weekly Agile team meeting to review code, look at issues and set development goals for the following week.
- Cleaning up and refactoring code. Determine the advanced chess features that you want to build into the app.
week 39 | agile team project, weekly check-in #5
Weekly Agile team meeting to review code, look at issues and set development goals for the following week.
- Work on writing tests and making sure that moves being performed are allowed or not.
week 40 | agile team project, weekly check-in #6
Weekly Agile team meeting to review code, look at issues and set development goals for the following week.
week 41 | agile team project, weekly check-in #7
Last meeting where we work on tasks that have not yet been finished and clear out tasks from the backlog.
week 42 | agile team project, retrospective
We talk about what worked and what didn’t work during the creation of the app. We then discuss how we would approach it differently if we were to start from scratch.

Accelerated Pace

2 weeks | firehose intro
A fundamental coding course, including an HTML/CSS portfolio page, Ruby code, flow control, functions and the perfect preparation for the Firehose Core Program.
week 1 | build your splurty app
A database-powered quotes generator with a slick, mobile-first design, built with Ruby on Rails, HTML, CSS3, GitHub, and Heroku.
week 2 | blogging about code
Read about the importance of blogging and expressing your passion for web development. Sharing your knowledge on a coding related topic indicates you really do have passion and drive when it comes to coding and aren't just phoning it in.
week 2 | web application overview
Understand how the different pieces of a web application fit together and dive into MVC architecture, HTTP requests, database migrations and routing inside your Splurty app.
weeks 2 - 5 | build your nomster app
A Yelp clone integrated with Google Maps and features like user comments, start ratings, image uploading, user authentication, automated email notification messages and admin dashboards.
week 3 | object oriented programming
Understand object oriented programming in Ruby, learn how to write your own classes and prepare yourself for the algorithmic coding challenges.
week 4 | coding challenge, image blur #1
Understand Object Oriented Programming. You will need to master arrays to solve this problem including creating arrays, iterating over an array, and even using 2-Dimensional arrays.
weeks 5 - 6 | coding challenge, image blur #2
In the previous coding challenge we built a data representation of a pure black and white image. In this challenge we will perform a transformation on the image data.
weeks 6 - 10 | build your flixter app
A two sided video streaming marketplace, featuring credit card payment capabilities, user role management, advanced UI & UX, and advanced database relationships
weeks 6 - 7 | oop with inheritance
Learn how Inheritance fits into object oriented programming, how it is used inside Ruby and how to use it in your code.
weeks 7 - 8 | javascript intro
Learn how to write and integrate JavaScript into your web applications to build interactive features, and understand how JavaScript is different from Ruby.
week 8 | coding challenge, image blur #3
This problem builds off the previous coding challenge and is designed to bring your coding abilities to their furthest levels. This will be the last assignment that will involve manipulating the image data structure we built earlier.
weeks 9 - 10 | coding challenge, linked list #1
In this coding challenge we are going to implement data structures by hand, and we're only going to have the bare essentials to deal with.
weeks 10 - 12 | use a tdd first approach
The industry standard - build automated software tests in Ruby, ensure good test coverage and release perfectly tested code on a professional web developer level.
weeks 10 - 11 | advanced git and version control
Use git and GitHub in advanced mode and understand how to use branches, pull requests and merges.
weeks 11 - 12 | coding challenge, linked list #2
Using the code from the last coding challenge, we will figure out how to change the direction the arrows point and reverse the list.
weeks 12 - 13 | advanced javascript concepts
Start getting comfortable with the advanced concepts that make JavaScript different from other programming languages. Learn about the Event Queue, Asynchronous Processing and fundamentals of the JavaScript language.
weeks 13 - 15 | javascript foundations
Work mastering the JavaScript programming language. Work with JavaScript coding challenges in the command-line using NodeJS.
weeks 13 - 15 | single page application
Build a Single Page application that is a full application that doesn't have any page refreshes, and instead uses AJAX to update the database.
weeks 13 - 14 | coding challenge, luhn algorithm
The Luhn algorithm is a method that credit cards and other identification numbers have which determines valid numbers from invalid ones.
week 14 | team project onboarding
The Team Project is one of the final project paths that we offer. Since it requires a lot of time and dedication, we require students meet the following requirements by the end of week 14:
  1. Be able to dedicate 20+ hours a week
  2. TDD App
  3. Algorithms Chapters 1 & 2
Around this time, if the requirements are met, you will be reached out to about being part of the Team Project to complete some prework.
weeks 14 - 22 | job preparation resources
Prepare for and tackle the developer job search. Learn key strategies, organize your job search, and nail the technical interview.
weeks 15 - 22 | choose your path
Agile Team Project: Job seekers build and launch an advanced web application just like in the real world - as part of an amazing team. Merge branches, conduct code reviews, hold weekly agile team meetings, refactor code, and launch new features consistently.
Entrepreneur Project: The Entrepreneur Project is for students who want to launch their own web application idea. Start with wireframing, designing the core application infrastructure, and shipping new features consistently. React to user feedback and consistently improve your application with help from weekly 1-on-1 mentor sessions.
week 15 | agile team project, weekly check-in #1
Weekly Agile team meeting to review code, look at issues and set development goals for the following week.
- Designing the database architecture, building views and setting up the development team infrastructure
weeks 15 - 16 | coding challenge, fibonacci sequence
Determining the value of the Fibonacci sequence for a particular number is one of the classic questions that computer science students solve.
week 16 | agile team project, weekly check-in #2
Weekly Agile team meeting to review code, look at issues and set development goals for the following week.
- Work on chess logic and finalize the database layout.
week 17 | agile team project, weekly check-in #3
Weekly Agile team meeting to review code, look at issues and set development goals for the following week.
- Figuring out the logic for moving pieces and implementing javascript to support it.
weeks 17 - 18 | coding challenge, collatz sequence
Determining the collatz sequence for a number is a problem similar to determining the Fibonacci number, but even more challenging.
week 18 | agile team project, weekly check-in #4
Weekly Agile team meeting to review code, look at issues and set development goals for the following week.
- Cleaning up and refactoring code. Determine the advanced chess features that you want to build into the app.
week 19 | agile team project, weekly check-in #5
Weekly Agile team meeting to review code, look at issues and set development goals for the following week.
- Work on writing tests and making sure that moves being performed are allowed or not.
weeks 19 - 20 | coding challenge, tree traversal
Implement a tree data structure by hand and use it to look for a specific node. This includes both Depth First Search and Breadth First Search.
week 20 | agile team project, weekly check-in #6
Weekly Agile team meeting to review code, look at issues and set development goals for the following week.
week 21 | agile team project, weekly check-in #7
Last meeting where we work on tasks that have not yet been finished and clear out tasks from the backlog.
weeks 21 - 22 | coding challenge, binary tree sort
A binary tree is a data structure, similar to a regular tree, except it explicitly has a maximum of two child nodes. Sorting algorithms are one of the most commonly discussed algorithms in computer science.
week 22 | agile team project, retrospective
We talk about what worked and what didn’t work during the creation of the app. We then discuss how we would approach it differently if we were to start from scratch.