This is the 4th (and final) part of a 4 part series. Part 1: Application + Database setup Part 2: Validations + Transactions Part 3: Testing In this last part, we're going to make it so that our application can receive and respond to HTTP requests. So far, we've been seeing how to use gems either from the dry-rb suite of gems, or the rom-rb suite of gems. In this part though, we're going to be using a gem from a different suite, a...
This post (and talk) is an updated version of my 2018 "Hiring Juniors" talk at RubyConf AU. This version of the talk was given at RubyConf Indonesia 2019 as the closing keynote. You can view the slides for this talk on Speakerdeck Intro Who's hiring right now? And who's finding it easy to hire developers at the moment? If you said it was easy to hire developers at the moment, you're either very lucky or lying. I work at a...
For the past two years, I have ran not one but two successful Junior Engineering Programs (JEPs) at Culture Amp. The official number of developers that I have trained there is 19. But I trained a bunch more developers from time-to-time as well. So the proper total would probably be in the range of 30-40 developers at Culture Amp that I have helped train, support and grow over the past two years. I am really proud of this work that I...
Really early on in Rails, you would write routes like this: redirect_to :controller => "posts", :action => "show", :id => @post.id What this would do is dutifully redirect to the show action inside the PostsController and pass along the id parameter with a value of whatever @post.id returns. Typical 302 response. Then Rails 1.2 came along and allowed you to use routing helpers, like this: redirect_to...
I've been revisiting Twist v2 recently. It's my book review tool that I've rebuilt multiple times over the past 8 years. Its latest incarnation is what I'm calling a "duolith": a very light Hanami backend application with a GraphQL API, and a frontend built with React and Apollo. The backend and the frontend codebases are kept in separate directories in the same codebase. This allows for separation between the Ruby and...
This post is part of a series of posts about the first cohort of the Culture Amp Junior Engineering Program (JEP). You can read the first two posts here: Junior Engineering Program: Launch Junior Engineering Program: Onboarding In the last post I covered the process of what we did in the weeks immediately following the juniors starting, but didn't talk too much about what we taught them during those or subsequent weeks. That is what...
This post is a short summary of the Culture Amp Junior Engineering Program (JEP) that I ran from November last year until June this year. If you're keen to apply for the 2nd cohort then you can do that here: Apply here for the Culture Amp Junior Engineering Program's second cohort This post is the first in a series of four blog posts which will go into detail about how the last JEP operated, with the aim of giving potential future...
Here are my raw speaker notes for my Web Directions Code Leaders talk, titled "Hiring Juniors". The video will be online later. The slides for this talk are available here on Speakerdeck Intro [slide] Hi, I'm Ryan. You know that part already. What you might not know is that I've been mentoring juniors on-and-off for close to a decade now and I've had varying rates of success. I've mentored juniors who have gone on to become...
This blog post has been translated into Japanese, thanks to @hachi8833! A few people have asked for my opinions on DHH's recent video series. And others have bemoaned the lack of a critical take on the videos. So here's...
