Skip to main content

A pivot point - from SharePoint to Advanced Analytics

Today marks exactly 12 years since I started this blog. My first post went up on 3rd October 2008 and the posts that followed went on to shape my career with opportunities am so thankful for to everyone that gave them to me. 

Unfortunately, in the last 4 years, I took a back seat from blogging here and later on did a slight career pivot, from SharePoint into the world of data engineering and data science. I had thought long and hard about retiring this blog because I had initially dedicated it to a vertical field of SharePoint, at least that's what it was known for anyway. However, I realized that I can still continue to use it, albeit in a new field being data engineering and data science which I've embraced over the last 4 years, since my last post, while at the same time retain my blogging journey. In there is a message as well, to those that might be looking for hope, wondering whether the pivot is even possible. 

As part of rebranding this blog and making it fit for purpose, I have decided to make a few changes to this blog. I've given it a more modern theme, renamed it to Storytelling With Analytics, and bought the domain name storytellingwithanalytics.com which I will point to this blog unless I come up with something better to use the domain name for. 

Going forward, I plan to blog on sharing my learnings and experiences around advanced analytics, including:

  • Machine Learning, leveraging platforms such as Azure, Databricks, and Apache Spark
  • Some Artificial Intelligence inspirations
  • Statistics, where it makes sense
I hope you will join me on this new journey and hopefully cheers for another 12 years!

Sharing is caring.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Zambia's first K2 BlackPoint roll-out

Reporting to you live from Code|Influence... My colleague and I have been managing our organization's SharePoint infrastructure for some time now and we have just rolled out the first K2 BlackPoint in the country, intended mostly for SharePoint workflow developments.
8 comments
Read more

Zambia's first Helpdesk System on SharePoint

For my 25th birthday today 3rd March, 2009, allow me to present to you another first of its kind in Zambia. Yes we have done it again, having been Project manager, I present to you Zambia's first Helpdesk System which Masialeti and I have developed on Microsoft Office SharePoint Server 2007. The system also implements SharePoint designer workflows, Infopath forms, SharePoint document library and sends email notifications to the relevant personnel. When a user logs in a call, the user automatically receives a mail from the system, telling them that their call has been received and is being attended to, IT section will also receive a notification and the helpdesk manager will assign the call to the right IT guy who will also automatically receive a mail notification from the system. When the call is resolved, the user again automatically gets notified by the system with a mail giving them description of the problem they logged and also how it has been resolved. The user also has an ...
7 comments
Read more

How to implement a SharePoint "Change Management Process"

Not so much from the technical point of view, SharePoint Change Management is the process of monitoring and controlling changes within a SharePoint project. By managing the implementation of change, you can: • Reduce the impact of changes to the SharePoint project • Identify new issues and risks as a result of changes raised • Ensure that changes do not affect the SharePoint project's ability to achieve its desired objectives • Control the cost of change within the SharePoint project Change Management is comprised of the following processes: Step 1: Identify Change: The first step in the change process is to identify the need for change. Any team member can suggest a change to the SharePoint project, if he or she believes it is needed to keep the SharePoint project producing deliverables to the customer's specified requirements. After identifying a need for change, the team member records relevant information on a Change Request Form (commonly called a CRF), describing the chan...
2 comments
Read more