323 reputation
39
bio website
location
age
visits member for 3 years, 5 months
seen 2 days ago

Jul
8
awarded  Yearling
Mar
29
accepted when to introduce an application services tier in an n-tier application
Mar
20
awarded  Editor
Mar
20
comment when to introduce an application services tier in an n-tier application
added more details in the question...
Mar
20
revised when to introduce an application services tier in an n-tier application
added more content to the question
Mar
20
asked when to introduce an application services tier in an n-tier application
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.
Jan
9
accepted Code review approaches
Jan
5
asked Code review approaches
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
awarded  Commentator
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
7
awarded  Scholar
Aug
7
accepted Design flaws and dealing with humiliation from it
Aug
7
awarded  Notable Question
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 :)