Object-Oriented Thought

Random Thought for the day:
One of the things I enjoy about OOP design is that there is no single best solution to a problem. (Or perhaps another way of putting it is that there's always a beter way to solve your problem!) Sure there are best practices, and a book like Head First Design Patterns can help you understand those. But I find the whole process of creating an object-oriented design forces you to make a lot of creative decisions, and experience really matters. When I finish an OOP project, I'll often look back and evaluate what worked well and what didn't, and apply things that were successful to the next project. So don't cling to the idea that there's a single right way to do things, and just dive in, experiment, and have fun!

360 Flex Countown

I'm really looking forward to the 360 Flex conference next week, and I consider myself fortunate to have gotten a ticket! If anyone who reads this blog is going to be at the show, don't hesitate to email me (avatar@pasz.com). I've sworn that I'm going to make a commitment to do more networking at this conference.

I've been boning up on Flex all week, and I feel solid enough that I can skip the "Flex 101" track and dive right into more advanced presentations. I'm especially looking forward to learning about Cairngorm. Up to now I've been of the Do-It-Yourself school when it comes to building apps. But as frameworks mature, and as *everything* becomes more and more complex, the need for frameworks grows.