When I’m in my “flow state” as a programmer, what I’m constantly doing is finding ways to eliminate redundancies, learning to recognize that entire subsystems as a whole can be made entirely redundant if I simply took the time to search for higher-level abstractions.
There are no full stack engineers?! Let’s talk about that. Also, just what is a componentized view architecture anyway? I break it all down and explain why I’m gung-ho about view components. Plus I answer questions regarding Stimulus, nice_partials, and other Rails tooling from listeners like YOU! Enjoy, and keep on Ruby-ing!
I’m so glad you could tune in for the debut episode of Fullstack Ruby. I’ve been on a few Ruby-themed podcasts over the past 18 months, but this is the first time I’m running a show about Ruby myself! To kick things off, I’d like to introduce you to Ruby2JS and explain why I think this technology is a game changer.
Today, right now, right this very minute, is the absolute best time to be a fullstack Ruby/web developer! And tomorrow will be even better.
The next big release of Bridgetown provides an intriguing new environment for teaching and learning Ruby and trying out new tools in the Ruby ecosystem.
There are various schools of thought around how best to define dependencies in your object graph. Let’s learn about the one I prefer to use the majority of the time. It takes advantage of three techniques Ruby provides for us: variable-like method calls, lazy instantiation, and memoization.
It kinda sorta works—with several asterisks. Hence the reason it took me so long to even write an article about Ruby 3 typing. I think I’m onboard with where this is all headed, but we have a ways to get there.
Historically, the only way you could truly achieve async parallelism in Ruby would be to fork multiple processes or schedule background jobs. Until now.
Updated for Ruby 3.1! How improved pattern matching and rightward assignment make it possible to “destructure” hashes and arrays in Ruby 3.