In the end, I hope it builds the curiosity of the uninitiated to discover this craft further. Additionally, I am aware that some unit tests highlighted are not best practice. I would be happy to answer any questions in the comments below. This post assumes an understanding of unit testing. Finally, we will conclude with high level takeaways such as learnings, build speed and file size measurements. This will include what was observed, what was used and not used in the language. ![]() Then, we will discuss the mechanical parts of unit test conversion. The first part will discuss the process behind our journey to Kotlin. If the information that follows helps just one engineer to better understand usage, it has served its purpose. It is to voice internal learnings through a story about how we are adopting Kotlin. It is also not a typically sized Medium post. This is not a typical explanation on applying Kotlin. We will take a drive through A-118 (Saint Petersburg Ring Road) during the reading. Kotlin Island and the causeways that connect.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |