The Pragmatic Craftsman :: Simplicity from complexity : by Stanley Kubasek ::

Fundamentals of programming

Almost all of us know the GoF patterns. Perhaps not all of the patterns. I forget them from time to time, but with more experience, I remember more and more. (I keep forgetting what a Memento is. :) )

As important as they are, I think there are other, perhaps more important patterns and principles that I follow. Some of them are “in my head” when I code. Some of them are there and I just follow them without naming.

They are fundamental theorems/patterns/principles of programming.

Good idea to review them.

Good idea to write about them.

Good idea to revisit them.

Don’t you think?

Languages and trends pass by. Principles and how we approach our programming tasks stays with us. Forever.

I’m currently deep into Python. Design patterns I learned earlier still apply. I learned JavaScript a while ago. Same thing.

I feel it’s not the languages we know count. It’s how we go about doing the tasks we have on hand. It’s how we craft software no matter what tools we use. Python is good for one thing; Java for other; and Javascript still for another, but we can apply “our learned way” to all of them.

Once we have solid principles in place, we’re able to reuse it fromĀ languageĀ to language. Deepening and improving that knowlege has the highest return, I feel.

So I’d like to revisit SOLID principles; GRASP patterns. They’re at the heart of programming. Close to my programming heart, at least. :) More to follow.

Related Posts

Leave a Reply

Favorite Quote

Topics

Tags

Archive

Currently Reading

Shelfari: Book reviews on your book blog

:: The Pragmatic Craftsman recommends

:: The Pragmatic Craftsman book reviews

Info

© 2001-2012 Stanley Kubasek About me :: Contact me

Me on Twitter

The Art of Readable Code -- looks like an interesting book. Good review by Mr. Zakas: http://t.co/clNLer0w - 8 days agoUnderstanding JVM Internals | CUBRID Blog: http://t.co/mbZMXcxG via @AddThis - 12 days agoBuilder pattern with required params: elagant solution! http://t.co/YjC3NRsv - 15 days ago@leszekgruchala Good to hear it's fast. Looking to upgrade to IntelliJ 11 soon. - 19 days agoPutting related classes together is another way of looking at "structuring your code by feature." Makes your code more cohesive. Big + imho - 28 days ago

»see more

Recent Entries