323 reputation
39
bio website
location
age
visits member for 3 years, 5 months
seen Dec 8 at 13:16

Oct
12
comment avoiding multiple calls to SQL while being modular
I've really not been able to profile the application because we are still in the design phase. I just feel that making three trips to a server when one trip can do the job is taking too many liberties too early. I could be wrong on this thought and Im willing to listen to critcism on this point.
Oct
12
comment avoiding multiple calls to SQL while being modular
the application which I described above is not yet written. At this point in time the possibility of individual views being required is not yet 100% But they are being written just because eventually they will be required as per the requirements we know today, which could also change in the future. what exactly did you mean by writing down a non-functional requirement ?
Oct
12
comment avoiding multiple calls to SQL while being modular
Thanks MSW for the comment. But could you expand a bit on why it would be reduntant? Each of those are doing different things.
May
30
comment Securing web services
both look the same to me, but I guess any clarity helps. I've committed your edits. Thanks.
May
30
comment Securing web services
Thanks. I was actually going for security at a conceptual level. assuming of course, all the basic things are done, like putting in https. In WCF you can actually send a user name password in the header or you can send the token. Keeping https in both ways, what would be the justifications of using one over the other? there must be some situation where one way favors the other and vice versa...
May
30
comment Securing web services
@BartvanIngenSchenau: in 'vs' situation you are looking at a clear winner. I'm not trying to find one winner here, but trying to understand which one is best suited under what particular condition. Its those conditions that I want to talk about; perhaps someone can talk of a third way as well?... The last para should have made that clear. If it isn't let me know.
Oct
25
comment How to manage and estimate unstructured requirements received from customers
Yes, I do that in all cases where we don't budget in a BA.
Sep
21
comment Software Architecture - From design to sucessful implementation
-ve markers please leave a comment so I can frame my questions better next time:) I've seen many other questions here that don't "fit" the format but have got some good responses to it.
Sep
21
comment Software Architecture - From design to sucessful implementation
+1 for the point about being ignored :)
Sep
20
comment Software Architecture - From design to sucessful implementation
sorry about that. what I meant was, where appropriate. Obviously you wont be able to apply OOP in ETL. My bad, will correct it. Thanks for pointing it out :)
Mar
20
comment when to introduce an application services tier in an n-tier application
added more details in the question...
Jan
19
comment Design flaws and dealing with humiliation from it
Mark - I don't understand how a question that has got the interest of 72 people and got 16 of them to favorite it, along with 18 brilliant answers that were collectively liked by over 200 people here, with an accepted answer, got "closed" as not being constructive!! The answers have facts and references from the respondent's personal work experiences. Where do you see a debate or argument or an extended discussion in a question that has a marked answer? If this question is not a good fit to the Q&A format then the Q&A format needs an ugrade... IMHO.
Sep
7
comment How can one manage thousands of IF…THEN…ELSE rules?
I wonder what the guys at the www.antiifcampaign.com have to say about your program.. :)
Aug
8
comment Do I really need oop for my kind of job? After 10 years I think I don't
whats the name of this book written by this guy from Romania who does a lot of magic with templates?
Aug
5
comment Design flaws and dealing with humiliation from it
I did admit I was wrong, but that dint help much because to both my manager and the customer I should have known better, considering my experience.
Aug
5
comment Design flaws and dealing with humiliation from it
No I dint push the bad design. I was brought into the team to solve problems that the team was continually failing at. Plus there was already the issue of bad design, code smells,etc. I was pulled in as the panacea to fix it all and make the customer happy. Lets just say that when I proposed this new design to our customer who has had more experience than me and of better quality too, I began to realize just as he was shooting it down that I made a fundamentally wrong decision somewhere. It was incrementally better than what the team had done, but still a lot in the red...
Aug
5
comment Design flaws and dealing with humiliation from it
I dont mind the learning. Its just the reputation u lose wen you keep making mistakes even if they are different every time. To everyone around it still looks like you made many mistakes. Not a new one each time, that you learnt from and got better.
Aug
5
comment Design flaws and dealing with humiliation from it
I made a similar mistake too. Deciding to keep a static class as the controller in an MVC app. Coming from a procedural background my OOP thinking is evolving everyday. I still think I have a lot to learn in making a decision on when to abstract and when not to. when to inherit, when go for composition. The worse part is after being shot down I spend time learning and after some time feel like I have finally got it..until I get shot down again..then its back to spending time learning.
Aug
5
comment Design flaws and dealing with humiliation from it
I'm no jon skeet :)
Aug
5
comment Design flaws and dealing with humiliation from it
As a senior resource I should have known those things. I'm sure my team thinks the same too.