Cristian Planas

@cplanas.bsky.social

Engineer & Rubyist. Speaker of tech stuff with a dubious sense of humour (https://www.rubyvideo.dev/speakers/cristian-planas). Author of Rails Scales! (https://t.co/g6sFeDDgp4). I lived around: BCN, HEL, CPH, SF, NYC. Currently @zendesk.

Amid the excitement of #TropicalOnRails, I forgot to share this: Rails Scales!—my upcoming book on Rails performance—has already sold 500+ copies in beta! And it’s not even officially out yet (launching May or June). Thanks to everyone reading early! pragprog.com/titles/cprpo...

Rails Scales!

Build Rails applications that scale. Discover the small changes that make a big difference in efficiency. Design applications for performance from the start.

pragprog.com

EN: On top of an amazing talk, @crplanas also brought a special treat for those of you who love a good read... 👇🏼💜 PT-BR: Além de uma palestra incrível @crplanas também trouxe uma oportunidade para vocês que adoram uma boa lekitura... 👇🏼💜

Bild

Just released a new version of Rails Scales! (pragprog.com/titles/cprpo...). This one includes the completed book. :) I'm currently working on the last revision, which updates the book from Rails 7 to 8. Mostly minor changes, with the exception that now I will cover Solid Queue.

Rails Scales!

Build Rails applications that scale. Discover the small changes that make a big difference in efficiency. Design applications for performance from the start.

pragprog.com

This is so spot on. Two things: 1. Being focused on producing output the fastest way possible means that you will never prioritize "going deep" 2. Going deep (and down the rabbit hole) is how you learn more: but you need to balance it. Figure out how to do both: it's tricky!

Bild

Updating my book to Rails 8 (it was written with an example application written in 7) I found an unexpected difference. In Rails 8, the request logs do not show the amount of memory allocations. This was quite useful for the examples of the book. Any way to turn this back on?

There's this evergreen joke on software development that goes something like this: "We're done with 90% of the project. Which means we only have the other 90% left to go." It's funny because it's true. It's also why experienced engineers are in-demand: they are the "finishers." AI tools: not now.

Bild

Just finished writing my first book, Rails Scales! (pragprog.com/titles/cprpo...) Here is how it ends: "Scalability is also empowering humans to reach their full potential for creativity and innovation. Here's to the Ruby community, and to all the other fools who dream. Here's to the mess we make!"

Rails Scales!

Build Rails applications that scale. Discover the small changes that make a big difference in efficiency. Design applications for performance from the start.

pragprog.com

Posts like this make me realize how opinions in software architecture field have changed in the last years. From a software engineer at AirBnB: "a polished monolith would have served us far better than our sprawling service ecosystem. [...]Microservices made our system more complex and brittle."

Airbnb's Three Biggest Mistakes

This is the perspective of one lowly engineer who cared too much. For context, I spent 6 years at Airbnb from 2016 to 2022, first as a senior engineer, then an engineering manager and finally as a sta...

bit.ly