Modern web applications are expected to facilitate collaboration, with user participation being a significant facet of the system. Components such as wikis, blogs, and forums are now commonplace. While feature sets continue to expand, there is continuing pressure to develop and deploy capabilities more quickly to enable organizations to remain competitive. This pressure has led to the development of languages and frameworks geared toward rapid prototyping, with Ruby on Rails being the most popular. Ruby on Rails is a model-view-controller (MVC) framework that enables efficient application development and deployment. Techniques such as convention over configuration and object-relational mapping with ActiveRecord along with enhanced AJAX support offer a simple environment with significant productivity gains. This code-intensive course introduces Ruby on Rails, the patterns it implements, and its applicability to the rapid development of collaborative applications.
The course materials are divided into modules which can be accessed by clicking Modules on the course menu. A module will have several sections including the overview, content, readings, discussions, and assignments. You are encouraged to preview all sections of the module before starting. Most modules run for a period of seven (7) days, exceptions are noted in the Course Outline. You should regularly check the Calendar and Announcements for assignment due dates.
By the end of this course, students will be able to:
Fully utilize Ruby on Rails framework in order to rapidly develop and deploy web applications.
There are no required textbooks, but the following 2 textbooks (1 for Ruby and 1 for Rails) are recommended if you feel that reading might aid your Ruby/Rails knowledge:
1. Agile Web Development with Rails 6
2. Head First Ruby or Eloquent Ruby
Students will need access to the following software bundles:
Ruby 2.5+ with DevKit
Rails 6.0
Git
It is expected that each class will take approximately 5–10 hours per week to complete. Here is an approximate breakdown: listening to the audio annotated slide presentations (approximately 2–3 hours per week), coding assignments (approximately 3–6 hours per week) and some possible outside reading (approximately 1 hour a week).
Students may choose to work on coding assignments in teams of 2. In the beginning of the course, you will have an option to pick your own teammate. If you don’t pick a teammate – you may choose to be assigned a teammate to work with. The grade gotten on the assignment by the team is the grade that both students receive. While I strongly encourage teamwork (specifically for this course since we are dealing with technologies like Git), I understand if you would like to work alone and are not interested in joining a team. Please, DO let me know either way by sending me an e-mail. The course consists of 8 coding assignments and 3 quizzes.
The breakdown of the final grade is as follows:
Assignments are due according to the dates in the Calendar. The grades for the assignments will be posted one to two weeks after assignment due dates. Each assignment will get a letter grade of either A, A-, B+, B, and so on. Late assignments will automatically get a half a letter grade lower (A- instead of A, B+ instead of A- and so on) AND a half a letter grade lower for every 24 hours late thereafter unless you contact me in advance and I grant you an extension. “In advance” means at least 48 hours before the assignment is due.
You must have an email from me stating that I granted you an extension, which means that you need to send me an email asking for one. Please, keep the email stating that you were granted an extension until the end of the course (when you receive your final course grade). If I made a mistake, you’ll have proof that I did, in fact, give you an extension.
Deadlines for Adding, Dropping and Withdrawing from Courses
Students may add a course up to one week after the start of the term for that particular course. Students may drop courses according to the drop deadlines outlined in the EP academic calendar (https://ep.jhu.edu/student-services/academic-calendar/). Between the 6th week of the class and prior to the final withdrawal deadline, a student may withdraw from a course with a W on their academic record. A record of the course will remain on the academic record with a W appearing in the grade column to indicate that the student registered and withdrew from the course.
Academic Misconduct Policy
All students are required to read, know, and comply with the Johns Hopkins University Krieger School of Arts and Sciences (KSAS) / Whiting School of Engineering (WSE) Procedures for Handling Allegations of Misconduct by Full-Time and Part-Time Graduate Students.
This policy prohibits academic misconduct, including but not limited to the following: cheating or facilitating cheating; plagiarism; reuse of assignments; unauthorized collaboration; alteration of graded assignments; and unfair competition. Course materials (old assignments, texts, or examinations, etc.) should not be shared unless authorized by the course instructor. Any questions related to this policy should be directed to EP’s academic integrity officer at ep-academic-integrity@jhu.edu.
Students with Disabilities - Accommodations and Accessibility
Johns Hopkins University values diversity and inclusion. We are committed to providing welcoming, equitable, and accessible educational experiences for all students. Students with disabilities (including those with psychological conditions, medical conditions and temporary disabilities) can request accommodations for this course by providing an Accommodation Letter issued by Student Disability Services (SDS). Please request accommodations for this course as early as possible to provide time for effective communication and arrangements.
For further information or to start the process of requesting accommodations, please contact Student Disability Services at Engineering for Professionals, ep-disability-svcs@jhu.edu.
Student Conduct Code
The fundamental purpose of the JHU regulation of student conduct is to promote and to protect the health, safety, welfare, property, and rights of all members of the University community as well as to promote the orderly operation of the University and to safeguard its property and facilities. As members of the University community, students accept certain responsibilities which support the educational mission and create an environment in which all students are afforded the same opportunity to succeed academically.
For a full description of the code please visit the following website: https://studentaffairs.jhu.edu/policies-guidelines/student-code/
Classroom Climate
JHU is committed to creating a classroom environment that values the diversity of experiences and perspectives that all students bring. Everyone has the right to be treated with dignity and respect. Fostering an inclusive climate is important. Research and experience show that students who interact with peers who are different from themselves learn new things and experience tangible educational outcomes. At no time in this learning process should someone be singled out or treated unequally on the basis of any seen or unseen part of their identity.
If you have concerns in this course about harassment, discrimination, or any unequal treatment, or if you seek accommodations or resources, please reach out to the course instructor directly. Reporting will never impact your course grade. You may also share concerns with your program chair, the Assistant Dean for Diversity and Inclusion, or the Office of Institutional Equity. In handling reports, people will protect your privacy as much as possible, but faculty and staff are required to officially report information for some cases (e.g. sexual harassment).
Course Auditing
When a student enrolls in an EP course with “audit” status, the student must reach an understanding with the instructor as to what is required to earn the “audit.” If the student does not meet those expectations, the instructor must notify the EP Registration Team [EP-Registration@exchange.johnshopkins.edu] in order for the student to be retroactively dropped or withdrawn from the course (depending on when the "audit" was requested and in accordance with EP registration deadlines). All lecture content will remain accessible to auditing students, but access to all other course material is left to the discretion of the instructor.