The discussion at 37:30 is a bit naive. This usually happens because tools like this require a development mindset, therefore they give developer power, productivity and prestige to people who are not in the IT department - and the IT department, by its own definition, has a monopoly on development (this is a gross simplification, but that's the effect). The answer is to resign and return as an external consultant with your own laptop on BYOD.
Very good point - I never considered this aspect. Having worked on both side, my view (as an external consultant BTW) is that IT tries to avoid complications made by user. Staying in control could be something they never openly shared with a consultant. I wouldn't say this affects all the large companies, but it certainly could be the unspoken truth in several cases!
@@marcorusso7472 That's it exactly. They won't tolerate something they can't support internally - there was a popular LinkedIn post just last week about how vital it is not to let "users" automate work with Power Query, Power Pivot, and so on, because it would only create "problems" for IT which were self-evidently worse than the users doing all the work by hand. I do this kind of automation all the time as an external, then I document what I've done and I teach the employees to maintain it, if the client will let me. But in practice I'm almost always working in Excel alone, both because it's accessible to the finance people I'm usually working with, and because it's uncontroversial. (Edit to clarify: Power Query and DAX are stunningly useful, but decision maker incentives often aren't aligned with results).
@@subjectline Interesting. Could you share the link to that LinkedIn post? I wholeheartedly disagree that letting users go wild with Power Query, Power Pivot, etc. would cause more/worse problems for IT. The thing is that users will always find a way to achieve their goals - and the alternative is much much worse. We've seen it before: Excel hell with VBA macros, MS Access databases, etc. It's much better from an IT perspective, to give them tools that do the job in a more streamlined and productive way - and tools like Power Query even provide some degree of control for an IT organisation, like the online lineage view, ability for Power BI admins to certify datasets, etc.... nothing like that is possible in Excel hell.
@@DanielOtykier to my regret, I didn't save the post - I wanted to avoid the temptation to get into an argument. It wasn't someone in my immediate network, it just popped up in the feed!
@@user-qq2dg3hz4o Probably because you need x86-based Windows to run DAX Studio and Power BI Desktop, at least until Windows ARM officially supports 64-bit emulation.
If you are using Azure services, then you can build a VM which acts exactly like a PC with Windows installed. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-k0645eXL0oc.html
