It's now the 4th time, I'm teaching the Rails class at the University of Wroclaw. The main goal of this class to prepare people to work in a Rails-based company. The students are the best of the best, so the goals can be high.
Every year, I introduce some changes to the program of teaching to reflect better what is happening in the Rails community.
This year I'm going to focus more than before on the integration with mobile, native apps and on the art of dealing with legacy projects.
We start with extremely quick Ruby lessons, based on the Ruby koans exercises (students do it on their own).
The first 3 lessons are about "the Rails way", which I make it clear - is good only for toy projects. This is where I teach about ActiveRecord-oriented programming, coupling everything with everything, making things impossible to test - you know, the usual Rails stuff.
Once we know the enemy and know the pains it provides, we learn how to avoid that.
This is where good, solid OOP lessons come in, service objects, repositories, domain objects, etc.
After that, we enter the "frontend" module. We learn how to create Single Page Apps using the dominant JS frameworks (Angular) and some no-framework techniques (HexagonalJS. This also includes techniques like Pusher to have server->client communication possible.
We also talk a lot about the way, a Rails backend can expose data through the API to the JS or mobile app clients. Mobile apps will take more time this way, as I want to show how to best cooperate with mobile developers.
There's a lesson about proper Rails deployment, things like Chef, Jenkins, Continuous Deployment etc.
Throughout the class, we'll not only create new Rails apps (lots of them), but I also want to teach how to find yourself in a legacy codebases, like Redmine or Discourse, how to refactor out from the mess, fix bugs, add new features - that's probably the hardest part of the class.
Testing is an ongoing topic in the class, as well. We'll learn about unit testing of different layers, integrated tests and their pains.
I hope it will be fun, as always :)
4 comments:
Great program. I just wonder how much time you spend on this course. One or two semesters? And how many students do you usually teach?
It's one semester.
It's about 30 students each year.
Are there any book/online resources that you think are great for quickly learning and applying OOP lessons in rails? I'm learning Active Record, Rails Way programming right now, but I certainly don't want to be stuck in that as I try to do non-trivial things. I mean, the Active Record programming is pretty good so far for building a simple content management system.
Why "the Rails way" is good only for toy projects? a detailed explanation would be awesome!
PS: Asking this because I'm a final year CS student and I'd like to build my career around Rails. What advice do you have?
Post a Comment