Don't you already have welfare, a system to pay for all people in the USA who happen to not be working?
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Link to Original Source
Link to Original Source
Link to Original Source
After doing that for two years and thinking the pastures were greener elsewhere, I found myself basically doing software installations, configurations, and onsite customer training. I'm fairly extroverted (especially for a tech guy), and so while I enjoyed training the customers, the tech side wasn't technical enough for me. Not to mention, after several years on the road, I had tired of the travel. I got caught up in a corporate layoff in this particular case or I'd probably still be tolerating the travel and doing this job.
But, I haven't been able to bring myself to apply for any "easy fit" positions for me (more traveling in management consulting). I'm tired of it.
I really think I'd enjoy being a programmer again — probably at the "team lead" level where I am actively programming, managing developers, interacting with management, but not really IN management where all the politics starts and where the programming ends.
My barrier is that my programming skills are out-dated and rusty. I can dust that rust off very quickly if I apply myself. Here's my questions.
(a) what language(s) would you study?
(b) would certifications help get me back in the door?
(c) what do I need on my resume to get past the interviews in order to be given a shot at such a role again? (I was a programmer team lead back around 1999-2001. Unfortunately, I got "promoted" past that point and haven't been as happy since).
Your thoughts are appreciated! -Thanks!"
That was the old Apple TV. This is the new Apple TV. It has a purpose. As ephemeral as the device's purpose is, only Jobs knows from day to day.
Here's my biggest problem with Apple ca. 2010:
Apple is the (surprising) intersection of technology and the liberal arts, and that is deeply offending to insecure geeks, to whom technology needs to be complicated, obtuse, highly technical and impenetrable. To them, making something usable is a travesty.
This was a correct statement for Apple during their dark ages in the 90s and up until the iPod. These days, while bringing more attention to form factors such as tablets and smartphones is laudable, what they've done an about face on is the liberal/creative art community: the same community that kept them going for a decade. (I'm not even going to go into the hacker community that gave Apple its start: that's a completely different ball game.)
Sadly, today that's no longer the case: Apple has increasingly been dictating how you should use their devices (i.e. the iOS walled-garden app store), failing to communicate or work with companies that provide that core community (i.e. illustrators, designers, artists of all varieties) their core software (i.e. Adobe), and insisting on the elimination of certain technologies which the entire community has rallied behind as a useful tool and interaction paradigm for their craft (i.e. pen-based tablets). It is for these reasons (and one other*) that I have severe misgivings and issues with present-day Apple.
I commend Apple on their inroads at making computing accessible, but I abhor their behaviour regarding their original demographic. There was a time where if you were going into the arts, in any way, you only did it with a Mac; to install and use Photoshop on a Windows system was appalling, not to mention unstable.
*: I have significant, personal issues with their switch from a POWER Architecture platform to an Intel-based platform; POWER was, and is, a far superior system architecture, as evidenced by the significant use of POWER-based architectures in common computing appliances found in most households (i.e. any current generation video game console).
I would recommend against using Alice right off the bat: it's way too focused on storytelling, and not actual game development. If you want to teach gameplay (as you should), use Microsoft Labs' Kodu available here. It's brilliant, and completely graphical, and anybody can pick it up quickly. I taught it this summer to children aged eight to 14 in a week, and they were capable of building their own games just fine by the end of the week.
The only real way to confirm exactly what you should use in your course is to actually use each package for about a week: know it, learn it, and always be several steps ahead of your class.
I wouldn't mind having Michigan. It would solve all the Windsor/Detroit problems with using the tunnel.
(Disclaimer: I live in Windsor.)