2024

• Rails application namespace
• How to get burned by 16 years old hack in 2024

2023

• Repository implementation on ActiveRecord
• Temporary databases for development
• Six ways to prevent a monkey-patch drift from the original code

2022

• Verifying Content-Security Policy with Selenium and Cuprite

2021

• Semantic blind spot in Ruby case statement
• Rails console trick I had no idea about
• How to balance the public APIs of an open-source library — practical examples from RailsEventStore
• Importing external posts into Nanoc
• Zeitwerk-based autoload and workarounds for single-file-many-classes problem
• Explaining Rack — desugaring Rack::Builder DSL
• Rack apps mounted in Rails — how to protect access to them?
• How to speed up Netlify build, twice
• Write once, publish in many places, keep SEO happy
• 3 tips to tune your VCR in tests
• Testing cursor-based pagination with Webmock

2020

• Practical use of Ruby PStore
• Managing Rails Event Store Subscriptions — How To
• How to migrate large database tables without a headache

2018

• Modeling passing time with events
• Serverless Slack bot on Lambda with Ruby (and what’s the less pleasant part about it)
• What I've learnt at RESCON
• Rewriting deprecated APIs with parser gem
• Process Managers revisited

2017

• How to get an audit log with RailsEventStore today
• Event Sourcing is a transferable skill
• Event-sourcing whole app — opinions
• One simple trick to make Event Sourcing click
• Rails components — neither engines nor gems
• Why we follow the Rails repo structure in Rails Event Store
• Dogfooding Process Manager

2014

• Microservices - 72 resources

2013

• Implementing worker threads in Rails

2012

• Packaging for dummies (2)
• Packaging for dummies (1)
• Optimize your SSH experience