Skip to main content

Power BI Journey: Blog #8



It is finished! The second to the last vlog talked about the different visualizations and when they are appropriate to be applied while the last vlog was about the final project which utilized all the lessons learned from Vlog 1 up to now. And, here is my final output.



In the above dashboard, we can see some demographics as indicated by the 630 total survey participants with an average age of 29.87 years old. We can also see that data scientist has the highest average salary ($94k) followed by data engineer ($65k) then data architect ($64k) among data professionals. We can also see that the favorite programming language of  data professionals is Python, followed by R and other programming languages and the distribution of data professionals in each of the given programming languages. For example, for those who selected Python as their favorite programming language, 255 of those were data analyst, 54 are either a student or still looking for a job or no job at all, while 54 have other job titles. We can also observe that a significant number of data professionals found it neither easy nor difficult to transition to becoming a data professional, followed by those who found it difficult and then followed by those who found it easy. Work-life balance is at 5.74 while salary satisfaction is at 4.27. This means that, on average, data professionals have above average work-life balance and a below average salary satisfaction.

What I found interesting in the final project is that whenever I click the country of origin, all the data pertaining to that country of origin will be displayed. It shows that the dashboard varies depending on your preferences. For example,



In this case, I selected the country of origin for survey participants in India. Here, we see that there are 73 survey participants and the average age of those who participated in the survey is 27 years old. We can also see that still the highest average salary in India are data scientist ($68k) followed by data engineer ($52k) then others ($27k) among data professionals. We can also see that the favorite programming language of  data professionals is Python where 31 data analyst reported utilizing the said programming language. Work-life balance is at 4.79 while salary satisfaction is at 3.51. This means that, on average, data professionals have below average work-life balance and a below average salary satisfaction. These numbers are comparably lower than the average work-life balance and salary satisfaction for all countries.

I am amazed by this platform and the possibilities it could make with data. Can't wait to apply this on a real-world data and work as a data professional. Maybe take this survey in the nearest future. Thank you Alex the Analyst.

Comments

Popular posts from this blog

Privacy Policy of ShinStats: descriptives calc

Privacy Policy Shin Nix built the ShinStats app as an Ad Supported app. This SERVICE is provided by Shin Nix at no cost and is intended for use as is. This page is used to inform visitors regarding my policies with the collection, use, and disclosure of Personal Information if anyone decided to use my Service. If you choose to use my Service, then you agree to the collection and use of information in relation to this policy. The Personal Information that I collect is used for providing and improving the Service. I will not use or share your information with anyone except as described in this Privacy Policy. The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, which are accessible at ShinStats unless otherwise defined in this Privacy Policy. Information Collection and Use For a better experience, while using our Service, I may require you to provide us with certain personally identifiable information. The information that I request will be retaine...

SQL Journey: Blog#10

So far, we are only "reading" from a given database or table using the SELECT command of SQL. In today's lesson, we will now start "writing" into a given database using the UPDATE and DELETE commands. Challenge: Dynamic Documents Given data: CREATE table documents (     id INTEGER PRIMARY KEY AUTOINCREMENT,     title TEXT,     content TEXT,     author TEXT);      INSERT INTO documents (author, title, content)     VALUES ("Puff T.M. Dragon", "Fancy Stuff", "Ceiling wax, dragon wings, etc."); INSERT INTO documents (author, title, content)     VALUES ("Puff T.M. Dragon", "Living Things", "They're located in the left ear, you know."); INSERT INTO documents (author, title, content)     VALUES ("Jackie Paper", "Pirate Recipes", "Cherry pie, apple pie, blueberry pie."); INSERT INTO documents (author, title, content)     VALUES ("Jackie Paper", "Boat Supplies...

SQL Journey: Blog #14

I am now on what Alex the Analyst would call the advanced SQL queries. First off, the Common Table Expression or CTEs. Based on what I understood in the video, CTEs is similar to a function or class in Python which you can call out. It is just how I felt when I first encountered this expression. Now, in this particular case, I tried to replicate what Alex is doing but also not copying the codes that he is using. I am just simply trying to understand what the expression that was used (which starts with WITH) and then observe how he used the said expression. This was my code. Now this code, resulted in the following error. Msg 8156, Level 16, State 1, Line 84 The column 'EmployeeID' was specified multiple times for 'CTE_Employee'. What does someone do in this day and age if we encounter something that bogs us down? We go to the internet especially to AI tools to aid us out. And, apparently, these tools will really come in handy. It stated that the error occurred because I...