133 reputation
8
bio website
location Folsom, CA
age 37
visits member for 3 years, 7 months
seen Aug 5 at 23:11

Jul
7
comment confusion on using nodejs within an actual web application or ide
Having said that, if you find a compelling need for node.js in your application, you would almost definitely do what @Oded suggested. You would use HTTP (most likely) to communicate from the main part of your application or web page to/from your node process. I think that's a perfectly valid approach.
Jul
7
comment confusion on using nodejs within an actual web application or ide
Oh, I totally agree. I've been dabbling with node.js off and on over the last few years as well. It's probably a good thing to get familiar with. I just think you're likely to get a bad taste in your mouth about it by going down this path. If you're keen to learn javascript in general, you may be better served by using something like jQuery on your ASP.net pages. That seems like a much more appropriate context for diving into javascript in your project. Granted they serve different purposes, but in terms of sheer usage, I think jQuery is more widely used than node.js...don't quote me on that!
Jul
4
answered confusion on using nodejs within an actual web application or ide
Dec
23
awarded  Popular Question
Oct
4
comment Should we quit trying to do agile if QA takes 12 weeks?
You are 100% correct. Your three items are good advice. I can only affect so much change as a single developer, but I can try to lead by example and see if some QA people want to come along for the ride. My biggest frustration is that nobody else really seems to care, which is obviously a huge barrier to the successful turn around required. Most people on the team are just happy to continue with the status quo; at least that's my impression.
Oct
4
comment What Types of Stories Should Be In a Sprint Review?
Sorry for the delay in accepting. Your answer is reasonable, and you bring up some great questions. My question came from a place of frustration, because our Agile effort is completely derailed. But it's like talking to a brick wall trying to get any realistic assessment of the situation. We have new PLM on board, and I think these questions you pose in your final paragraph are a good starting point to begin the conversation with her to hopefully get a fresh start. Thanks.
Oct
4
accepted What Types of Stories Should Be In a Sprint Review?
Sep
1
awarded  Editor
Sep
1
revised What Types of Stories Should Be In a Sprint Review?
Edited to be more direct instead of being a rant.
Sep
1
comment What Types of Stories Should Be In a Sprint Review?
No, not really concerned, because these are arguments I'm prepared to make with the necessary people internally. The post is a bit of a rant though, so I'm going to edit it.
Aug
31
asked What Types of Stories Should Be In a Sprint Review?
Aug
19
awarded  Nice Question
Jul
28
comment Should we quit trying to do agile if QA takes 12 weeks?
Thanks for the conversation guys, it was very valuable to me. I think it'll be valuable to strive to include QA in the iteration and think of our product not as a whole but rather as the smaller components that constitute the whole. This seems like a good plan to address the situation.
Jul
28
awarded  Scholar
Jul
28
accepted Should we quit trying to do agile if QA takes 12 weeks?
Jul
28
comment Should we quit trying to do agile if QA takes 12 weeks?
Our full product is really made up of many smaller parts that can all be upgraded independently. I think our customers are very willing to upgrade those smaller components much more frequently. It seems to me that we should perhaps focus on releasing and QA'ing those smaller components at the end of sprints instead. We could shorten the feedback loop due to a more focused approach and deliver value to customers more quickly. Then we could do a full product release at some point that wraps up all the smaller bits. Then QA has less to do since most has already been validated in prior sprints.
Jul
28
comment Should we quit trying to do agile if QA takes 12 weeks?
However, I don't recall us ever releasing a build to a customer after a sprint. Furthermore, the way our customer base is, they don't want a full product release that often. Our customers are slow to upgrade. The most important point that you made was at the end of your response in terms of not applying agile if the requirements are not agile. I think this is spot on. When we started doing agile, we had it dialied in, and the circumstances made sense. But since then, things have changed dramatically, and we are clinging to the process where it may not make sense any longer.
Jul
28
comment Should we quit trying to do agile if QA takes 12 weeks?
I think this is probably the best response in light of our current situation. For me, one of the most important parts of Agile is having a shippable release at the end of each sprint. That implies several things. First, a level of testing must be done to ensure no showstopping bugs if you think you could release the build to a customer. Second, assuming the first statement is true, is it possible that QA is duplicating a lot of work that should have already been done during development? I think there is probably something to address there, both in our QA and our development team (I am a dev).
Jul
28
comment Should we quit trying to do agile if QA takes 12 weeks?
Your response brought up some good conversation between a colleague and myself. The main point in your response that got me was, "At the end of a sprint (or a couple) you release a product you are confident it could be put in the market." I don't ever recall releasing product at the end of a sprint until after we've completed a whole series of sprints, it's gone through QA, and we've had several rounds of follow-up bug fixing. In that respect, I think we're using Agile merely as a way to break up and organize our workload and nothing else. We are not gaining any benefits of Agile really.
Jul
28
comment Should we quit trying to do agile if QA takes 12 weeks?
I think this is a very good response. I'm not really aware of how the QA team is organized or how they proceed with their testing. Our QA team is in India, which I think is a not insignificant part of the problem. From what I understand, their test plans are not published such that anyone can review them and validate them. Furthermore, due to the time difference, the turn around time on the back-and-forth between developers and QA is atrocious. What should take an hour of conversation at someone's desk turns in to days of emails or JIRA comments.