← Graph

Let's Find a Meaning Problem to Solve

talk 6 connections

wroclove.rb 2026 lightning talk arguing that open-source advice overemphasizes how to contribute and under-discusses what to build. Suggests finding important-but-not-urgent problems on the Eisenhower matrix — often neglected, generic enough to transcend a single company, and where the existing solutions are unsatisfying. Uses the speaker's own EuRuKo talk (an anonymized-database masking gem that now ranks in the top 60% of daily RubyGems downloads) as an example: important because database incidents are damaging, generic enough to apply broadly, and better than existing procedural approaches. Second path: find your own real-world problems — illustrates with a Japanese friend who released ~200 gems and accumulated 2000+ stars from problems he actually hit (SQL tuning, KMS-based encryption, batch-process graphs). Third: follow your passion — Matz built Ruby because he loved programming languages; another speaker fell in love with Ruby after being a Java developer; Linus Torvalds made Linux to understand the hardware. Speaker mentions a fun personal Crystal project and invites collaboration.

type
lightning-talk
talk Let's Find a Meaning Problem to Solve
about
Matz person
Cited as follow-your-passion example: built Ruby because he loved programming languages
talk Let's Find a Meaning Problem to Solve
about
Cited as follow-your-passion example: built Linux to understand the hardware
talk Let's Find a Meaning Problem to Solve
about
Ruby tool
Refers to another famous speaker who 'fell in love with Ruby' after being a Java developer
talk Let's Find a Meaning Problem to Solve
about
Crystal tool
Speaker mentions his fun personal project in Crystal and invites collaboration
from_talk
Let's Find a Meaning Problem to Solve talk
Core heuristic of the talk
talk Let's Find a Meaning Problem to Solve
presented_at
Lightning talk at wroclove.rb 2026

Provenance

Created in
wroclove.rb 2026 Lightning Talks 2026-04-22 08:41