4 ms·
> Annotation-based programming might seem cool now, but wait a few years. I even have this experience on my own projects and with much shorter span than a year
by 75dvtwin 8y ago
> Annotation-based programming might seem cool now, but wait a few years.
I even have this experience on my own projects and with much shorter span than a year.
When I go back to a code base I worked just 3-4 month ago -- I have very hard time following Dagger injections.
Braking one of the Dagger providers (I use dagger 2) creates 10s and 10s of compilation errors.
So I have been slowly removing dagger from my code bases.
As I just cannot follow it, I do not know it well enough either.
I stopped using Lombok for same reason, although I found Lombok is much more intuitive.
I thought about going to Kotlin, but it was just too much of cognitive overload (in this particular instance both for backend and android UI).
Instead, I am finding the use of rxjava and friends a lot more intuitive and helpful for the type of things I need help with (interconnecting components on different threads, with different lifecycle and data structure semantics, with lots of asynchronous behavior options).
And the same rx-<> library is available to many other languages, therefore, the skill I am building up is sort of 'cross-language'.
- woolvalley 8y agoThats fairly funny, since I find Rx to be the very complicated thing if used extensively in a project and hard to reason about memory usage and other things when trying to dig into problems. On top of that it creates huge ass stack traces that makes finding your code difficult unless your debugger can filter out specific packages: https://github.com/ReactiveX/RxJava/issues/4834 https://github.com/ReactiveX/RxJava/issues/4834 Kotlin on the other hand is a fairly clear language!