Okay, so I’ve learned WPF and WCF and that was great. I didn’t bother with CardSpace because it’s probably not gonna take off.
Should i bother with Workflow,..is it worth it? What’s the big deal?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Okay, so I’ve learned WPF and WCF and that was great. I didn’t bother with CardSpace because it’s probably not gonna take off.
Should i bother with Workflow,..is it worth it? What’s the big deal?
It is worth learning or at least understanding WF. WF offers a different paradigm for building apps, a paradigm which may become mainstream in the future. Enterprisey? Yes, maybe today. But longer term WF or at least the paradigm it promotes, may become ubiquitous and universal. Using Workflows to describe programs may today be in the stage where OO and C++ was, 20 years ago.
Learning a new thing broadens your thinking. For example, even if you use C# or Java in your day-to-day job, knowing Lisp helps broaden your thinking about how to solve problems. IMO. WF is the same.
A second thought is to think like an investor. If you want to raise the value of YOU as a programmer, whether to learn WF would depend on the market or job you are in. WF skills in your space or in your company may or may not be worth your extra effort.