design patterns / Architectures etc

[abcd]

I have 13 yrs experience working from Visual Studio 1.x today VS 2005 (both
VB and C++)

Most of the time I have worked in N-tier applications, Web applications,
Windows applications....My company is a small company very limited
budget..We have enterprise web products written in VB/VC++, class ASP. We
have not even used .NET etc.

Lots of people are talking about Design patterns, standard architecture (SOS
or other IBM). I am very novice on these concepts...How should I learn all
these things and how should it help me to enhance my products, will that
help me to generate revenues....Why should I re-engineer my working
products....

Can someone focus on my dilema....

Thanks

 

[Guest]

Hi,
this is the begining:
http://www.codeproject.com/useritems/simplifiedDpatterns.asp

Books :
http://www.amazon.com/Design-Patterns-Steven-John-Metsker/dp/0321126971


Regards,
Husam Al-aáraj
www.aaraj.net

 

[Kevin Spencer]

Here's a good starting point:
http://msdn2.microsoft.com/en-us/practices/default.aspx

--
HTH,

Kevin Spencer
Microsoft MVP

Printing Components, Email Components,
FTP Client Classes, Enhanced Data Controls, much more.
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net

 

[Moty Michaely]

I have 13 yrs experience working from Visual Studio 1.x today VS 2005 (both
VB and C++)

Most of the time I have worked in N-tier applications, Web applications,
Windows applications....My company is a small company very limited
budget..We have enterprise web products written in VB/VC++, class ASP. We
have not even used .NET etc.

Lots of people are talking about Design patterns, standard architecture (SOS
or other IBM). I am very novice on these concepts...How should I learn all
these things and how should it help me to enhance my products, will that
help me to generate revenues....Why should I re-engineer my working
products....

Can someone focus on my dilema....

Thanks

Hi,

During all your working years, have you tried to maintain Object
Oriented programming design and implementation?

Moty

 

[Mr. Arnold]

I have 13 yrs experience working from Visual Studio 1.x today VS 2005 (both
VB and C++)

Most of the time I have worked in N-tier applications, Web applications,
Windows applications....My company is a small company very limited
budget..We have enterprise web products written in VB/VC++, class ASP. We
have not even used .NET etc.

Lots of people are talking about Design patterns, standard architecture
(SOS or other IBM). I am very novice on these concepts...How should I
learn all these things and how should it help me to enhance my products,
will that help me to generate revenues....Why should I re-engineer my
working products....

Can someone focus on my dilema....

Two books I have used are ISBN 0-596-00712-4 (It's in Java but Oops
programming is Oops programming. The other one is ISBN 0-321-26820-2.

You can look-up the ISBN numbers, use Google.

And if you want to know the power of .Net, then I suggest you get either the
VB or C# book and learn about frameworks, either 3rd party ones like CSLA or
in house written company frameworks for N-Tier architecture, based on Base
Objects.

http://www.lhotka.net/Article.aspx?id=1351540e-b941-446a-bacb-e0059cc82ee7

 

[Jon Skeet [C# MVP]]

I have 13 yrs experience working from Visual Studio 1.x today VS 2005 (both
VB and C++)

Most of the time I have worked in N-tier applications, Web applications,
Windows applications....My company is a small company very limited
budget..We have enterprise web products written in VB/VC++, class ASP. We
have not even used .NET etc.

Lots of people are talking about Design patterns, standard architecture (SOS
or other IBM). I am very novice on these concepts...How should I learn all
these things and how should it help me to enhance my products, will that
help me to generate revenues....Why should I re-engineer my working
products....

You're almost certainly using the patterns already, but:

1) By using standardised language (adapter, flyweight, singleton etc)
it's easier to communicate

2) Some patterns are easy to get wrong (like double-checked locking in
..NET) and it's good to have a fairly standard way of implementing them

If you're *not* using these patterns already, chances are your code
could be refactored to be more maintainable. It doesn't make sense to
go back and do it all immediately, but when you need to go back to some
code anyway, it's always worth seeing how it can be made more readable
or how design smells can be eliminated.

As for how to learn them - there are plenty of books around. With C++
experience, the Gang of Four book may well be your best starting point:

http://www.amazon.com/Design-Patterns-Object-Oriented-Addison-Wesley-
Professional/dp/0201633612/ref=pd_bbs_sr_1/105-1983324-1348430?ie=UTF8
&s=books&qid=1181716181&sr=8-1

There are plenty of other pattern books around - the Head-first Design
Patterns book has a good press, although personally it's a bit over-
the-top informal for me. (It's also Java-based - not an issue if you've
done Java though, and many patterns are applicable to most languages.)

 

[Mr. Arnold]

http://www.amazon.com/Design-Patterns-Object-Oriented-Addison-Wesley-
Professional/dp/0201633612/ref=pd_bbs_sr_1/105-1983324-1348430?ie=UTF8
&s=books&qid=1181716181&sr=8-1

You surround the URL with <a long url >

http://www.amazon.com/Design-Patter...1348430?ie=UTF8&s=books&qid=1181716181&sr=8-1

http://tinyurl.com/

http://preview.tinyurl.com/2doybv