<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.xsl" type="text/xsl"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:stanko.io,2005:/talks/feed</id>
  <link rel="alternate" type="text/html" href="https://stanko.io/"/>
  <link rel="self" type="application/atom+xml" href="https://stanko.io/talks/feed"/>
  <link rel="first" type="application/atom+xml" href="https://stanko.io/talks/feed"/>
  <link rel="last" type="application/atom+xml" href="https://stanko.io/talks/feed"/>
  <title>Stanko Krtalic Rusendic: Talks</title>
  <updated>2026-02-14T14:11:33Z</updated>
  <entry>
    <id>tag:stanko.io,2005:Talk/1050011312</id>
    <published>2026-02-14T14:10:40Z</published>
    <updated>2026-02-14T14:11:33Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/working-at-37signals-the-birthplace-of-ruby-on-rails-EYGo2LNyOqQ3"/>
    <title>Working at 37signals: The birthplace of Ruby On Rails</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;Last July I started working at &lt;a href="https://37signals.com/"&gt;37signals&lt;/a&gt;, the company
behind Basecamp, Hey &amp;amp; Fizzy and the place from which the very first version or
Ruby On Rails was extracted back in 2004.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s still the company with the largest influence on the direction of Rails
development with major contributions like ActiveStorage, SolidQueue, Turbo &amp;amp;
Stimulus.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ll talk about how the company works and what it&amp;#39;s like to work there.&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">Last July I started working at 37signals, the company behind Basecamp, Hey &amp; Fizzy and the place from which the very first version or Ruby On Rails was extracted back in 2004.

It's still the company with the largest influence on the direction of Rails development with major contributions like...</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/14</id>
    <published>2024-01-24T12:00:00Z</published>
    <updated>2024-03-22T14:20:17Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/deconstructing-action-cable-uM1SflOFpRUk"/>
    <title>Deconstructing Action Cable</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;A deep dive that explores and explains how Action Cable works starting from the
initial HTTP request all the way to sending bytes over the WebSocket.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/rubyzg/slides/blob/master/2024-01-24/Deconstructing_Action_Cable.pdf"&gt;Slides&lt;/a&gt;
&lt;a href="https://stanko.io/deconstructing-action-cable-DC7F33OsjGmK"&gt;Article&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">A deep dive that explores and explains how Action Cable works starting from the initial HTTP request all the way to sending bytes over the WebSocket.

Slides Article</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/13</id>
    <published>2022-06-15T12:00:00Z</published>
    <updated>2024-03-22T14:17:58Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/hotwired-postKGrYxj1F"/>
    <title>Hotwired</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;This talk will be an introduction to Hotwired, a bundle of three frameworks that
enable server-side rendered pages to act and feel as single page applications.&lt;/p&gt;
&lt;p&gt;The frameworks are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Turbo - a successor to TurboLinks but with expanded functionality through the
addition of turbo frames and turbo streams&lt;/li&gt;
&lt;li&gt;Stimulus - a component framework that turns pre-rendered HTML into JS
components&lt;/li&gt;
&lt;li&gt;Strada - his part of the talk is reverse engineered out of Hey&amp;#39;s source code;
Strada is a framework/communication protocol that enables the frontend JS to
interact with native host functionality&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href="https://github.com/rubyzg/slides/blob/master/2022-06-15/rubyzg_hotwired.pdf"&gt;Slides&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">This talk will be an introduction to Hotwired, a bundle of three frameworks that enable server-side rendered pages to act and feel as single page applications.

The frameworks are:

• Turbo - a successor to TurboLinks but with expanded functionality through the addition of turbo frames and turbo...</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/12</id>
    <published>2019-01-29T12:00:00Z</published>
    <updated>2024-03-22T14:15:00Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/mruby-crash-course-nBLLyxmHhURS"/>
    <title>MRuby crash course</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;The talk introduces MRuby and explains the motivation behind the project by
contrasting it with the traditional approach in embedded devices and it&amp;#39;s
applicability to real-world projects.&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">The talk introduces MRuby and explains the motivation behind the project by contrasting it with the traditional approach in embedded devices and it's applicability to real-world projects.</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/1</id>
    <published>2018-10-06T15:00:00Z</published>
    <updated>2024-03-22T14:21:58Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/do-you-really-need-websockets-huEURtr2Oclt"/>
    <title>Do you really need WebSockets?</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;People mostly use WebSockets whenever they need a real-time web component. Turns
out WebSockets aren&amp;#39;t the best solution for everything.&lt;/p&gt;
&lt;p&gt;Over the years I&amp;#39;ve had this conversation a couple of times.&lt;/p&gt;
&lt;p&gt;People use WebSockets without knowing what they are, why they use them or what
alternatives exist.&lt;/p&gt;
&lt;p&gt;Existing alternatives provide advantages such as universal compatibility, simple
implementations and low upkeep.&lt;/p&gt;
&lt;p&gt;This talk will give you an overview of how WebSockets and the alternatives work,
and when you should use one or the other.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://stanko.io/do-you-really-need-websockets-343aed40aa9b"&gt;Article&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">People mostly use WebSockets whenever they need a real-time web component. Turns out WebSockets aren't the best solution for everything.

Over the years I've had this conversation a couple of times.

People use WebSockets without knowing what they are, why they use them or what alternatives...</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/11</id>
    <published>2018-05-03T12:00:00Z</published>
    <updated>2024-03-22T14:12:43Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/http2-rb-TwXtcnCN2yxI"/>
    <title>HTTP2.rb</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;Why aren&amp;#39;t all Rack apps served over HTTP 2 by now? What exactly is HTTP 2 and
is it better than HTTP 1.1? How can you use it in Ruby?&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">Why aren't all Rack apps served over HTTP 2 by now? What exactly is HTTP 2 and is it better than HTTP 1.1? How can you use it in Ruby?</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/10</id>
    <published>2018-02-27T12:00:00Z</published>
    <updated>2024-03-22T14:22:19Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/rabbitmq-is-more-than-a-sidekiq-replacement-9sL5VI530eMo"/>
    <title>RabbitMQ is more than a Sidekiq replacement!</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;We are used to Sidekiq being the defacto norm for a queue service in the Ruby
ecosystem. If you replace Sidekiq and Redis with RabbitMQ you may find yourself
with a few less problems, and more tools to scale your app.&lt;/p&gt;
&lt;p&gt;This talk will go into problems with using Sidekiq and Redis as a queue service,
migrating to RabbitMQ, and using RabbitMQ’s features to scale your Ruby apps a
bit easier.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/rubyzg/slides/blob/master/2018-02-28/rabbitmq_is_more_than_a_sidekiq_replacement.pdf"&gt;Slides&lt;/a&gt;
&lt;a href="https://stanko.io/rabbitmq-is-more-than-a-sidekiq-replacement-b730d8176fb"&gt;Article&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">We are used to Sidekiq being the defacto norm for a queue service in the Ruby ecosystem. If you replace Sidekiq and Redis with RabbitMQ you may find yourself with a few less problems, and more tools to scale your app.

This talk will go into problems with using Sidekiq and Redis as a queue...</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/9</id>
    <published>2017-11-28T12:00:00Z</published>
    <updated>2024-03-22T14:09:27Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/helix-Bb3vvarckPXR"/>
    <title>Helix</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;Helix is a Rust library for writing Ruby extension. With it you can write hassle
free extensions with confidence that they won&amp;#39;t fail.&lt;/p&gt;
&lt;p&gt;This talk will introduce you to Ruby extensions, Rust and Helix.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/rubyzg/slides/blob/master/2017-11-28/helix.pdf"&gt;Slides&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">Helix is a Rust library for writing Ruby extension. With it you can write hassle free extensions with confidence that they won't fail.

This talk will introduce you to Ruby extensions, Rust and Helix.

Slides</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/2</id>
    <published>2017-10-06T16:55:00Z</published>
    <updated>2023-10-29T13:07:32Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/developing-a-safer-web-with-rust-DfhyvPw3yruT"/>
    <title>Developing a Safer Web with Rust</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;Developing web services with Rust. Using Rust&amp;#39;s built in safety and open-source
frameworks to make fast and fault-tolerant web applications.&lt;/p&gt;
&lt;p&gt;We all want to write high-performing, scalable, safe code with as few bugs as
possible. But with threading, data races, SQL injection, out-of-bounds access
and segmentation faults this can prove to be a hassle.&lt;/p&gt;
&lt;p&gt;Rust solves most of those issues out-of-the-box, but with projects such as
Rocket and Diesel those guarantees can be extended to the level of a framework.&lt;/p&gt;
&lt;p&gt;Providing an easy and fast way to write high-performing fault-tolerant web
applications.&lt;/p&gt;
&lt;p&gt;Perhaps your next web app should be written in Rust?&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">Developing web services with Rust. Using Rust's built in safety and open-source frameworks to make fast and fault-tolerant web applications.

We all want to write high-performing, scalable, safe code with as few bugs as possible. But with threading, data races, SQL injection, out-of-bounds access...</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/15</id>
    <published>2017-05-17T12:00:00Z</published>
    <updated>2024-03-22T14:26:22Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/developing-a-faster-and-safer-web-with-rust-aX7rlu4J81Cv"/>
    <title>Developing a faster and safer web with Rust</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;Rust provides a safe way to do concurrent programming without the speed penalty.
It&amp;#39;s finally web-ready. This talk will guide you through creating a web
application in Rust. Through that process, available libraries will be outlined
and compared to their counterparts in other ecosystems.&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">Rust provides a safe way to do concurrent programming without the speed penalty. It's finally web-ready. This talk will guide you through creating a web application in Rust. Through that process, available libraries will be outlined and compared to their counterparts in other ecosystems.</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/8</id>
    <published>2017-03-28T12:00:00Z</published>
    <updated>2024-03-22T14:07:46Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/graphql-oKdA0gYkLdZq"/>
    <title>GraphQL</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;GraphQL is a better way to write APIs. It is auto-documenting, simple to
understand, flexible yet powerful. Lets explore how we can build APIs using its
Ruby driver and solve common problems that we face when using techniques such as
REST, JSON::API or HAL.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/rubyzg/slides/blob/master/2017-03-28/graphql.pdf"&gt;Slides&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">GraphQL is a better way to write APIs. It is auto-documenting, simple to understand, flexible yet powerful. Lets explore how we can build APIs using its Ruby driver and solve common problems that we face when using techniques such as REST, JSON::API or HAL.

Slides</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/7</id>
    <published>2016-10-25T12:00:00Z</published>
    <updated>2024-03-22T14:06:11Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/steganography-2qujhKxhy9ow"/>
    <title>Steganography</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;Sick and tired of those pesky watermarks ruining photos? Or perhaps you have
something to hide, but don’t want people to suspect something? Using Ruby and
steganography it’s possible to hide messages in plain sight. Though it seems
useless it’s applications are limitless.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/rubyzg/slides/blob/master/2016-10-25/steganography.pdf"&gt;Slides&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">Sick and tired of those pesky watermarks ruining photos? Or perhaps you have something to hide, but don’t want people to suspect something? Using Ruby and steganography it’s possible to hide messages in plain sight. Though it seems useless it’s applications are limitless.

Slides</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/3</id>
    <published>2016-09-28T12:00:00Z</published>
    <updated>2023-10-29T13:12:52Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/stubs-mocks-spies-MdyHowlg0PqN"/>
    <title>Stubs, Mocks &amp; Spies</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;1000 tests running for hours on continuous integration services should be a
thing of the past.&lt;/p&gt;
&lt;p&gt;Don&amp;#39;t lose time waiting for your tests.&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">1000 tests running for hours on continuous integration services should be a thing of the past.

Don't lose time waiting for your tests.</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/6</id>
    <published>2016-04-28T12:00:00Z</published>
    <updated>2024-03-22T14:04:28Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/stubs-mocks-spies-7GHQbNHP6vdJ"/>
    <title>Stubs, Mocks &amp; Spies</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;What are stubs, mocks, spies and fakes?&lt;/p&gt;
&lt;p&gt;How can they improve my tests?&lt;/p&gt;
&lt;p&gt;Those are two questions that I want to answer with this talk.&lt;/p&gt;
&lt;p&gt;Stubs, mocks and spies are essential tools of every testing library.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/rubyzg/slides/blob/master/2016-04-28/stubs_mocks_spies.pdf"&gt;Slides&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">What are stubs, mocks, spies and fakes?

How can they improve my tests?

Those are two questions that I want to answer with this talk.

Stubs, mocks and spies are essential tools of every testing library.

Slides</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/5</id>
    <published>2016-02-25T12:00:00Z</published>
    <updated>2024-03-22T14:02:38Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/docker-for-rubyists-dEUwfw2w6EYv"/>
    <title>Docker for Rubyists</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;Use Docker to solve common development and deployment problems without making
too many changes to your workflow and development environment.&lt;/p&gt;
&lt;p&gt;The goal of this presentation is to introduce you to Docker, present it as a
development tool and to explain the strengths and weaknesses of this development
approach.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/rubyzg/slides/blob/master/2016-02-25/docker_for_ruby_devs.pdf"&gt;Slides&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">Use Docker to solve common development and deployment problems without making too many changes to your workflow and development environment.

The goal of this presentation is to introduce you to Docker, present it as a development tool and to explain the strengths and weaknesses of this...</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
  <entry>
    <id>tag:stanko.io,2005:Talk/4</id>
    <published>2015-03-31T12:00:00Z</published>
    <updated>2024-03-22T14:02:45Z</updated>
    <link rel="alternate" type="text/html" href="https://stanko.io/talks/ruby-extensions-Uma3TYttk1tT"/>
    <title>Ruby Extensions</title>
    <content type="html">&lt;div class="lexxy-content"&gt;
  &lt;p&gt;How to achieve better performance by offloading computationally heavy tasks to a
&amp;quot;faster&amp;quot; language, but still keep a Ruby-like interface&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/rubyzg/slides/blob/master/2015-03-31/ruby_extensions.pdf"&gt;Slides&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;
</content>
    <summary type="html">How to achieve better performance by offloading computationally heavy tasks to a "faster" language, but still keep a Ruby-like interface

Slides</summary>
    <author>
      <name>Stanko Krtalic Rusendic</name>
      <email>hey@stanko.io</email>
    </author>
  </entry>
</feed>
