You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All new classes should be written in Kotlin. We should enforce this on all future PRs as well as make an effort to rewrite some of the legacy classes in Kotlin as we're working in them. Thanks team!
Sent from my iPhone
The text was updated successfully, but these errors were encountered:
I think it might be safer to rewrite the code entirely in XML and use XSLT to transform it into Java, Kotlin, Scala, and Groovy. In this way there will be no duplication and staffing will be much easier going forward. Everyone can edit some XML, right? I also had a talk with our HR partner, and they agree that replacing "Java" with "XML" on the list of required skills lowers the wages of future FTEs by as much as 25%!
Our CTO already signed off on the change. I'll draft a memo to let the developers know of their "new positions" and find a clever way to spin "salary decrease" as a positive thing.
All new classes should be written in Kotlin. We should enforce this on all future PRs as well as make an effort to rewrite some of the legacy classes in Kotlin as we're working in them. Thanks team!
Sent from my iPhone
The text was updated successfully, but these errors were encountered: