4 ms·
>You just rewrote the app from C++ to Ruby on Rails Unless the C++ app was poorly written (and thus some kind of maintenance nightmare) this seems a little bac
by voidlogic 13y ago
>You just rewrote the app from C++ to Ruby on Rails
Unless the C++ app was poorly written (and thus some kind of maintenance nightmare) this seems a little backwards... I normally see CPU performance bound Ruby turning into C/C++,Go,C#,Java not the other way around.
Also, I'm trying to understand the moral of this story, is it:
Executing only matters if it furthers your bosses goals; furthermore, sometimes you need to explain how something you have done furthers said goals? (Surely this should happen before not after?)
Seems like common sense, but maybe I am missing something here..
- drojasug 13y agoHello, Thanks for commenting. The C++ to Ruby on Rails was just a joke. Something to make an example. Maybe I didn't explained myself well. What I wanted to say was that what you should do must align to your company, product or team goal. Thanks again for the comment.