Check it my article about observability: it’s a good candidate for #KotlinServerSide 🎉.

RT @funcode_mag: A small part of the fun code() Magazine team at @kotlinconf! 🎉.An unofficial magazine for @kotlin developers, from the Kot….

I just read this really nice article about ports & adopters article, highly recommend for people who want a deep dive into the topic!.

I’m excited to share my latest article on adding #observability to your service is on this week @KotlinWeekly! Check it out! 😊 #Kotlin #Development #Tech #Article

It was a pleasure to talk at #KUGBerlin about code smells ❤️.

7/ 📚 Want to learn more about Kotlin Code Smell? Check out the full article at .

6/ 🏁 Conclusion: Don't be too clever for your own good. Smart developers write clean code. Clear beats clever every time!.

5/ 📌 Exceptions where cleverness might be okay:. Optimized code for low-level operations.1-liner code functions.

4/ 🧪 Examples of too-clever code include:. Optimized loops that sacrifice readability.

3/ ✅ Solutions to avoid these problems:. - Refactor the code.- Use better names for variables and functions.

2/ 🚫 Problems with being too clever in code:. - Readability issues.- Harder to maintain.- Code quality suffers.- Premature optimization.

1/ 🧠 Being too clever with your code can backfire! Clean code requires readability and simplicity. Here's a thread on Kotlin Code Smell - Too Clever For Your Own Good.

Design Patterns - Singleton.{ by @yonatan_karp } from @hashnode

RT @ramtop: Finally the printed version is ready!.Waiting for getting a physical one!.

7/ 📚 Want to learn more about Kotlin code smells and how to avoid them?. Read my full article on the blog and level up your Kotlin game! 🚀.

6/ 🏁 Conclusion:. Don't let strings take over your code! Prioritize actual objects and establish clear protocols to differentiate them from strings.

5/ 📝 Sample Code:. Check out the full article for examples of wrong and right code snippets to help you avoid string abuse in your Kotlin projects.

4/ 🌟 Examples: Serializers and Parsers. These are just two examples of how you can replace strings with more appropriate abstractions.

3/ ✅ Solution 2: Replace strings with data structures that handle object relations. This will allow you to better manage your code and avoid bijection problems between real objects and strings.

2/ ✅ Solution 1: Utilize objects instead of strings. By using actual objects, you can simplify your code and make it more readable.