dev self-training - pluralsight.com

http://pluralsight.com/training

read public ontologies using F#

F# and OData (to read public ontologies using F#)
http://msdn.microsoft.com/en-us/library/hh156504%28VS.110%29.aspx

Microsoft COSMOS - massive data aggregation processing

https://www.google.ie/search?q=cosmos&rlz=1C1CHHJ_en-GBIE466IE466&sugexp=chrome,mod=16&sourceid=chrome&ie=UTF-8#hl=en&safe=off&rlz=1C1CHHJ_en-GBIE466IE466&sclient=psy-ab&q=cosmos+microsot&oq=cosmos+microsot&gs_l=serp.3..0i13l2j0i13i30j0i13i5i30.6264.7385.1.7541.8.6.0.2.2.0.111.546.4j2.6.0...0.0...1c.PJWZeAsroxE&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=400185c91e9e233f&biw=1920&bih=943

SharePoint articles

SharePoint Dev

Training Videos from Microsoft

http://msdn.microsoft.com/en-us/sharepoint/aa905692

Powershell

Features and Solutions cmdlets

http://technet.microsoft.com/en-us/library/ee906565.aspx

SharePoint performance 

includes load-testing:

http://www.sharepointpromag.com/content1/topic/sharepoint-performance-troubleshooting-141506/catpath/sharepoint-server-2010/page/3


SharePoint performance test - does NOT sound too impressive ?!

A recent load test example. Looking at your web servers, you need to examine the number of concurrent users that you're going to expect to have and measure that number against what your hardware and VM can manage. A recent load test that I performed showed these results:

• Two SharePoint web servers (four cores, 16GB RAM), using load balancing
• One SharePoint application Server (four cores, 16GB RAM)
• One SQL Server instance (16 cores, 128GB RAM)

When performing a simple Create, Read, Update, and Delete operation in a standard SharePoint list, the system became completely non-responsive at 500 concurrent users. This minor field test simply logged a user in, created a list item, added text to the item, saved the item, deleted the item, and logged the user out. Watching this test on the server side, we found that we were immediately CPU-bound.

SharePoint Troubleshooting

Developer Dashboard

http://www.windowsitpro.com/article/sharepoint/sharepoint-troubleshooting-data-long-141674

SharePoint 2013

http://www.sharepointpromag.com/blog/dan-holmes-viewpoint-on-sharepoint-blog-24/sharepoint/sharepoint-2013-decision-143754

kanban - time management via Importance, Focus, Value

kanban - two simple rules:

• visualize your work 
•  limit your work in progress

http://www.personalkanban.com/pk/


kanban & pomodoro technique:
time management via:

• Importance
• Focus
• Value