← Back to context Comment by monocasa 2 hours ago It's his conference he made because he was banned from railsconf. 2 comments monocasa Reply tnolet 2 hours ago aha, that explains the podium. Thanks for enlightening me. Kudos to Railsconf. pushcx 2 minutes ago No kudos earned. They didn't ban him, they just didn't invite him to give a keynote. Then Ruby Central put him back on stage for a RailsConf keynote q&a. It was the snowball that started rolling an ongoing avalanche of secondary crises.
tnolet 2 hours ago aha, that explains the podium. Thanks for enlightening me. Kudos to Railsconf. pushcx 2 minutes ago No kudos earned. They didn't ban him, they just didn't invite him to give a keynote. Then Ruby Central put him back on stage for a RailsConf keynote q&a. It was the snowball that started rolling an ongoing avalanche of secondary crises.
pushcx 2 minutes ago No kudos earned. They didn't ban him, they just didn't invite him to give a keynote. Then Ruby Central put him back on stage for a RailsConf keynote q&a. It was the snowball that started rolling an ongoing avalanche of secondary crises.
aha, that explains the podium. Thanks for enlightening me. Kudos to Railsconf.
No kudos earned. They didn't ban him, they just didn't invite him to give a keynote. Then Ruby Central put him back on stage for a RailsConf keynote q&a. It was the snowball that started rolling an ongoing avalanche of secondary crises.