Keeping motivated
OK. So I'm terrible at keeping focus. Except under one condition. When I'm learning something.
I was able to complete Veronica's application because I was teaching myself NHibernate. I was able to complete Tony's application because I was working with XAML for the first time. And just about everything else has perished.
Got me thinking on this because I haven't touched Tony's new application in a while. I had forgotten about WPF Toolkit on Codeplex so all of that effort in a custom Data Pager was a bit of a waste. Kept me focused for a bit, but once it was done pretty much everything else went with it.
Which got me thinking. I've started hearing the MVVM pattern being talked about a lot more extensively at work lately as one of our Silverlight control providers is starting to enforce a more MVVM approach themselves. I also vaguely remembered Prism. So went out and did some research and figured, that might be a good approach to my next project. Attempt to write the next version of Tony's application using Prism.
No guarantees that I'll stick with it. Tony isn't even using the current application which makes developing a second one seem like a waste. And Prism at present reminds me of the first time I looked at Silverlight and XAML. I didn't touch it for probably a full year after the first time I looked at it because it was such a different coding paradigm. Prism is much the same. But at least I also understand the value of what I'm looking at with Prism, whereas I didn't see the value in Silverlight when I first looked at it.
Also on the topic of potentially abandoning it. Prism is of less value to a lone developer on a small project with rather static requirements. Sometimes I wish I was more interested in completing projects than I am interested in simply consuming an idea. I already know why and when to use Prism, so I also know there is a good chance I will not get serious about implementing it until I find something meeting those criteria.
I was able to complete Veronica's application because I was teaching myself NHibernate. I was able to complete Tony's application because I was working with XAML for the first time. And just about everything else has perished.
Got me thinking on this because I haven't touched Tony's new application in a while. I had forgotten about WPF Toolkit on Codeplex so all of that effort in a custom Data Pager was a bit of a waste. Kept me focused for a bit, but once it was done pretty much everything else went with it.
Which got me thinking. I've started hearing the MVVM pattern being talked about a lot more extensively at work lately as one of our Silverlight control providers is starting to enforce a more MVVM approach themselves. I also vaguely remembered Prism. So went out and did some research and figured, that might be a good approach to my next project. Attempt to write the next version of Tony's application using Prism.
No guarantees that I'll stick with it. Tony isn't even using the current application which makes developing a second one seem like a waste. And Prism at present reminds me of the first time I looked at Silverlight and XAML. I didn't touch it for probably a full year after the first time I looked at it because it was such a different coding paradigm. Prism is much the same. But at least I also understand the value of what I'm looking at with Prism, whereas I didn't see the value in Silverlight when I first looked at it.
Also on the topic of potentially abandoning it. Prism is of less value to a lone developer on a small project with rather static requirements. Sometimes I wish I was more interested in completing projects than I am interested in simply consuming an idea. I already know why and when to use Prism, so I also know there is a good chance I will not get serious about implementing it until I find something meeting those criteria.
Comments
Post a Comment