In this episode, we speak with Letladi Sebesho, a South African developer who recently completed all (well, most) of the Launch School courses. He talks about how Launch School compares with his computer science courses, his job hunt process, and also how he’s been doing now that he’s been working for a few months.
In this episode, Jay Shenk talks about changing career goals from an aspiring clarinetist to a programmer and how he applies what he learned as a trained musician to programming. Jay’s been at Launch School for around a year and shares some advice and tips around how to make the most out of your Launch School experience.
Terry Lee came on the podcast today to talk about her experience so far at Launch School. Terry has been at Launch School for about a year and has aced every assessment so far. She talks about her previous career as a product manager, getting laid off, and then doubling down on her own education. We also talked about her recent participation at a hackathon and how she contributed despite not knowing the technology stack being used.
We’re happy to introduce our newest book, Core Ruby Tools, to our Open Bookshelf! This book provides a short tour of four core Ruby tools: Gems, Ruby Version Managers, Bundler, and Rake. We’ll see how these tools fit into the Ruby environment and your computer system, and learn how to diagnose and fix problems that you may encounter when using them.
We’ll give you a sneak peek into the book by including its introduction chapter in this blog post.
Naveed is has been learning at Launch School for around a year and has been an outstanding student so far. He’s nearing the end of the curriculum and stopped by the podcast today to share his story. We talked about the unique challenges of Mastery-based Learning from a remote village in Pakistan. He has to deal with issues ranging from consistent internet connectivity to pricing — you won’t believe what he’s had to do to pay for his subscription to Launch School.
In part 3 of this series, we focused on isolating our view related code to a
views directory, and moving it out of our main application code. In this post, we’ll continue to separate out the view related code for our other routes, and then finally, we’ll extract some more general purpose methods to a framework. This is the last step in our work to “grow” a web development framework. Let’s get started.
Part 2 of this series focused on routing and expanding our application to serve back HTML responses. In this post, we’ll start to think about separation of responsibilities between our core routing logic and our views. We’ll introduce a library
ERB that will help us turn Ruby code into HTML. Finally, we’ll update our application code to include view templates.
In part 1 of this series, we explained what Rack is and how to use it to build a simple web application. In this post, we’ll be expanding on that by adding in different URL endpoints. To do this we’ll also have to delve a bit deeper into how Rack keeps track of request data via headers.
This post is the first part in a four part series on how to build your own web framework with Rack. The 4-part series will cover what rack is, how to use it to handle incoming requests, how to use templating techniques to return a response, and finally, how to extract common code to plant the seeds for your very own web application development framework. Here in part 1, we’ll give a short introduction on what Rack is and how to use it. We’ll end things by building a simple Rack application.
Darren Burgess stopped by the podcast to talk about his experience at Launch School. Before starting at Launch School, he spent many years as a Filemaker Pro developer and even attended a different coding “bootcamp”. We talked about the learning process he’s been on and why he almost left Launch School.