Skip to content

Commit f924628

Browse files
authored
Merge pull request #17 from rubytaiwan/remove-yatish-from-schedule
Remove Yatish from schedule
2 parents 81d8cc0 + 412718b commit f924628

1 file changed

Lines changed: 11 additions & 41 deletions

File tree

_data/schedule.yml

Lines changed: 11 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -312,8 +312,8 @@
312312
- session_id: b9
313313
type: break
314314
start_time: "10:30"
315-
end_time: "10:35"
316-
duration: "0:05"
315+
end_time: "10:40"
316+
duration: "0:15"
317317
day: 2
318318
track: TR209
319319
lang:
@@ -325,8 +325,8 @@
325325
abstract:
326326
- session_id: s11
327327
type: session
328-
start_time: "10:35"
329-
end_time: "11:05"
328+
start_time: "10:40"
329+
end_time: "11:10"
330330
duration: "0:30"
331331
day: 2
332332
track: TR209
@@ -341,9 +341,9 @@
341341
abstract: "Ruby is beloved for its developer experience, but it's not always known for raw performance or scalability. With Falcon and Async, we're changing that.\n\nIn this talk, I'll walk you through building modern, concurrent Ruby web applications using Falcon — a high-performance async web server — and Async, the foundation for non-blocking I/O in Ruby. We'll cover the full lifecycle of a production-ready app:\n\n- **Building**: Writing non-blocking, fiber-based web apps using Async and Protocol::HTTP.\n- **Deploying**: Running Falcon in production environments, from containers to the cloud.\n- **Monitoring**: Observability strategies for async systems — logging, metrics, and tracing.\n\nWhether you're serving APIs, streaming data, or scaling real-time features, this talk will equip you with practical tools and patterns to confidently run async Ruby apps in production."
342342
- session_id: b10
343343
type: break
344-
start_time: "11:05"
345-
end_time: "11:10"
346-
duration: "0:05"
344+
start_time: "11:10"
345+
end_time: "11:20"
346+
duration: "0:10"
347347
day: 2
348348
track: TR209
349349
lang:
@@ -355,8 +355,8 @@
355355
abstract:
356356
- session_id: s12
357357
type: session
358-
start_time: "11:10"
359-
end_time: "11:40"
358+
start_time: "11:20"
359+
end_time: "11:50"
360360
duration: "0:30"
361361
day: 2
362362
track: TR209
@@ -369,41 +369,11 @@
369369
speaker_bio: "NexHealth.com : Backend Engineer"
370370
subject: "Loosing Seat in Concurrency: A tale of Transactions and Locks"
371371
abstract: "Let's say there is one seat left in the aircraft. And two people want to buy a ticket. And they submit a form at the almost same time. Who gets the seat?\nIn this talk I'll touch classic database concurrency problems, transaction isolation and anomalies, pessimistic, optimistic and advisory locking and patterns to use it."
372-
- session_id: b11
373-
type: break
374-
start_time: "11:40"
375-
end_time: "11:45"
376-
duration: "0:05"
377-
day: 2
378-
track: TR209
379-
lang:
380-
speaker_id:
381-
speaker_avatar:
382-
speaker_name:
383-
speaker_bio:
384-
subject: Break
385-
abstract:
386-
- session_id: s13
387-
type: session
388-
start_time: "11:45"
389-
end_time: "12:15"
390-
duration: "0:30"
391-
day: 2
392-
track: TR209
393-
lang: EN
394-
speaker_id: KXGSTL
395-
speaker_avatar: yatish.jpg
396-
speaker_name: Yatish Mehta
397-
speaker_github: yatish27
398-
speaker_x: yatish_me
399-
speaker_bio: Staff Software Engineer, Asana
400-
subject: No "Pundit" Intended
401-
abstract: Has your has_access? method morphed from a straightforward guard into a tangled mess? While most Rails applications rely on Pundit, truly complex systems demand a more robust approach. In this talk, we'll dive into implementing a tuple-based authorization model—an approach leveraged by Google and other large-scale applications—right within Rails. Learn how to tackle intricate permission scenarios without migrating to an external authorization system.
402372
- session_id: b12
403373
type: break
404-
start_time: "12:15"
374+
start_time: "11:50"
405375
end_time: "13:30"
406-
duration: "1:15"
376+
duration: "1:50"
407377
day: 2
408378
track: TR209
409379
lang:

0 commit comments

Comments
 (0)