AR lazy eval
Writing good code is not an easy task to accomplish and every developer has his weak spots.
For me, developing in a concurrent environment and scheduling between tasks is a serious weak spot.
I know, it may be obvious why these two specific topics might burden the development but I’d like to put it into simple words:
(1) The tiny fact that I cannot read the code line by line and know it really was the order of execution can sometimes make me wish I would have chosen a different profession (not really 🙂 )
Debugging suddenly becomes hell, if not useless, and all these threads pop up to your console from nowhere without having control over them. Not a pleasant experience indeed.
Lucky lucky me, as a Rails developer, I don’t get to deal with concurrency too much (if at all), but that doesn’t mean that (1) is solved…
View original post 599 more words