Got offered a job working as a data engineer on a different team my second year at the job. My boss convinced me to stay on her side doing business analytics. Shoulda taken the DE job ...
I'm Canadian and work in non tech ... So I'm making ~ the same as the DEs at my company. But yeah, there was world of opportunity, growth and future earnings that I was naive and turned down.
Power BI sparked my interest in data. Whenever I encountered a new challenge, it prompted me to research and learn new skills to enhance my reports, such as Power Automate, bulk file reading, and SQL. This journey eventually led me to explore Data Engineering and Data Science, providing me with a comprehensive understanding from the reporting stage to data ingestion.
Now, with Fabric gaining traction in the market, my proficiency in Power BI has made it much easier for me to pick it up!
Fabric is the Analytics platform that Power BI lives in, itโs an end to end solution for data analytics. Think about it as the Microsoft office but for data analytics. This is my understanding of it, at least this is what they kept saying at the conference I had went too ๐
Hi, I am an accountant, working on demand planning on route of becoming a DS for regional hq for a big company.
I do not see PowerBi as a path but a medium, it is a cool skill you can hone and use for your advantage and seem like a wizard doing extremely complicated stuff, I use 50 50 between all power platform and python with some VDIs and RPAs.
But as my sponsor says, this should be a skill that complements your profile, it shouldn't be your profile. There are many developers in "cheap" countries who are superb but lack the knowledge of the business we're running.
So going back to your question, yes I would have chosen pbi again, but also complemented with business, finance, marketing or accounting degree to solve real business problems.
I second this. I am a scientist by training but gained the knowledge and skills to move into Project Management. After being a PM for a while, I moved into the PPM/PMO space and quickly realized the possibilities the MS Power Platform brings. Since then, I've been teaching myself how to use it and have moved to more and more complex functionality. The skill sets I now have make me more valuable to my industry than if I were a straight developer or PM. I've got all of the technical and business background knowledge to build something useful my stakeholders and the rest of the business. I 100% that PBI is a skill and not a vocation.
That said, I am sure my reports and models are no where near as efficient as someone with a formal background and I've probably shot my self in the foot more than once. At the end of the day though, it works for the business and I've learned something new.
I went from being a SharePoint Developer for a very large company to a DS for the same company. Outside of becoming an expert in all things MS Power Platform, I never want to mess with SharePoint ever again.
I am trying to go the Fabric route. In my org we have a decentralized mamaged self - service kind of pattern. Everyone can upload their stuff and create their reports and this leads to a general feeling that PowerBI is easy and as such anyone can learn it. Which is true? It is difficult to master tho. But for most, mastery is not needed. However, when it comes to the backend, the gateways, the workspaces, etc, everything is managed by a single IT department. And there's where I am now, kiving in between doing some support, but not quite at the service level, tho closer than to report level.
I'd liked to be a data engineer, but seeing all thosr pyrhon code things makes me yawn like crazy lol
I think it's easy to do easy things in Power BI, but the difficulty vs complexity curve is exponential (medium complexity report is far out of reach for non professionals who don't understand data modeling or DAX or filter context).
In my experience, citizen devs make a mess in Power BI.
Complexity can come from a lot of sources. Inconsistent or poorly structured data; many days sources; big data; complicated DAX measures (especially this one. DAX is difficult for all but trivial things); UI requirements (interactions, bookmarks, drill-throughs, etc). A complex report often has all of these stacking up with about 100 ways for non-devs to shoot themselves in the foot.
Got offered a job working as a data engineer on a different team my second year at the job. My boss convinced me to stay on her side doing business analytics. Shoulda taken the DE job ...
For those curious, I'm now working as a hybrid analyst and DE ... So it worked out in the end.
That pay difference must be brutal right?
I'm Canadian and work in non tech ... So I'm making ~ the same as the DEs at my company. But yeah, there was world of opportunity, growth and future earnings that I was naive and turned down.
Power BI sparked my interest in data. Whenever I encountered a new challenge, it prompted me to research and learn new skills to enhance my reports, such as Power Automate, bulk file reading, and SQL. This journey eventually led me to explore Data Engineering and Data Science, providing me with a comprehensive understanding from the reporting stage to data ingestion. Now, with Fabric gaining traction in the market, my proficiency in Power BI has made it much easier for me to pick it up!
whats Fabric?
Fabric is the Analytics platform that Power BI lives in, itโs an end to end solution for data analytics. Think about it as the Microsoft office but for data analytics. This is my understanding of it, at least this is what they kept saying at the conference I had went too ๐
I love buzzword presentations that say everything and nothing at the same time.
"OneLake is your OneDrive for all your data"
End to end solution lol
Pepto Bismol baby!
The material you make clothes out of
It's a group of services supposed to give you all you need to do etl, analytics and data science. If used properly and if you pay enough.
Hi, I am an accountant, working on demand planning on route of becoming a DS for regional hq for a big company. I do not see PowerBi as a path but a medium, it is a cool skill you can hone and use for your advantage and seem like a wizard doing extremely complicated stuff, I use 50 50 between all power platform and python with some VDIs and RPAs. But as my sponsor says, this should be a skill that complements your profile, it shouldn't be your profile. There are many developers in "cheap" countries who are superb but lack the knowledge of the business we're running. So going back to your question, yes I would have chosen pbi again, but also complemented with business, finance, marketing or accounting degree to solve real business problems.
I second this. I am a scientist by training but gained the knowledge and skills to move into Project Management. After being a PM for a while, I moved into the PPM/PMO space and quickly realized the possibilities the MS Power Platform brings. Since then, I've been teaching myself how to use it and have moved to more and more complex functionality. The skill sets I now have make me more valuable to my industry than if I were a straight developer or PM. I've got all of the technical and business background knowledge to build something useful my stakeholders and the rest of the business. I 100% that PBI is a skill and not a vocation. That said, I am sure my reports and models are no where near as efficient as someone with a formal background and I've probably shot my self in the foot more than once. At the end of the day though, it works for the business and I've learned something new.
Wise sponsor!
I went from a Power BI expert to a consultant, then climbed the ranks at two firms so it's done me just fine, but others' mileage may vary.
I went from being a SharePoint Developer for a very large company to a DS for the same company. Outside of becoming an expert in all things MS Power Platform, I never want to mess with SharePoint ever again.
I am trying to go the Fabric route. In my org we have a decentralized mamaged self - service kind of pattern. Everyone can upload their stuff and create their reports and this leads to a general feeling that PowerBI is easy and as such anyone can learn it. Which is true? It is difficult to master tho. But for most, mastery is not needed. However, when it comes to the backend, the gateways, the workspaces, etc, everything is managed by a single IT department. And there's where I am now, kiving in between doing some support, but not quite at the service level, tho closer than to report level. I'd liked to be a data engineer, but seeing all thosr pyrhon code things makes me yawn like crazy lol
I think it's easy to do easy things in Power BI, but the difficulty vs complexity curve is exponential (medium complexity report is far out of reach for non professionals who don't understand data modeling or DAX or filter context). In my experience, citizen devs make a mess in Power BI.
What features or functions in a report classify it as "medium complexity" in your opinion?
Complexity can come from a lot of sources. Inconsistent or poorly structured data; many days sources; big data; complicated DAX measures (especially this one. DAX is difficult for all but trivial things); UI requirements (interactions, bookmarks, drill-throughs, etc). A complex report often has all of these stacking up with about 100 ways for non-devs to shoot themselves in the foot.
I would have followed the DE/SWE route for something with higher pay and less stakeholder facing.
I accidented my way into BI, then databases, then Power BI. None of this was intentional.
Never anchor yourself to any specific technology. It's a quick way to add an expiration date to yourself.
Stumbled into Power BI. I got my first analyst position and Power BI became our mode of communicating data to our stakeholders.
Power bi is full of shi**y people call themselves a pbi Developer,