Good thing I'm in the mid west I guess. I'm over 40 and find work easily. I also kept my skills up to date and can do anything the younger devs can do.
I think I see the problem, I've been working with the.net stack for years now and don't even have to look for work, it finds me. Most/. ers rip on MS constantly and yet seem to not find work easily, interesting.
I work for myself and can fire clients if need be. I'll do whatever they want since my rate is high but I don't have to put up with anyone's bullcrap if I don't feel like it. Being independent kicks ass.
Yikes, I hope MS doesn't crumble. I've supported my family for years thanks to MS. The demand for devs is hotter now than ever before. I'm already working for a company that is switching to win8 tablets for field agents. Going to work every day would suck balls is MS went away, I'm spoiled using the best dev tools around and can now use them on tablets and phones.
It's really not that difficult unless you're writing winForms. Otherwise, if you're working with WPF or SL it's very easy to do it in a way that allows a lot of re use between WP and Win8/RT if that's desired. Further, if you work with something like mvvmCross, you can target iPhone and Android as well, using the Xamarin products.
I suppose bad programmers will make it difficult though.
My app passed certification Feb of this year. It's about to reach 20k downloads, some are ad driven and some are purchases for.99. So far, I can't complain. I've made a few house payments.
I'm not at build and not using VS2010 to work on WP71 projects anymore. They work fine in VS2012 and run on the emulator just fine. Of course you need to install Win8, which is pretty quick and easy.
I invested and my app is doing well. I also wasn't dumb and wrote it in a way that made it easy to port. With the latest changes to portable class libs my app is almost ready to do for wp71, wp8, and win8.
The article makes it sound like anything done in WP7 isn't applicable or reusable on WP8. That's total bunk. With the latest updates to Portable Class Libs and the async targeting pack for vs2012 it's super easy to share code between the 8's. WP8 SKD was just released today btw.
Slashdot Mirror
So it's Amazon S3, neat.
I'm in the Midwest also and the demand for java and .net devs is through the roof right now.
Good thing I'm in the mid west I guess. I'm over 40 and find work easily. I also kept my skills up to date and can do anything the younger devs can do.
I think I see the problem, I've been working with the .net stack for years now and don't even have to look for work, it finds me. Most /. ers rip on MS constantly and yet seem to not find work easily, interesting.
I work for myself and can fire clients if need be. I'll do whatever they want since my rate is high but I don't have to put up with anyone's bullcrap if I don't feel like it. Being independent kicks ass.
Works great for me, one mans trash is another mans treasure I guess.
My win8 release setup doesn't fel like beta, it's super stable and I haven't had any problems.
You'll take an iPhone (hardware) over WinRT (software) ... Weird.
Yikes, I hope MS doesn't crumble. I've supported my family for years thanks to MS. The demand for devs is hotter now than ever before. I'm already working for a company that is switching to win8 tablets for field agents. Going to work every day would suck balls is MS went away, I'm spoiled using the best dev tools around and can now use them on tablets and phones.
Weird, my 7 year old figured Win8 out on his own.
My company jumped to win8 but that's because I'm in charge.
For the .NET devs that don't know java or obj-c, yeah.
Yeah, it's super hard. Dear .NET developers your skills transfer right over to WP. You're all mobile devs now, have fun.
Way to ruin is FUD parade.
VB6 is alive and well, SL is alive and well. Any skills used developing SL won't be wasted, they transfer right over to Win8/RT XAML development.
It's really not that difficult unless you're writing winForms. Otherwise, if you're working with WPF or SL it's very easy to do it in a way that allows a lot of re use between WP and Win8/RT if that's desired. Further, if you work with something like mvvmCross, you can target iPhone and Android as well, using the Xamarin products. I suppose bad programmers will make it difficult though.
My app passed certification Feb of this year. It's about to reach 20k downloads, some are ad driven and some are purchases for .99. So far, I can't complain. I've made a few house payments.
I'm getting paid to do it right now, not by MS though. The company I'm working for are porting their app to WP and Win8.
It does but of course you can create a WP8 project, point to what you need in the WP71 project and add everything else to the WP8 project.
I'm not at build and not using VS2010 to work on WP71 projects anymore. They work fine in VS2012 and run on the emulator just fine. Of course you need to install Win8, which is pretty quick and easy.
I invested and my app is doing well. I also wasn't dumb and wrote it in a way that made it easy to port. With the latest changes to portable class libs my app is almost ready to do for wp71, wp8, and win8.
The article makes it sound like anything done in WP7 isn't applicable or reusable on WP8. That's total bunk. With the latest updates to Portable Class Libs and the async targeting pack for vs2012 it's super easy to share code between the 8's. WP8 SKD was just released today btw.
I missed the screwing over part, Im a .net dev and do not feel screwed over, just saying.
Developers don't have to flock to windows 8, there are already boat loads of .net devs.
I had the complete opposite of your experience.