Tuesday, August 11, 2026

XO Ruby joins RubyConf/RailsWorld as Another Exclusive Discriminatory Unexcellent Conference

So, I got contacted by the organizer of the XO Ruby conference (aka Travelling Ruby), Pascal Laliberté, on meetup.com because I organize the Montreal.rb Ruby Meetup and am a Montreal-based Expert Ruby Software Engineer. He said XO Ruby is coming to Montreal and asked me for help with it. We end up meeting in a video conference call. 

To help out, I indicated that I asked my company to consider sponsoring the conference. Furthermore, I volunteered to give a talk as a Montreal-local Ruby Expert (given I have won 2 awards by Matz and have spoken 4 times at RubyConf and 2 times at RailsConf, plus 2 times this year at Ruby conferences in Europe, including this talk that I shared with him); I offered to ask my company's former CTO (who is still with us in a different position) to give a "Founder" topic talk (one of the topics of the conference) about how to be a Tech Founder for a Ruby on Rails project (our previous Montreal-based Fintech company is a huge success story as we got bought by a larger Silicon Valley Fintech 1.5 years ago that is a leader in the Credit Union AI/Agent Conversational Software space); and I offered to recommend other potential Ruby speakers from Montreal. 

After everything I volunteered to help with, Pascal strangely seemed to push back against me giving a Ruby talk at the Montreal-based XO Ruby even though there are empty slots left and I am literally one of the biggest representers of Ruby in the Montreal Tech community today (not many Ruby Software Engineers from Montreal present at RubyConf like I have in 2022/2023/2024, and no one from Montreal as far as I know has won awards by Matz, the creator of Ruby). I've also put in many many hours and days into keeping the Montreal.rb Ruby Meetup going, including giving extra presentations myself whenever needed, and that's in addition to the many many hours and days I've put into Ruby Open-Source Projects. Honestly, if an interviewee at a job interview I am conducting had reacted with that sort of apathy after hearing my accomplishments, they'd be cut immediately from the interview process due to being apathetic instead of passionate, and due to not appreciating excellence, as only unexcellent people don't appreciate excellence. Truly excellent people always appreciate excellence and excellent accomplishments, while maintaining an attitude of curiosity about them.

I asked him how many talk slots are left in the conference. He said there are about 9 slots and about 4-5 are left, including empty slots for the "Open-Source Projects" topic. Then, he started trying to explain that he wanted a very technical Ruby talk (it's a weird note given Glimmer DSL for Web is one of the most technically interesting and innovative Ruby projects ever with its ultralight, expressive, and minimalistic DSLs). So, I told him I've given talks at many Ruby/Rails conferences and meetups on a variety of topics, including Domain Driven Design, Design Patterns, Object Oriented Design, Desktop Development, Frontend Development, and DSL Engine Meta-Programming, plus I have literally won an award from Matz, the creator of Ruby, last year for my Open-Source Project, Glimmer DSL for Web (in addition to winning another award a few years ago for Glimmer DSL for LibUI), so I can easily give a strong Ruby technical presentation. The weirdest and creepiest thing is Pascal's face was so apathetic when I was recounting all my Ruby accomplishments as if they don't matter. That's not the reaction of a strong ethical Software Engineer who cares about the fact that past Ruby accomplishments have benefited many customers and continue to benefit customers directly or indirectly today. 

Then, Pascal said he could not guarantee a slot for me despite having empty slots, believe it or not, without providing any valid reasons! I told him given that I am 100% qualified to give a talk at the conference, this is discrimination! After all, if I wasn't qualified, or even had some competition, I could understand not being guaranteed a slot. But, I am the only one in the Montreal community who has won awards from Matz, my new innovative open-source project has no competition, and no Software Engineers in Montreal have represented Ruby as much as I have in recent years through continued effort in fostering the local Ruby community with running the Montreal.rb Ruby Meetup. Meaning, this is 100% discrimination. 

To give a point of comparison, I was literally hired instantly at my current company a number of years ago (when we were still a small startup before acquisition) because my boss appreciated all my Ruby accomplishments and knew that I had a large enough body of work in the Ruby community (many RubyConf/RailsConf talks and Ruby open-source projects) that demonstrated my Ruby skills beyond the shadow of a doubt and warranted instant acceptance of me. My boss back then who was the CTO at the time is a Super-Duper Ultra Strong Software Engineer/Architect/CTO by the way, so he knew what he was doing. 

Any normal competent ethical strong Software Engineer would have been absolutely excited to have me talk at their Ruby conference (like the organizers of wroclove.rb and RubyConf Austria), especially that I have won an award from Matz himself, the creator of Ruby. They would have been 100% curious to learn what the award-winning project is all about and would have wanted me to share that knowledge with others in the Ruby community for the benefit of customers (not for selfish reasons). 

I responded to Pascal further by telling him that his conference practices discrimination and is an unexcellent garbage conference that is way below my standards for how a Ruby conference should be (it should be non-discriminatory and appreciative of excellence that wins awards from the creator of Ruby).  So, I don't want to participate in it anymore nor help it. The fact that the conference doesn't immediately accept a talk by someone who won awards from the creator of the programming language that is the reason for the conference existing means it is a trash conference. It can't possibly be sharing top-level Ruby excellent knowledge, yet lower-level mediocre knowledge. I told him I was ending the video conference call because discrimination is not acceptable anywhere in Canada. It's funny how this creepy unethical guy was trying to act as if he's "more important" than me when in fact he probably doesn't have half my accomplishments. This reminds me of this blog post about entitled people in the Ruby community, which applies to him as well.

The crazy thing is he tried to interject and say things about "my behavior" towards the end of the video call when in fact his behavior was already bad through discrimination and lack of appreciation for excellence, so if his behavior is already bad, he is in no position to judge anyone else's "behavior"! My behavior is exemplary in the Montreal Ruby community over many years.

One other thing worthy of note that relates to discrimination is that at one point, Pascal tried to focus the conversation on the pronunciation of my last name, which felt uncomfortable and felt as if he was trying to pigeon hole me into whatever "country of origin" my heritage belongs to instead of just treating me as a 100% equal Canadian (as I am a 100% Canadian after all). I have just completed my employer's yearly training for workplace prevention of abuse, harassment, and discrimination. And, such behavior came up in the training as "discrimination based on the country of origin". When he asked about how my last name is pronounced, I told him my last name is just pronounced like it's written in English, with the end being silent, similarly to the pronunciation of the word "melee" (meaning a skirmish). To be honest, over the years, I have received that sort of discrimination from a number of people in Canada. It's disappointing that some people in my country, Canada, discriminate against others based on their country of origin, sometimes in very subtle ways with plausible deniability (this was blogged about as covert discrimination). I had less experience of that discrimination when I lived in the USA in the past during the first 10 years of my career. It's ironic that the international stereotype of Canadians is that they are nice people, but in actuality, some of them (not all) apply "niceness" with a double standard (which is not nice), treating people in their in-group nicely and treating others in their out-group not nicely at all. That's something I have experienced by some of the people who work for Shopify in the past (this blog post by Paul Battley and this blog post by André Arko confirm my experience of Shopify being mean). Fortunately, I work with very nice people at my company's Montreal branch and I have a very nice French Canadian girlfriend too.

Another thing worthy of note is that this XO Ruby conference is associated with Jim Remsik who runs Falgrant. In a past RubyConf that I presented at, at which I met Jim Remsik, I literally saw swag/stickers by Flagrant that included the F word, which were very unprofessional and disrespectful. Professional Software Engineers who don't make it a habit to drop F bombs at work would not use that sort of language in business marketing material as that immediately reduces a company like Flagrant into a trash company that spreads unethical trash with every interaction they have with others. I removed Jim Remsik from my LinkedIn in the past after I noticed that just as I removed Pascal Laliberté from my LinkedIn today after our video call.

I have mentioned this before; from the perspective of discriminators who have an unconscious or conscious in-group/out-group bias, it doesn't matter if someone from the out-group has launched rockets to the moon successfully with excellent effort, as they would still get treated as if they are unequal unimportant people and as if their accomplishments don't matter (in spite of having practically benefited many customers directly or indirectly with their accomplishments). 

In conclusion, to avoid enabling discrimination and unexcellence in the Ruby community, avoid attending, sponsoring, and presenting at XO Ruby. Also, know that it is a mediocre garbage conference that is way below the high quality standards of Ruby Experts like me for excellence and ethics. 

P.S. Of course, as with my other blog posts, to prove that I'm on the right side of things, I acknowledge that nobody is perfect and everyone makes mistakes. Meaning, I am always open to the idea of forgiving people if they redeem themselves. So, if Pascal was to apologize about his discrimination/lack-of-appreciation-for-excellence and allow the most active Expert Ruby Software Engineer in Montreal to present at a Montreal Ruby conference, I'd be happy to retract this blog post. Otherwise, if I am wrong about something and it was kindly, patiently, and respectfully explained to me with genuine loving intentions, I'd be happy to reverse my position too. 

Thursday, July 30, 2026

Ruby Memes 2026-07-30: One Bad Monkey Spoils The Bunch

One Bad Monkey Spoils The Bunch! 🤣🤣🤣🤣🤣


This Ruby meme is a variation on the common expression "One Bad Apple Spoils The Bunch" that is noting how introducing inferior devs into a Software Engineering team ends up reducing the entire team's skill and intelligence to the least common denominator skill and intelligence of the weakest links, thus corrupting the whole team the same way a bad apple gradually ruins a bunch of healthy apples when placed with them. 

It's so true when it comes to Ruby on Rails development teams that suddenly make the bad decision of hiring a React.js dev for Frontend work one day even though React.js contradicts the Ruby Way and Rails Way and JavaScript is inferior to Ruby!!! The Ruby on Rails Software Engineers that were once smart suddenly become React.js code monkeys and start forgetting all the best practices and principles of Ruby on Rails due to getting used to React.js breaking them with its inferior over-engineered ways. So indeed, one bad monkey ends up spoiling the bunch!

That's why I strive very hard to avoid hiring even one bad dev on my team as I notice immediate degradation in everyone's work quality as soon as one bad dev enters a team, so we keep a tight ship on my team instead.

Tuesday, July 28, 2026

The Embarrassing Ruby/Rails Community Chronicles 2026-07-28

"The Embarrassing Ruby/Rails Subreddit Chronicles" becomes "The Embarrassing Ruby/Rails Community Chronicles" as it expands to cover embarrassing interactions by bad Ruby/Rails devs all across social media and the real world, exposing rudeness, meanness, discrimination, and unexcellence/unintelligence in the Ruby/Rails worldwide community. The goal of course is to call that out to discourage in favor of true Rubyist MINASWAN attitudes and behaviors instead (Matz Is Nice And So We Are Nice).

While going through the yearly Bystander Intervention training for my job, I stumbled upon "Persistent unwanted personal questions" as a form of verbal abuse. 

I have to confess I recently experienced that at a Ruby tech event. A bad Ruby dev (the kind you'd find on the Ruby/Rails subreddits) kept rudely asking me what my salary was after I told him I won awards by Matz (the creator of Ruby) for my open-source projects. Any normal Rubyist would have asked me about my open-source projects instead, just out of normal Software Engineering curiosity to learn better ways of serving customers with Ruby. Instead, he kept prying very hard about my salary and was unwilling to accept the fact that it's rude to ask people he doesn't know for their salary. 

After I gave him multiple examples of how previous companies I worked at had policies against people asking about salaries because knowing the answer could cause envy and create bad relationships, citing a real story of that happening at one of my previous jobs when someone's salary leaked, he pivotted towards asking me if "I felt uncomfortable answering". He kept insisting on me answering that new question instead going forward. The person was already coming across by that point as a very awful rude unprofessional person due to literally attempting to make me feel uncomfortable with incessent questioning.

He sounded like he desperately wanted to "win the conversation/situation" in any way possible (of me having won awards he hasn't won, instead of being humble/happy for me) by trying to make me "look bad" as someone who is "weak" due to being "uncomfortable". That revealed to me what his original intention and ulterior motive was behind asking for my salary: He just wanted to make me "look bad" as I'm sure he was going to tell me my salary was too low no matter what answer I would have provided, as a trap, to insult me and render me "unimportant" even if I've won awards by Matz. As if the awards were about me "being important" or "making more money" as opposed to ensuring I serve customers with the best quality work possible (which is what awards really encourage from the perspective of truly ethical excellent people who don't prioritize greed or pride over customer service). 

What a ridiculous interaction that was! I finally answered him by saying "it's not about me being uncomfortable. It's just a bad practice/etiquette to ask for someone's salary, especially if you don't know them well, and I won't endorse/enable that practice by answering the question even if I were comfortable with answering it."

The dude confessed to me eventually that he doesn't work in Ruby anymore because he lost a political battle at work, so he is now using Python even though Ruby is more effective than Python at building his work application. What a loser! That's exactly the kind of pushover rude loser my team would never hire and would screen for during the interviewing phase of hiring. We don't want devs who lose political battles for what technology decisions are best for serving customers. I have won many many such political battles at my company over the years, and it was because I'm no pushover. A bad dev being unethical/rude goes hand in hand with other bad attributes like being a pushover, which is why we never hire such devs in the first place.

Tuesday, July 14, 2026

RubyConf 2026 Is Not a Safe Environment for Everyone

RubyConf 2026 is not a safe environment for everyone. They have an in-group and an out-group. If you're in the in-group, they will treat you well and accept talk proposals by you even if you don't have top-level skills in Software Engineering. If you're in the out-group, it doesn't matter if you launch rockets to the moon successfully on your own or win the approval of Matz himself, you will be excluded and discriminated against: 

https://andymaleh.blogspot.com/2026/06/rubyconf-has-joined-railsconfrailsworld.html

If that weren't true, then RubyConf's folks would not be afraid to address the issue of feeling discriminated against for the benefit of keeping their reputation clean. Alas, like all discriminators out there, they cower and hide instead of addressing the issue because the discrimination is 100% real. A discriminator usually discriminates because they don't see everyone as equal or because they're frauds and don't have the energy to treat everyone equally, so if discrimination is brought up to them, they won't take it seriously. 

Respectful treatment means to treat someone well and fairly for what they have accomplished and what they offer. I realize I could buy a ticket to the conference, but rejecting a talk by me that won the approval of Matz, the creator of the Ruby programming language that is the reason for the conference existing means I have earned the right to talk about the subject that I won an award from Matz for. Otherwise, I am being robbed and discriminated against. This is no different from how the MLB (Major League Baseball) used to mistreat Afro Americans and relegate them to playing in the Negro league instead of the Major League. Telling someone who can perform at the major league level they are unaccepted as a player there, but could attend if they want is most definitely discrimination 100%. 

By the way, under other circumstances, if I had no project to talk about, I would be 100% OK with attending RubyConf instead of presenting as I would normally want to support other speakers and learn from them. But, in 2026, the issue is if they rejected a talk by someone who won an award from Matz at a near impossible international competition to win, it means they probably rejected a lot of top-quality talks and accepted many subpar mediocre quality talks. I don't want to go to a conference in which I become mediocre by attending mediocre talks. Excellence and unexcellence are infectious. The next thing I know after hanging out with unexcellent speakers at RubyConf 2026 is I'll become unexcellent and subpar like them. This is no different from entire mediocre communities like the React.js comunity and others where the blind are leading the blind into a pit, but everyone is celebrating the popularity of mediocre ideas and technologies (meaning they only perceive themselves as being smart, but objectively, they're all performing suboptimally for customers and don't provide the best smartest work). No thanks!!!

RubyConf 2026 is a cesspool of discirmination and exclusion:

https://andymaleh.blogspot.com/2026/07/reminder-that-rubyconf-2026-is-cesspool.html

One might think that RubyConf's folks are too busy to look into the discrimination claim. But in fact, I contacted them about the perceived discrimination about a month ago. They had all the time of the world to look into the discrimination and lack of appreciation of excellence (an equally serious matter). Also, if they claim to be "excellent", "inclusive" and "diverse", then looking into discrimination and lack of appreciation of excllence would be the top priority of RubyConf, alas they're a mediocre discriminatory conference in 2026 that doesn't put excellence and lack of discrimination at the top of their priorities, just like any dictator at a third world country would act. They're no different. It's a fraud of a conference in 2026.

The fact that it doesn't bother them to have these blog posts published as to want to contact me and settle the issue of discrimination against me proves they are discriminators 100% because discriminators aren't bothered by having discrimination reported to them, but real non-discriminators put ethics and good equal treatment of everyone first above everything else.

I have talked extensively about covert discrimination in the Ruby community in the past, including microdiscrimination / personal discrimination (meaning discrimination against a single person, which makes the discrimination escape protections available for minority groups). Ignoring someone without attempting to resolve things amicably definitely falls under covert discrimination:

Monday, July 13, 2026

Ruby Open-Source Innovation Process Expectation vs Reality

Expectation regarding the Ruby open-source innovation process:

1- I stumble upon a problem at my job in our Ruby application.

2- I build a solution for it in an open-source project (e.g. the ability to write the Frontend with a Ruby Frontend Framework instead of using an inferior JavaScript library like React).

3- I win an award for my open-source project by Matz, the creator of Ruby.

4- I get accepted to present my open-source project at Ruby conferences.

5- Ruby Software Engineers adopt the new highly innovative open-source project, benefiting themselves and their customers greatly. 

Reality regarding the Ruby open-source innovation process:

It doesn't matter how innovative an open-source project that you build is in your free time as a free beneficial contribution for the Ruby community. Even if your open-source project won an award from the creator of Ruby himself at an international tech competition that very few devs won, the project will get rejected from RubyConf due to discrimination and lack of appreciation for excellence from everyone equally. If you're in their discriminatory out-group instead of their in-group and/or you cover a topic that might upset RubyConf folks who aren't 100% for Ruby (e.g. unseating React/JavaScript with Ruby), you are excluded (even if your talk's project has zero competition), to the detriment of the Ruby community at large. 

Learn more:

https://andymaleh.blogspot.com/2026/06/rubyconf-has-joined-railsconfrailsworld.html