Recently I got a call from some company who wants me to do some job in F#, for its client. The client took my interview and told that its client wants to do some work in F#. Things were going smoothly until the interviewer asked me that I should be writing F# code following standard and design patterns.

I just went to pause, as my brain trying to search Functional Programming Design Patterns. It gave me Scott Wlaschin’s famous answer. In functional programming every design pattern is function. But can’t give that answer to the client’s operator for sure. So, I gave the other best possible answer.

You are asking about F# code like Python or F# code like Haskell?

The contract didn’t get converted but this post does.

Let’s start with first shade. F# like typed Python.

If you are old enough to know and write code with Visual Studio 2012 then go back to that time, and try to remember good talks you have seen to learn F#.

Here are few of my favorites

• The Best Introduction to F# by Luca Bolognese, people might point you to many different resources for getting started with F#. But this video is still the best one to get started. Trust me on that.
• “How machine learning helps cancer research” by Amazing Dr.Evelina Gabasova, one of the gifted speaker in F# and machine learning community. Not only she is a good speaker, but she is also a damn good person, guru, and wonderful friend.
• Parallel and Asynchronous Programming with F# by Father of F# Don Syme. If you still think Don Syme is human, then go watch this video. He is not, you can tell from the way he pulls this talk and way he codes.
• Building a Better SQL Type Provider with Ross McKinlay. This guy bend language to practically a level where language has to tell, enough is enough man.
• Game Programming in FSharp with Andrea Magnorsky. I call her and Ross the Dragon Masters. You think FP is slow, think again. Dragon Master Andrea gonna prove you wrong.
• Xamarin Evolve 2014: Mobile App Development in F# — Rachael Reese, Firefly Logic — Long before fabulous born, F# was working with Xamarin. If I remember correctly Rachael gave the first talk about it.

There are common things you can abstract away from it

• Functions (obviously)
• Forward Pipe (Best thing in language)
• Type Providers

There were no Result Type, Elevated world, not even Railways. Even I have to ask on Stack Overflow, just to do multiple validations on an entity.

The language was so simple and beautiful. Tooling was good enough, at least it works most of the time. Don’t crash on my lap just because I have opened any big project. People are way more friendly then compare to now for sure. Good old days.

Python gets traction from the Data Science community because of its simplicity. It is too good to write algorithms, especially when you have definite input and output.

Here, F# just adds more power to this. You have types and type providers, you can write simple functions to process data, join them using forward pipes. It was too much fun then, I tend to convert every damn thing to forward pipe. Overdoing it sometimes but it was fun. This is the F# I loved the most. I still like this kind of programming, no specific types, few record types to define input and output and all the functions. Files and modules are always there to help in case of separation. So, nice and so Python-like.

Let’s see some code. I am demoing famous world bank data example (from their docs only).

So, what’s wrong with this approach. Practically nothing, but real-world problems (especially in web, distributed system, mobile, etc) kind of need something more. It needs some more design and architecture to hold big applications together.

But don't we already have design patterns for ages? Can't it be applied to F#.

F# is functional first language running on .Net. And it does support object-oriented programming. Here comes second shade of F#.

F# as better C#.

If someone likes me coming from C#, this might be a natural transaction. Try to map whatever you learn in C# to F#. I also wrote a couple of articles long back explaining how you can use traditional object-oriented design patterns in F#.

Here is how a typical C# class looks like.

and here equivalent beautiful F# code

You can make a little bit terser without going more functional

Look how beautiful F# code looks. I did write immutable C# code so I don’t have to write mutable F# code.

Let’s push F# code to the little more functional end. Here we have a small example from Railway Oriented Programming.

We are defining kind of domain with two different styles.

let’s do the same thing with class

Pick your choice, both give the almost same result on the consumer side.

But with this, we are moving more towards Haskell. Languages like Haskell, Scala have something called HKT or Higher Kind Types backed into language.

F# as a language by design lacks features like HKT.

For a long time I didn’t know HKT means Higher Kind Types. And the even longer amount of time I took to understand it.

There is a discussion going on how useful it is? So, it depends on choice of elders but F# at the time of writing this blog doesn’t have HKT.

It still doesn’t hold anyone to push your F# code more towards Haskell.

Here is the final shade. F# more like Haskell.

If you like to skip all the IO and monad stuff, just pause this blog here and watch this video by Scott W.

You can gradually grow your system to push towards Haskell. A Little help to LIFT your code will surely be useful. Read Functional Programming for Fun and Profit's Railway oriented programming post. Written by Scott Wlaschin's

Or you can use a wonderful library like F# plus

Let’s check out the validation example, I have taken from docs of F# plus. So, you can build upon that.

This style of coding is very helpful when you are designing a big IO based system. This way you easily separate logic from execution.

I did purposefully skip heavy functional concepts here. Concepts and patterns based on Algebra, Category Theory, Monads, etc. It’s good and important to know them. But that is totally out the scope for this blog. So, maybe next time.

F# is a very flexible language, and one can bend it as one like. Write down in comment what is your shade of F#?

Originally published at https://kunjan.in on October 27, 2019.

Speaking of issues, will going to talk about Functional Programming. Because if you are coding with Functional Programming you normally get fewer errors. I love them for those reasons.

In this post also as the title suggests I will be going to talk about Functional Programming only. There will be no code though, but mostly in a meta sense.

Fable

As we are talking about Functional Programming we have to talk about Fable. My current favorite tech. It nicely converts F# to JavaScript. Also, have a wonderful ecosystem. I am lucky enough to be part of it, and also maintaining awesome-fable. I am using it in multiple projects since more than a year. It is very much battle ready for putting in a big or very big project. I will talk about projects later. But let us talk about a few other announcements.

Green Print

If you take Blue and mix with Yellow what will you get? It is Green. Here is Green Print project. It is a thin wrapper around Blueprint Js. So, the blueprint can be used with Fable Elmish. Blueprint is UI library built for a desktop heavy web application. All the namespaces are in Fable fashion, Fable.Blueprint.*. It is still a work in progress though. I did port core and icons but others are still pending.

I love Fulma so I did take that project and make Green Print from it. I am using a library in a project for work. I will be adding to it to open source project as well. It is kind of working. The thing here is, BluePrint is quite a big library so I can’t test all elements with all features. Docs are also pending so there is a chance of few corner issues. But here I need community’s help to make feature ready as fast as possible. Fine tune the API or working on docs. It is the same as Fulma but bit different. Check out Blueprint JS and see if that matters to you. I’ll be happy if that can be useful to anyone.

Fabulous

Fabulous is a fabulous library for cross-platform mobile development. It is a wrapper around Xamarin.Forms with Elmish in it. I was so pumped up when it first launched, tried and made a couple of apps with it. Nothing fancy but was having fun around. There were a few things I was not happy about.

• The list is quite jumpy
• Not happy with the performance in android
• I felt there is too much wire up I need to do
• Live reload didn’t work for multiple files in the project

But

FabScaffold

Recently I created application with Fabulous within a week. Polishing UI did take a week more. I will write more about it in separate write up once I launch a application. Coming very soon. For now I rip apart my application and created a scaffold from it.

Here is the project called FabScaffold. It is having almost everything to get you started. It also provides an architecture to grow your next business application. Go for it. I have solved all mentioned issues other than live-reload for multiple files in a project.

Fabulous has same limitations what Xamarin.Forms have. Back end plugins gonna work as it should and for UI you might need a wrapper for few and few gonna work as it is. But it is too good without all that Xaml around.

Machine Learning Monday

I have started Machine Learning Monday a few months back. But due to year ending can’t continue. But will going to continue from next week. Coming Monday I will be reviewing F# for Machine Learning Essentials. Got this book from Sudipta Mukherjee himself. It would be fun. So, stay tuned.

Sad state of F# & Moving Forward

This is a little bit personal. Some might find it rant but please don’t mind. I started my consulting gig Fuzzy Cloud last year. There are a couple of people other than me. Sole motive behind starting my own gig was to do more work in F#. Be it consulting or training. It is such a sweet language and having a wonderful community around it. I did get a continues contract work a year before. But last year was not so good. Not only it is hard to find work in F#, but people also keep asking for other languages like Scala or Haskell. There is not enough buzz or work in F#. Even in a functional conference when people speak about Haskell, Scala, Elixir in the same breath they always skip F#. Even in twitter account Functional Works skips F# quite a couple of time. Even though I learn those languages, I am all in for F#.

I should not fall in love of language (it is just a tool). But what one should do when language is so delightful.

I am still going to try a few more months if I get good work in F#. Else I need to keep it for my hobby projects, only. I will be working more towards Scala, Rust, and Kotlin. Haskell and Swift are also there but I m kind of undecided on those.

I am available for F# related training and work if anyone interested or having a remote position open.

Speaking

In 2019 I will try to speak at more conferences. As of now F# exchange is top of my mind. Please suggest good conference if you think they are good and don’t mind fresh speakers.

Languages

Because of my for history I never liked English that much. Also, never bothered about it. But I guess I need to improve on that. Also, want to learn German as well. People says it is very close to Sanskrit. May be I can learn both. If you know how to get started with German better than Google search then please let me know.

If someone is confused about history and English they can read about Bengal Famine 1943 a very recent incident.

I will also try to write more compared to the last couple of years. There are many things I like to share but never get enough time to write. With that, I am closing it. Happy New Year once again to everyone.

Originally published at https://kunjan.in/2019/01/functional-programming-adventures-in-2019/.

Functional Programming Adventures in 2019 was originally published in FuzzyCloud on Medium, where people are continuing the conversation by highlighting and responding to this story.

Few days back I did a poll that which new shiny library I should be trying. Here is result of that

Kunjan Dalal on Twitter

I am thinking of trying one of the #MachineLearning - #DeepLearning library. Which one I should be trying? It should be fun and if possible can be used with #fsharp and / or #dotnet core. I ll share my experience in blog / video. Please RT.

As per popular demand I should be trying ML.Net. It is recently open sourced library from Microsoft for Machine Learning. It was started with all the C# examples. But lately there have been many F# samples.

So, obviously my first choice is to do with F#.

First, few good things about ML.Net

• Still in 0.6 version so a lot can improve (I like to try bleeding edge stuff)
• Quite a good things coming in, including Infer.net
• Here are the lines from ML.Net blog Over time, ML.NET will enable other ML scenarios like recommendation systems, anomaly detection, and other approaches, like deep learning, by leveraging popular deep learning libraries like TensorFlow, Caffe2, and CNTK, and general machine learning libraries like Accord.NET.

I will be looking deep into the library as well. But for now there are too many questions then answers

• I couldn’t find how internals of it works?
• How all the calculations part being done?
• Is there any options for GPU processing or it will leverage power of dependent library like TensorFlow or CNTK ?
• How it compares to Keras? As that is also doing similar things.

For now I have given a PR to make F# things more F# like. Nothing major but little bit clean up to make code more functional. Hope that gets approved. And I will be digging more into library.

Will try to have new article on F# in Machine Learning or Machine Learning in general every Monday. So, till next Monday stay tuned.

Originally published at https://kunjan.in/2018/10/machine-learning-monday/.

Angular 1 was good, very good specifically in its timezone. But after that they lost control on versioning and I lost control on Angular.

I did port Angular 1.0 to 2.0 which was kind of weird experience because both are completely different. While 1.0 is old school two way binding stuff; 2.0 was more of react rip off or catching up with react.

But it reach 7.0 (that was fast) , after a long time I was reading announcement blog and amazed the with progress angular made.

Specifically how they joining force with NativeScript. NativeScript allows use of Angular since ages but the ways code sharing is happening now; was never there before. There is a whole blog about it here.

Two things is here to stay, SPA and mobile application (android and iOS both). For the application suitable for a single page application in most cases it also suitable for a mobile application.

Most of the time people just put SPA in mobile using Cordova/ phonegap and hope that things just works. It did work for a start but soon you gonna miss native performance.

Here there are many option to create Native application, Native Script is one of them, I will not go in to the other options, but current integration of Angular and Native Script provide a wonderful opportunity for Green and Brown Field projects to add Native Mobile App support to SPA. It is having around 70% code sharing between angular and NS. Trust me that is not bad at all, look at it this way

70% code share means you are saving 70% of project time. That is equivalent to saving 70% of project budget.

Native Script was slow, but again it was. It is quite fast as of now, almost inline with Xamarin Forms or React Native. So, this is kind of best of both world and a option one should not miss if they are working in or looking into Angular.

Looking for help regarding this? Reach us out at FuzzyCloud .

Native Script — Angular Once Again was originally published in FuzzyCloud on Medium, where people are continuing the conversation by highlighting and responding to this story.

I always believe that be it paid or free, if and whenever possible tools, languages and compilers should be open source. There may be some drawbacks about this but getting a good community support is way better to ease out cons.

Even from day zero at Fuzzy Cloud, I always wanted my fellow friends to make mark in open source, till date I can’t drive them by example. But not any more. We are open sourcing internal application.

You can find github link here. It is Proof Of Concept; we did few days back to check out Ionic 4. I must say I am very impressed with results, we did create quite a good amount of screens covering every aspect of application. Requirement was to create application that can compare flight prices and hotel prices with single app. And within 2–3 weeks we are almost ready with UI part of it.

App is developed with Angular 6 but can be developed with any of your favorite framework. Yes, you heard me right, Ionic 4 is not attached with Angular anymore. But it did provide quite a good support for same. There are still many missing pieces to make native ready mobile apps but things are getting ready for better. Eagerly waiting for final release of Ionic 4.

Do have a look, and if you are thinking of having a word about it please don’t hesitate to contact us. Looking forward to it.

Until next time happy coding.

First Step in Open Source World was originally published in FuzzyCloud on Medium, where people are continuing the conversation by highlighting and responding to this story.

As far as I remember I never felt issue in using F# library in C# or vice verse. Obviously there were always a problems to make things work and my initial F# questions on Stack Overflow were mostly about inter-portability. But at the end of day in most of the cases it works without much of an issue. Today is different and we will going to talk about current state of F# for Web programming.

Just to give you a gist, F# was never a Mathematician’s, Data Scientist’s only language but now it is showing that it is as general purpose as any other language if not more.

History Lessons

I never wanted to include this section. But as written by George Santayana “Those who cannot remember the past are condemned to repeat it.”; I have put this section in article. This article is nothing but telling everyone that I am getting old now. It is bit of F# history and my history with F#.

Intro to F#

My introduction to F# is kind of because I wanted to learn how things work if I want to develop something related to finance. One thing led to another and I started learning F# using tryfsharp. Good old days of Silverlight. At that time Visual Studio not officially supporting F#. You need to install tools separately and install it for F# support. Forget about any other template. I don’t even remember there were much people using it. I distinctly remember Tomas, Evelina, Don and few more. As my most of the experience in Web, at that time also I wanted to use F# in Web Programming. I was using it by adding separate library project of F# in C# Web Project; it did work. But still something was missing. A complete F# Web Project.

F# on Heroku

I was able to run F# web application (self host using ServiceStack ) on Heroku back in days. It was listed under official guide for F# for web programming. My first bit of glory in F# world. I did spend couple of sleepless night to run that. And when it runs it was pure aha moment. I never got that much excited after that.

That was year 2013. You can still find the code here. It is old code but it works and served as a reference for a long time. Now, F# org site is going under a make over; I hope it stays in new site as well, as historical monument.

This was the time when one has to play with GUIDs if they want pure F# web application. I did added my bits to make this thing easier via creating templates for Web Application for Visual Studio 2012 and 2013. We do have templates for all the web framework available in Dot Net Full Framework. And yes there was no dot net core . Even though we still make things working on Azure with Kudu deployment.

Yes, I have been doing F# even before VSCode and Ionide , before paket and Fake was popular and way before Fable was there. Sometimes I do miss good old days of fixing Visual Studio and fsproj file.

Always a Hero

Even though things are not good enough, F# was always a hero. It works and it works way better.

Have a look at this, I was able to write beautiful Nance + SignalR code in F# and deploy it to Azure.

Same thing with ServiceStack and SignalR. Code looks way better in this. But still people were not picking up as option.

Until this time around when effort to bring F# to web increased multi-fold.

Web and F# — Right Now

Web Sharper

Oldest F# specific project to write F# on client and server side. It comes with commercial support and it is super awesome, always has been. Let’s see simple example of it.

ServiceStack with F#

ServiceStack is one of the most favorite web framework in early days to write API with F#. V3 is still available for free while V4 is now comes with commercial license. But this is one of the best framework I have worked with. Very much natural fit to functional language like F#. I can tell that after working with plenty of .Net web framework including WCF. It works with dotnet core, have plugins for almost everything and anything. It also has light weight ORM called OrmLite. And that too; works with F# without any issue. It is my personal favorite for production projects. Let’s see the code.

NancyFx with F#

Whenever I want to write sweet code with C#, NancyFx was and is always and first choice. Things become sweeter when it comes to F#. Here is Hello World from NancyFx.

ASP.Net MVC and Web API

Asp.Net MVC and Web API worked with F# since their inception. And it worked without more of any issue because of F#’s great support of CLR and OOP side of it. At the max sometimes just to make tooling happy we need to keep C# project around as wrapper and push client related stuff like JS, CSS and Razor in C# project and other things can be moved to F# project. Dot Net Core and Dot Net Core project templates have made things even more easier for getting started with F#.

I will skip those sample as F# community is kind having love — hate relationship with Microsoft Backed projects.

Above all are C# web frameworks, which holds the fort till new F# specific framework comes on horizon.

Suave

Suave is first one in town. First F# specific framework, with its own server implementation; if my memory serves me right. Just like Nancy it was micro framework and one can get up and running in minimum possible code. Let’s have a look at code.

Giraffe

When dot net core arrived. It was natural to have F# code that works on asp net core. But Giraffe goes one step ahead with wrapper that makes natural to write F# code on top of asp net core.

Freya

Freya take different approach then above two as web framework. It is composition based concurrent framework. Here you start creating machines that takes care of executing requests. Have a look at below code. Understanding Freya in details is definitely out of scope for this article so may be next time.

Saturn

I have always missed RoR like web framework. Asp.net MVC was there but never gave quite a feel. After phoenix came to Elixir, I wanted something for F# too. And then one fine night, I did see Saturn in sky. It is traditional MVC framework build on top of Giraffe. It comes with batteries (generators). Definitely a choice for some old school projects. Have a look at the code.

Fable

Fable is best thing happen to F# after F# it self.

It is F# to JavaScript transpiler. Just like WebSharper but don’t bound you to specific library. Completely free and Open Source. No strings attached.

It will take more than a article to write about Fable. Here is simple code in F# with respective generated JavaScript code.

You can always stared or watched awesome-fable list for any Fable related stuff.

We did come a long way ahead, and I was lucky enough to be part of it. Currently F# works on Dot Net Full Framework and Dot Net Core. Visual Studio and Visual Studio for Mac supports it by default. VS Code, Atom, Vim and other editors supports via plugins. You can build not only back end but beautiful front end using F#.

SAFE

Every technology have their abbreviation stack. It is basically combination of different technologies. So, how can F# stays behind. SAFE is same thing, combination of different technology to achieve one single goal; build a web application using F# everywhere. Have a look at how to start with SAFE stack and different option we have in SAFE template.

Fuzzy Cloud

After working in different technology for front end, back end, mobile, IOT and Cloud etc. I finally decided branch out. I have been consulting on F# project for last year as day job. So, after closing that I am / we are ready for new assignment. At Fuzzy Cloud we are happy to assist you for F#, Type Script, Front End, Back End, Cloud related projects. Be it Green Field or Brown Field. Just drop a message and we can talk about it.

We are officially supporting SAFE stack, along with two other wonderful consultancy.

Just drop a message at FuzzyCloud site or drop a mail at kunjan.dalal [at] fuzzycloud [dot] in . You can always follow me at twitter or at medium Kunjan Dalal.

Love to here from you. Happy Coding.

Current state of Web Programming in F# was originally published in FuzzyCloud on Medium, where people are continuing the conversation by highlighting and responding to this story.

So, what is there in it? We can say everything. Love stories to stories about war to stories about revenge. Philosophy to military tactics. Policies on tax, rules of espionage, watch over enemies and how to find the most able people and make them ministers. Theory karma which is part of Gita, which is part of Mahabharata. Yog (not to confuse with physical Yoga people do) explained in Mahabharata and so do life, death and life after death. A tale where God not solve problems for you but guide you to solution, enable you face the problems. A story where God is not forefather but a friend who is always there for you.

A story where even God accept curse with due respect given by a mother. A story where story teller him self not only narrate the story but also integral part of it. A tale stays same but meaning of it keep changing to every reader. A story which has spiral of different small stories consisting further different stories. A infinite source of knowledge, wisdom and fun.

I can go on and on; but let’s come back to F#.

Natural Language Processing

Understanding the human language, words and sentiments always is exciting. Specially using your favourite programming language. Processing old epic books is always fun, as it not only tells about history / mythology but take back to your heritage and culture. So, This part is from my Mentorship program (more details at the end). An article born from home work I got recently.

I don’t know the complexity level of it. It totally depends on reader. But results are indeed too good.

Let the fun Begin

First thing is to find out source in English (As it is easy to compare with data sets.). Project Gutenberg is good place to find some license free text. If you like to do code with this article then get your favourite book from site or you can always download if from my project.

That is whole Mahabharata in four text files. So, I did some manual labour to separate the books from it. You can find them here. There are total 18 books (sub books are not separated).

Let’s start with simple File IO.

That’s quite a lot terms for small piece of code. Now, we are one step behind to become data scientist.

Let’s find the unique terms and frequency of them.

see another line and we are done. We are now official data scientists.

Go ahead and try for other books also. If you are feeling lazy you can check out results here or see below.

For Terms:

For Unique Terms:

For Unique Terms per Terms

What next? Let’s do the sentiment analysis of all this books and compare them with each others.

Sentiment Analysis

Whaaat?

Analysis done to find out the tone of given text. Here we are having books. Basically using this we can find out that books is more joyful to read or tilted towards sadness. How many surprise elements book do have. It is useful to understand conversation, if it is more towards positive end or negative end.

Coding bits

It will make more sense while comparing.

As everything else in F# here we also start with type and start putting things in it. Let’s call it Book type. Because why not.

Now, for a second keep this aside. We need more details or here data to find out sentiments. Data with which we can compare our book terms. So, we will be using two data sets. For emotions we will be using this and for positive / negative ratings we will be using this.

Here are what they look like.

Emotion Lexicon:

And Word with Ratings:

Traditional way to pull data out of CSV file is for -> for -> for loops. But we are in F# land, we will be using csv Type Provider. Let's pull data out of CSV and shape it in types.

Here is the thing about this data. Emotion column is also specifying the emotion, not always but they are there. So, we need them too. That is reason for that extra calcution we are doing. Here for every emotion found we are adding 1 else it is 0.

If you can see I am not comparing with string but with concrete F# term. It is because in data we are having “anticip” for “anticipation”. Now, in future if we add another data to this collection and they have “anticipation” then it will add extra case for same result. So, it would be better to encapsulate them away. And clean way to do that using Active patterns.

Here is missing piece of code.

As we are having more than 7 cases, we will be using partial Active Patterns and join them in match statement.

Same can be done for word with Positive and Negative ratings.

Here is code for same.

Great. Now stage is set to convert books made of terms to books made of numbers. Let’s create for one book and then we will loop it for our array.

Single function and it’s done. That’s it. What we are doing in that? Creating our Book type.

Terms and Unique Terms were extracted away.

Little bit complicated looking part is where we are trying to find Sentiment Index for book. So, first step is clean up the word set. That is the reason we are using unique terms. All terms are not present in data set we are having. So, there is need to take common terms. Again no more loops and conditions. They are two sets we need common terms so just intersect it. One line without performance over head. Now find out Sentiment details for that word and to get for book just fold it and do the sum of it. Done.

So, we are having all the data in memory. In our case in FSI / REPL.

As we are official data scientist we required that we see things in Graph format. So, first let’s conver things to JSON and write to disk so we can use it.

Here I am using Fsharplu.Json, do check their project story.

Now, once JSON is ready we can easily use to show in graph using any graph library.

Here I did little cheating and wrote some dirty JavaScript. A good practise would be to write code in Fable. So, I will not show code of JavaScript part.

You can find book wise graphs here and transformed analysis here which is sentiment wise. Or Check out few of them below.

Book Wise:

Sentiment Wise:

Same can be done for positive and negative word set. (DYI for you.)

Reading the Graphs & Experience

One thing needed to be understand here. Data set are created by human, code is written by human and code is executed by dumb computer. So, there is and always will be little bit manual tweaking. As language is topic with perception. One need to understand culture / history of those words from where they are coming. Graphs should be read in that context only. Let me put an example here.

Check out word frequency graph here. Pick any graph. Here I am taking three graphs to compare.

“Great” would be always first. And “Fire” will come in last five always. In normal western literature “Great” word used as adverb for person or thing. But in Indian or Mahabharata context they use it to address someone. Like Hey, Great worrier Arjuna. A poetic way of saying things. Looks good but also make word totally useless in context of understanding phrase. This issue can be solved with Inverse Document Frequency but again it is an extra effort. Same goes for word "Fire". It is having negative value in normal context but in this specific context it is not that negative. Fire God and Fire it self (yagna) are positive. It is very much contextual.

But again generating graph is much more data sciencey to explain.

What’s Next

Next step would be doing more detailed analysis of this Epic. Compare number / analysis with original context of books. Try to push number as near as possible to words. And probably extract some good NLP library from it.

All books are divided in sub-books telling different stories. Wiki links are added in Table list. If you are interested then check them out.

Complete script file for this article is available over github.

Download your favourite books and have fun with graphs.

Thanks Note

Special Thanks to people without whom this project may not exist.

Rachel Reese — For arranging this season of Mentorship program.

Mentorship program : In simple words. It is a program where Mentor and Mentee are tagged with each other. And they have hour / week to teach / learn some topic specific to F#. As highly technical people things looks little old school but the effect that flesh and blood can create nothing else can. No books or no recorded videos. 45–60 minutes can cover more than one can cover in month or two using deal material. It is always good to have someone there alive in front of you whom you can ask questions. Again that is all my preference and what I like about this program.

Andrea — For last season of Mentorship program.

My lovely fiancée for not only allowing me but also encouraging me to give extra time to this.

Saheb to be my phone a friend for any kind of machine learning and data science queries.

Devdutt, my current favourite mythologist. Author of two of my favourite books Jaya and My Gita in this genre

Note to my Mentor

Words can’t explain how much grateful I am to have Evelina Gabasova as my mentor or may be guru would make much more sense in current context. After a long time I can have kid’s curiosity and innocence to ask anything and everything to her. And she is always there with answer and ever smiling face. Always pushing extra mile to beat the time zone differences.

In Mahabharata, Krishna narrate Gita to Arjuna in middle of war field; empowering him with eternal knowledge. Just like that,

Hey, Great Evelina, I am no Arjuna but you are always been my Krishne. Guiding my way in the flood of data. It is always good to have you around. Be as mentor and as friend. Please be there always.

Closing

I like to close with few of my favourite picture describing war moments of Mahabharata

Krishna narrating Gita to Arjuna

Krishna driving Arjuna in war field

Krishna, Arjuna and Bhisma three great warriors but helpless in front of time (situation)

Originally published at kunjan.in.

Epic Mahabharata was originally published in FuzzyCloud on Medium, where people are continuing the conversation by highlighting and responding to this story.