concept implementation in category data

This is an excerpt from Manning's book The Art of Data Usability.
The last question, about when you can expect an outcome, is important to think about both in terms of implementation and measurements. Gathering measurements for analysis can take a lot longer than the actual implementation. If you were changing a work process at a bakery, you can’t expect a great outcome in a single day; the bakers will have to get used to the new process. You let it run for maybe a month and then you can see if things improved. You need to know what period, the reference period, to compare your measurements against.

This is an excerpt from Manning's book Think Like a Data Scientist: Tackle the data science process step-by-step.
Compared to MATLAB, in R it’s easier to load and handle different types of data. MATLAB is good at handling tabular data but, generally speaking, R is better with tables with headers, mixed column types (integer, decimal, strings, and so on), JSON, and database queries. I’m not saying that MATLAB can’t handle these but that it’s generally more limited or difficult in implementation. In addition, when reading tabular data, R tends to default to returning an object of the type data frame. Data frames are versatile objects containing data in columns, where each column can be of a different data type—for example, numeric, string, or even matrix—but all entries in each column must be the same. Working with data frames can be confusing at first, but their versatility and power are certainly evident after a while.
Sure, you can always code the methods yourself, but if you’re using a fairly common method, then many tools probably already have an implementation, and it’s probably better to use one of those. Code that’s been used by many people already is usually relatively error free compared to some code that you wrote in a day and used only once or twice.