Featured post

3 Top Books Every Analytics Engineer to Read

Many of the analytics jobs nowadays are for the financial domain. The top financial domains are Banking, Payments, and credit cards. 
The Best Books are on:
SASUNIXPython

The skills you need to work in data analytics are SAS, UNIX, Python, and JavaScript.  I have selected three books for beginners of data analysts. 

1. SAS best book 
I found one best book that is little SAS. This post covers almost all examples and critical macros you need for your job.

The best-selling Little SAS Book just got even better. Readers worldwide study this easy-to-follow book to help them learn the basics of SAS programming.

Now Rebecca Ottesen has teamed up with the original authors, Lora Delwiche, and Susan Slaughter, to provide a new way to challenge and improve your SAS skills through thought-provoking questions, exercises, and projects.
2. UNIX best book
The basic commands you will get everywhere. The way of executing Macros or shell scripts is really you need. This is a good book so that you can automate…

JSON XML learn Today for data analytics jobs

JavaScript Object Notation (JSON) was invented by Douglas Crockford as a subset of JavaScript syntax to be a lightweight data format that is easily readable and writable by both humans and machines. In general, JSON is considered terse when compared to other interchange formats.

 After you become familiar with JSON, you will find it fairly easy to read complex JSON data structures. Even though JSON is based on a subset of the JavaScript programming language, it is considered language independent.

JSON XML

The flexibility of XML has made it increasingly prevalent in programming environments. Unlike the Unix® world, where configuration files are usually text files with either tab-delimited name/value pairs or colon-separated fields, configuration files in the open source world are often XML documents.

Most well-known application servers also use XML-based configuration files. The Ant utility relies on XML-based files for defining tasks.

Data Integration

A tremendous amount of data in the business world and scientific community does not use the JSON or XML format. To give you some perspective, roughly 80% to 90% of all software programs were written in either COBOL or Fortran™ in the early 1990s (and NASA scientists were still using Fortran in 2004).

Therefore, data integration and migration can be a complex problem. The movement toward XML as a standard for data representation is intended to simplify the problem of exchanging data between systems.

You probably already know that XML is ubiquitous in the Java world, yet you might be asking yourself one question: What's all the fuss about XML? In broad terms, XML is to data what relational theory is to databases; both provide a standardized mechanism for representing data.

XML Documents

A nontrivial database schema consists of a set of tables in which there is some type of parent/child (or master/detail) relationship in which data can be viewed hierarchically.

An XML document also represents data in a parent/child relationship. One important difference is that database schemas can model many-to-many relationships such as the many-to-many relationships that exists between a student's entity and a class's entity.

XML documents are strictly one-to-many, with a single root node. People sometimes make the analogy that XML is to data what Java is to code; both are portable, which means you avoid the problems that are inherent in proprietary systems.

Read more

Comments

Popular posts from this blog

Quick Comparison AWS Vs Azure Load Balancer

Hyperledger Fabric: 20 Real Interview Questions

10 Best Visualization Charts to Present data

JavaScript Vs JSON Top Differences