I guess this means I'm an actual published author now...
I've got a few papers under my belt in conference proceedings, but I just sent in the copy-to-be-typeset for a book chapter.
Intent-Oriented Design Pattern Formalization using SPQR will be Chapter 7 in the upcoming Design Pattern Formalization Techniques, due out RSN from Idea Group publishing.
Keen.
Now to get to work on an actual entire book... :D
Intent-Oriented Design Pattern Formalization using SPQR will be Chapter 7 in the upcoming Design Pattern Formalization Techniques, due out RSN from Idea Group publishing.
Keen.
Now to get to work on an actual entire book... :D
no subject
If you're looking for more practical texts, then I'd start with the granddaddy _Design Patterns_ text by Gamma et al. It's a good intro, and pretty clear. Also, it lays out the basic patterns that most people use.
OTOH, I can talk about this crap for hours if you're interested - one of the books I have in mind is an approach to programming that *starts* with patterns instead of ending up at them. And yes, I actually have a way of making it understandable to the novice. :D Given an understanding of what a function is, and what variables are, I can walk a new programmer up through OO principles in a methodical fashion such that they learn to think in abstractions from the beginning, instead of trying to shoehorn those in later. I figure it should be easier for an established programmer to pick up the patterns portion along the way. ;)
no subject
I am interested (I imagine I can at least listen intelligently, even if I can't contribute much to the conversation), and I'd definitely be interested in the hypothetical book. A lot of effort has gone into figuring out design patterns (not that I have to tell you that), and it only makes sense to use that effort to short-circuit the learning process--it's only when the starting point advances that significant progress starts to be made at the frontier.