Interactive Data Story of Forbes Top 100 Celebrities

-
When looking at the table of "The World's Most Powerful Celebrities", compiled by Forbes, it is hard to get insights like the relationships between celebrities and the factors they are ranked by. 


I decided to create a project using D3.js to do some exploration. 

 In the project I tried to find how the celebrities' social networking power related to their marketability. I grabbed the data from Forbes. I added categories (Actors, Actresses, Athletes, etc) so certain groups can be compared with each other. Hovering over the points revealed their names and jobs. (Labels by each point would be too cluttered.) 

Here is the story from the data ...
Actors and actresses overall are very marketable with the exceptions of Kristen Stewart and Tom Cruise, as can be seen by hovering over each of their points:

As a group, actors have more social networking power than actresses, and are slightly more marketable. 

 Now let's take a look at directors and producers: 



Directors and producers generally have less social networking power and less marketability than actors and actresses, which makes sense. Exceptions are Steven Spielberg, Seth MacFarlane, and Tyler Perry. 

Athletes appear to be less marketable overall, which is a little unexpected: 
Now, looking at the personality category: 

This category is one of the most scattered categories. However, it looks like the more social networking power a personality has, the more marketable they are. Examples are Oprah Winfrey and Ellen Degeneres, who both have a lot of social networking power and are very marketable. 

 A notable exception is Kim Kardashian, who has a large amount of social networking power, but not a lot of marketability: 
These are just a few of the insights from the data. Though I expected some patterns, many were surprising! 

 Data can not only be represented in numbers, but also in lines and colors. D3 makes it fun to experiment with data and tell a story.

Popular posts from this blog

Building A Toy Language Interpreter in Go

-
Image
In this post, I'll be giving a high-level overview of interpreters, why they're interesting, and how they work. I'll be referencing my repo, go_interpreter , which is a simple interpreter written in Go for a toy language. The figure below shows the structure of our interpreter with an example input: What is an interpreter?  An interpreter is a language processor that seems to directly execute the source program on user input: In contrast, a compiler first takes in a source program and translates it to an executable machine code target program. Then, the user can pass in inputs to this target program and get outputs. In general, an interpreter is better at reporting errors since it's processing statements one at a time, and a compiler is faster at generating outputs from inputs. In this post, we're going to go over a simple interpreter that is capable of supporting: integers, booleans, strings, arrays, hashmaps prefix, infix operators index opera
Read more

Space Race: a simple Rust game built on the Bevy framework

-
Image
When I saw a post announcing the release of the Bevy framework  (an open source game engine written in Rust), I thought it'd be a fun way to learn Rust.  So I made Space Race , a 2 player game on top of the Bevy framework. How to Play The Astronaut moves around collecting jewels (using WASD keys). The Alien moves around trying to catch the Astronaut (using arrow keys).  The Astronaut wins if they collect at least 5 jewels and make it back to home base before the Alien catches them.  The Alien wins otherwise.  Things I learned about Rust  I had a lot of fun making & playing this game, and also got some hands on experience with Rust like working with structs enums vectors iterators traits dyn trait vs impl trait  dyn trait is used for trait objects, which are fat pointers made up of 1) a pointer to the value 2) a pointer to a vtable. A vtable is a table of methods, where each method points to its implementation, generated once at compile time. Each instance of a type that impleme
Read more

Building a Toy Language Compiler in Go

-
Image
A follow-up to my previous post about building a toy language interpreter in Go. Throughout this post, I'll be referencing my repo . We'll go over a compiler which translates source code to machine code, and then a VM to execute this machine code. What is a compiler?  A compiler takes source code and translates it to executable machine code . (See my previous post for more details.) The figure below shows the high-level architecture of a simple compiler. Like the interpreter we built previously, our compiler has a lexer and a parser which turn our source code into an AST . This is our compiler's frontend . However, that's where a compiler diverges.  The compiler may translate the AST into at least one internal representation (IR) . The IR(s) may be represented using any data structure (even another AST!), but they should follow two rules: (1) be easy to produce, (2) be easy to translate into the target machine code. The IR can also be optimized
Read more