I promise
-
My coworker this morning started to "take shots" at my use of the "q" object in our project. Through some discussion I told him that I appreciated the clarity, and that angular also has the "q" model so the code would look the same on both ends. You also don't need to guess on weather or not something is goina block, etc (especially if you are new to the code type). It also allows us to implement a waiting on things that normally wouldn't. Most importantly, all with a consistent interface. All the code base uses the same methods. His argument was "I prefer the async in node". A great argument! What do you think?
Elephant elephant elephant, sunshine sunshine sunshine
-
My coworker this morning started to "take shots" at my use of the "q" object in our project. Through some discussion I told him that I appreciated the clarity, and that angular also has the "q" model so the code would look the same on both ends. You also don't need to guess on weather or not something is goina block, etc (especially if you are new to the code type). It also allows us to implement a waiting on things that normally wouldn't. Most importantly, all with a consistent interface. All the code base uses the same methods. His argument was "I prefer the async in node". A great argument! What do you think?
Elephant elephant elephant, sunshine sunshine sunshine
-
My coworker this morning started to "take shots" at my use of the "q" object in our project. Through some discussion I told him that I appreciated the clarity, and that angular also has the "q" model so the code would look the same on both ends. You also don't need to guess on weather or not something is goina block, etc (especially if you are new to the code type). It also allows us to implement a waiting on things that normally wouldn't. Most importantly, all with a consistent interface. All the code base uses the same methods. His argument was "I prefer the async in node". A great argument! What do you think?
Elephant elephant elephant, sunshine sunshine sunshine
-
I think the end satisfies the means, whatever option can make it work best should be used... tough i would like to see a better argument than that.
Life's like a nose, you've got to get out of it whats in it!
I win anyway unless there's good evidence of why not. I'm the only one that writes code in the project. He also has only basic experience with node and only simple sample projects with angular. I just thought the conversation was .... odd.
Elephant elephant elephant, sunshine sunshine sunshine
-
I win anyway unless there's good evidence of why not. I'm the only one that writes code in the project. He also has only basic experience with node and only simple sample projects with angular. I just thought the conversation was .... odd.
Elephant elephant elephant, sunshine sunshine sunshine
Sounds like your average college group project discussion. i remember having this conversation once: Student 1: "As for version control, should we go for Git or SVN?" me: "School provides a svn server so we might aswell use it." student 2: "we should use Git." Student 1: "... and why?" student 2: "because it's awesome!" Try asking the lad if why i thinks async should be used asside from prefference and counter it. Even if he's a greenhorn (like me btw) :laugh:
Life's like a nose, you've got to get out of it whats in it!
-
Sounds like your average college group project discussion. i remember having this conversation once: Student 1: "As for version control, should we go for Git or SVN?" me: "School provides a svn server so we might aswell use it." student 2: "we should use Git." Student 1: "... and why?" student 2: "because it's awesome!" Try asking the lad if why i thinks async should be used asside from prefference and counter it. Even if he's a greenhorn (like me btw) :laugh:
Life's like a nose, you've got to get out of it whats in it!
Stefto wrote:
greenhorn
They have drugs for that now. :-D
Mongo: Mongo only pawn... in game of life.
-
My coworker this morning started to "take shots" at my use of the "q" object in our project. Through some discussion I told him that I appreciated the clarity, and that angular also has the "q" model so the code would look the same on both ends. You also don't need to guess on weather or not something is goina block, etc (especially if you are new to the code type). It also allows us to implement a waiting on things that normally wouldn't. Most importantly, all with a consistent interface. All the code base uses the same methods. His argument was "I prefer the async in node". A great argument! What do you think?
Elephant elephant elephant, sunshine sunshine sunshine
I prefer the one that gives the better performance-test results, whether I find it aesthetically, egoistically, or sexually appealing or not. If it's neither, then I, quite frankly, don't give a toss.
I wanna be a eunuchs developer! Pass me a bread knife!