Hey Navdeep — Definitely don’t want to be negative but there are some gaping issues with this article. I would personally be very worried about someone finding this content and thinking this is the best practice for creating RxSwift-based applications.
Not using any of the following generally… Since there are Image Literals I don’t find myself needing strongly typed Image References anyways.
And for Swiftgen, I only toyed with it… Still nothing serious.
It’s kinda like Sourcery — I always want to find time for it, but never get around to it / have a strong enough use case for it :)
Did you happen to check out Swiftgen ? I think it’s much nicer and more thorough. R is nice but it doesn’t work for everything, and also that force unwrapping … yikes :P
Awesome list! That Bret Victor video just blows me away every time. Doesn’t matter how many times I’ve seen it. I wonder if Playgrounds or Elm Live Eidt would even exist without his thoughts, since you can clearly see how he invented that concept, and maybe some young Chris Lattner seeing it ;-)
Since the obvious stance here is the employer being the “victim”, I’d like to look on the other side of this. To me, this seems like extremely poor management. Letting a single employee build an entire product is destructive for the team, but also for the employee’s mental health. Working 12/7 for 3 years is not a way to sustain talent.