Sorry about your bad experience.
While it’s certainly possible that those folks were rude to you, it’s also entirely possible (perhaps likely) that wasn’t their intent. Maybe they had somewhere to be. Maybe someone felt ill. Maybe they are intensely introverted or very shy. Maybe they didn’t recognize you. There are hundreds…
We don’t explicitly follow agile, but we do all of these things. We just don’t need recurring meetings to accomplish them. We can defer to asynchronous written formats most of the time, or schedule standalone meetings as needed.
Retrospectives and other reviews can be scheduled when needed. How do you know exactly when the recurrence should be or that you even need a meeting? Forcing a retro every x weeks may not even align with a release.
Stand ups are definitely unnecessary. Those are a major waste of time and can be accomplished in written form /…
One thing I’d ask is, perhaps, why are your schedules so busy? Maybe too many meetings in the first place?
I’d also challenge the assumption that a team should routinely block off a piece of their week for meetings. I think a newly scheduled, one-time meeting that has a specific need based on real events is better than one…
When you know that language X does something better than language Y, it’s only natural to point it out.
Agreed, if it’s done constructively. Hate whatever you want. Point out flaws. Point out benefits. But do it in a way that leads to constructive discussion and teaches instead of purely ripping apart someone else’s work.
Kotlin is equally strongly typed as Java — it compiles down to 100% Java byte code. I don’t see anything specific to OO that’s unique to Java that Kotlin doesn’t fully, properly support.
Why the attitude that for something to do well, something else must fail?
Many people have found happiness in working with Kotlin. I’m sure many people have found happiness with C# too. This doesn’t have to be mutually exclusive.