Per was right, the xmlns was the beginning of my issue(s).

I was just able to install and activate the Timer Job, yea! But, I took a different route than what I did yesterday. Initially, I copied over the feature folder to the product SP2010 hive, and edited and renamed the AltirisFeature1.feature file to Feature.xml. This was incorrect. Though with enough hacking, I was able to get the Feature.xml worthy enough to get installed and activated, the feature subfolder from my vs2010 project did not contain the necessary compiled code of the Timer Job. Yes, i was confused.

To solve my problem, I deactivated and uninstalled the feature from my sp2010 production environment. I then went back into my vs2010 project and added the feature to the package and built the wsp. From there, I loaded and deployed the package to sp2010 using tested scripts. From there, I ran the get-spfeature cmdlet to confirm the feature was added to the farm, and confirmed the name. From there, I activated/enabled the feature using the enable-spfeature cmdlet. success. The timerjob is now running every 5 minutes. 

so, Per, thanks for the direction. I have some more learning to do.

Errors when attempting to install a sharepoint 2010 feature
TL;DR;
I need a compound that is harmeless to the human body, odorless, tasteless, causes some kind of visible reaction (urine coloration perhaps) AND can be bought without medical recomendation.
LONG VERSION;
Food stealing in my company fridge has become a serious problem. It's not only a recurring issue but a targeted one... our thief has been targeting "high" value, particularly coconut water. HR seems to ignore our complains... so I decided to take matters in my own hands... since I have access to timesheets, I thought that if I can scare out thief to leave work or skip it, I can narrow-it-down/point-him-out because we have about 30 people in our office...
