xiongmao wrote:Yup, AJAX, Android and jQuery get my vote, along with MySQL.
The rest is fluff really.
Also add on C# or Java like I have and you'll have some very marketable skills.
Free OOA/OOD like C-sharp and Java??!?! via this program? Nah. I'm shocked that Ruby on Rails is even offered there;
that's a sick language from the syntax, compilation, and run-time.
I wouldn't need C# training anyway; I got it on lock. Not coldly, but nevertheless, I still got it on lock that TechNet,
StackOverflow.com, and SharePoint.StackExchange.com are a click away if I were to run into difficulties.
One part of the C# suite that I would regularly look up .NET Assemblies in Powershell (don't call it scripting even though it's not a true OO language; I take offense to people calling PowerShell a scripting language) to obtain their 4-part-assembly information (Culture, Public Key Token, Version, and Namespace/Name of Assembly).....Not all .NET Assemblies are registered in the GAC on any server so yeah.
Powershell is a goddamn programming automation language!!!! I automated registry permission entries for AD (Active Directory domain) accounts on Servers, used CredSSD on WinSock Manager to speak to boxes even through firewalls, IIS WebSites with their respective App Pools, Taxonomy/Managed Metadata Service for SharePoint 2010 and SharePoint 2013, more IIS App Pools so that SharePoint Web Apps (with creating Super Reader and Super User Portal Buffer account automation and Policies for Web Apps) can run on them so that Site Collections can retain WebSites), automating SharePOint Out of the Box Application Services like Enterprise Search, MMS/Taxonomy and User Profile Sync with AD, writing LoopBack entries of all the serves on the SharePoint farm out to the HOSTS file, writing out to web.config files in various directories, granting permissions to IUSR webserver account on EventLog Registry entries so that it can write to the Event Log with no worries, not just the SharePoint ULS logging system, then automating writing multiprotocol bindings to IIS Websites, a lot of sh.it just to take away the manual manhours to implementing such a real-world solution. Now Batch files are scripting, not Powershell, but I digress!!!)
9,461 lines of PowerShell code just to do that!
