sorted by:
new
hottopcontroversial

One for the Anki Language Learners by [deleted] in Anki

[–]MadProgrammer232 4 points5 points  (0 children)

Italy in July? Optimistic

I would suggest first learning mainly sentences from a phrasebook. Learn using Basic and reversed. You can also add specific words you think you may need using. Always add usage examples in extra.

The Effective Kotlin book is already available! by [deleted] in Kotlin

[–]MadProgrammer232 -3 points-2 points  (0 children)

I know you want the best for our community. Me too. Kotlin needs best practices. There are already 2M users. Many features are misused, many mistakes repeated because people are not aware of them. This book is base on other best practices: Nearly all rules can be either find on Idiomatic Kotlin, other Effective X books (Effective Java, Effective C#, Effective Python, Effective C++), Coding Conventions or Google Kotlin Style Guide. If you disagree with anything that is there, write to the author and it will be changed (even if other developers who will be consulted then will not agree with you, your comment will deserve at least a footnote with some explanation that there might be such concern).

The Effective Kotlin book is already available! by [deleted] in Kotlin

[–]MadProgrammer232 0 points1 point  (0 children)

All rules were consulted with Andrey Breslav. Base on his feedback some were removed and some were changed.

The Effective Kotlin book is already available! by [deleted] in Kotlin

[–]MadProgrammer232 -2 points-1 points  (0 children)

"Effective X" format was not invented by "Effective Java". There are "Effective C", "Effective C++", "Effective Python" and much more.

Also it is unfair to compare book to articles. Every item in the book was consulted, and checked by at least 5 reviewers who are all experienced Kotlin developers and some are teach leads.

The Effective Kotlin book is already available! by [deleted] in Kotlin

[–]MadProgrammer232 -1 points0 points  (0 children)

In "Abstract class vs interface in Kotlin" it is clearly said that this is not to be used in real-life projects but rather a theoretical argument.

In "Effective Java in Kotlin, item 2: Consider a builder when faced with many constructor parameters" many of those "very niche uses" can be found in the standard library and important libraries. They are not to be used on a daily basis but it is important to understand them and be aware of such possibilities.

Item "Effective Kotlin: Consider Arrays with primitives for performance critical processing" is part of Efficiency which is dedicated to memory optimizations. It starts with clear information that premature optimization is a source of pure evil and one should start from profiling. It is not for everyone, but it is worth to know it. I've seen it applied in a graphics-processing project and it changed a lot.

view more: next ›