Definitely. Devaluation has «helped» the app. I'm sure the author did not try to make any predictions related to the reduction in the value of a currency. At the same time, it's a good lesson to learn — predictions can help you a lot, but they should never be considered as the only way to reach the goal, as any prediction may not come true. As a brief summary, I think it does always make sense to spend at least a little time on analysis, but never expect them to be 100% accurate.
Seems the original author is not around. I guess the design was not that expensive. The author is from Russia, where you can hire a free-lance designer for up to a $1k (for a single app).
It depends on what you are trying to achieve. You can save the model by calling model.save(), but then you'd probably have to have a field which would point to the right collection.
Freya, our project is not for promoting your own products. You should read the Rules page. If you want to let people know about your product, share the technical side of it. Community will reward you for that. Otherwise your publications will be downvoted and automatically be moved to Trash hub.
Thanks for a detailed feedback, Chao. We are looking into editing the article.
Off-topic: this conversation brought us to an interesting idea. What if we would let our users to edit articles and send diffs to authors, similar to git pull requests?
Very true about code readability. Scala is definitely one of the tools that can produce a lot of spaghetti code unless you use the language «the right way». Just curious, how often do you use implicits?
You are fun. Seriously. Unfortunately, Nikolai Ershov is not around to comment on how to improve the code. But I think your code looks good. You can also check this implementation: AVLTree.h and AVLTree.cpp.
But why would we use 60 bytes for padding?
Off-topic: this conversation brought us to an interesting idea. What if we would let our users to edit articles and send diffs to authors, similar to git pull requests?