Curated list of episodes, bundled to help you on your learning path!
Videos of tech, infrastructure, hardware and software which non-instructional by nature.
Articles around software and tutorials.
Show your love and support while looking fancy.
Got a question or want to chat about a topic? Let's talk!
Rack provides a minimal, modular, and adaptable interface for developing web applications in Ruby. In this episode, we create and insert our own Rack Middleware into a Rails 6 application.
In this episode, we look at setting up a fresh application with Auth0 and mimic a lot of the commonly used Devise methods to make a transition from Devise to only Auth0 easier.
In this episode, we look at creating a DSL for HTML tables. Though a simple example, it opens a lot of possibilities for consistency and expandable in what can be done with a DSL.
Continuing from the previous episode, we add testing to the Stripe Payments without adding any additional dependencies.
In this episode, we take a look at our GraphQL API that we created from Episode 119 and refactor the mutations and queries so that we keep the structure and API manageable.
In this episode, we create a chat application using Rails 7, esbuild (JS Bundling), CSS Bundling, Hotwire, and Action Text. We also dive into some issues around CSS Bundling and Action Text.
Turbolinks makes navigating your web application faster. Get the performance benefits of a single-page application without the added complexity of a client-side JavaScript framework. Use HTML to render your views on the server side and link to pages as usual.
In this episode, we look at creating an iOS Application which will communicate with the Rails API application from the previous episode.
Time Zones in Rails can sometimes cause confusion and erratic behavior. In this episode, we look at working with Time Zones in Rails.
Using Scenic, you can bring the power of SQL views to your Rails application without having to switch your schema format to SQL. Scenic provides a convention for versioning views that keeps your migration history consistent and reversible and avoids having to duplicate SQL strings across migrations.