In software engineering, a design pattern is a general repeatable solution to a commonly occurring problem in software design. A design pattern is...
For further actions, you may consider blocking this person and/or reporting abuse
lol... if i will get theese questions, i will berelly answer to the first one... (fulltime developer with 6+ years of experience here) :)
I feel you. Deep down you do know the concepts and understand them and even know in which situations one pattern is best suited than the other, but you have trouble to explain them verbally or by writing. It's not easy for me to provide answers with such detail in so little time.
Anyway, nice article. :)
Exactly! :) is possible i use majority of these things and i even do not know it :D i am self learner with no formal CS study. So I still have interesting "aha" moments. "This is how binary works? woow", or "Oh, that are pointers! cool" and so on... :D
Agreed, I even read two books about patterns, but somehow I can't explain them in conversation and don't remember most part of them.
The first picture is the John Hancock Center, Chicago.
Chicago has a lot of Nice examples of good buildings with great architecture which inspires to build beautiful code.
Nice summary. I'd also like to add Singleton pattern in here although it is sometime not to considered as a design pattern but I have been asked about it most of the times during interviews.
I once got a question in an interview, something like "What's a Singleton pattern?", although I used it a lot, I couldn't build the right sentence to explain it clearly or shortly...
What a most practical post I've ever read. Fortunately, I read this before doing any interviews. This abstract things make me mad anytime. (-_-)
Such abstractions are one of the many reasons that I try to avoid OOP the most as I can, not my cup of tea at all.