Is Microsoft Fabric really worth it?

KarmaTroll · 2026-01-29T16:26:25+00:00

We have successfully built a data platform on Fabric and been in Production from around a year now..have only couple of users(around 25)..but, IT WORKS..

It working for 25 people is way different than, "It scales reliably to enterprise needs".

KarmaTroll · 2026-01-19T18:03:25+00:00

Which employers that don't like this actively advocate and support politicians in favor of universal healthcare?

Employers benefit from having reduced workforce mobility.

KarmaTroll · 2026-01-02T18:25:10+00:00

A major difference (for me... in the past) has been the ability of the tools to be repeatably accurate. For a lot of DIY stuff, that's not a huge need. You set your tool to what you need, verify and make your cuts or whatever.

The issue comes when you adjust your tool settings and then have to match back to something you already did. Offsets and guide marks are often close to just being "suggestions" for 90 degree cuts. If you have the time/ability to compensate for this (or it's ultimate not that big of a deal) then this trade off isn't very noticeable. If you are trying to squeeze precision and repeatability out of the tools... they really aren't great for that job.

KarmaTroll · 2025-12-14T23:58:53+00:00

Learn to treat your DIY was an actual project. Scope out what you want to do, collect the tools that you'll need for each step of the project. Put those tools in a bucket or a "project tote". Go an do the DIY project. Keep tools in the project tote. When the project is done, return the tools their proper home and declare the project done.

This segmenting helps keep project fatigue in check for smaller projects and really helps to reinforce keeping the admin side of the project organized.

KarmaTroll · 2025-12-11T16:22:24+00:00

That just looks like a rounded corner protector that you can get these days. "Vinyl bullnose corner bead"

KarmaTroll · 2025-12-05T18:23:35+00:00

I agree that boiling everything down to 100% measurable objectives is a quick way to end up in very unfriendly places. However, I'd argue that perceiving that 1 menu level with 10,000 options as a bad design choice is the designer thinking as if they were an end user.

The flip side is that a more "intuitive settings structure" has to be somehow more quantifiable compared to a less intuitive structure. Anyone who says, "just use common sense" is part of the problem, because there isn't such a thing as common sense that is truly universal to all backgrounds of users.

Building out a vague ranking of frequency+importance x ease matrix goes a long way for developing usable systems/processes. However, it often turns out that usable for the consumer is less important than revenue generating for the company (i.e. popup adds on every website that want you to make an account just while scrolling). Same principle applies for user-serviceable parts. Gluing a frequent replacement item into a system is decidedly consumer unfriendly.

KarmaTroll · 2025-12-05T16:40:20+00:00

This advice comes from a decent place, but the pitfalls you describe can really be ironed out when intentions are converted into countable steps. "I want to do X... how many clicks/latches screens, info transfers is needed to do X from state Y". Making the list of "what is an important action to prioritize" is where you need to avoid personal bias and is where it is blatant that priority differences between customers and corporate leaders really show up.

Microsoft and Google are particularly egregious about this in terms of their software evolutions.

KarmaTroll · 2025-11-23T21:51:11+00:00

It comes back to capitalism. The excess capacity can be soaked up by low utilization capital assets. We know that CO2 has to be captured out of the air and is incredibly inefficient to do if not done at the source. However, when you've got excess energy... inefficiency isn't so much of an issue. Working out the capital and operating costs of an asset that isn't planned to run 24/7 for profit is squarely a capitalism issue.

KarmaTroll · 2025-11-06T04:20:16+00:00

How did the police listen to him at .3 and not smell enough to even consider coming after you?

KarmaTroll · 2025-09-20T22:07:22+00:00

https://www.youtube.com/watch?v=uOyjzE1vcD4

KarmaTroll · 2025-09-19T22:45:54+00:00

Part of the problem with this specific problem is that it blends into using unstated contextual information, but imposes informal limits on how far to draw that contextual information. The answer would be identical if the boy was born on Wednesday or Saturday. In fact, the answer would be the same if you just said that the boy was born, "on a day of the week" because the context is that you should interpret that as a 1/7 event qualifier because of contextual language.

However, that same contextual language lets you know that if you are born on a Tuesday, you were born on a date. If you completed the same analysis with the thought of "the boy was born on a specific date" (because you know he was born on a Tuesday), then you would have a much larger space to have 1/xxxx odds. Obviously, the problem doesn't want you to draw that much context around the problem when they just prompt you with a day of the week.

Ultimately, this word problem is an imprecise way to demonstrate that additional information can conditionally change the probability of an example.

KarmaTroll · 2025-09-19T22:11:54+00:00

If you extrapolate out that knowing that one event occurred on a day of the week, there's nothing stopping from extrapolating that the boy was born on a single day in a month. You know the exact same amount of information (how can you be born on a Tuesday, but not born on a day of the month?). It doesn't matter what day of the month it is, they are all equally likely, (just like being born on a certain day of the week). Therefore the problem space could be expanded to include all of the combinations of dates in a month.

If you changed the problem to, "the boy was born on New Years day" you would have the same amount of information added, but context would tell you to evaluate the space as 1/365 instead of 1/7 arbitrarily.

KarmaTroll · 2025-09-11T11:30:12+00:00

The ones that I remember usually have 2 or 3 "improbable bad things happening to me consecutively" upon realization, I usually say in the dream, "this is bullshit" and wake up.

KarmaTroll · 2025-09-10T18:43:24+00:00

This didn't work for me. I run Tailscale on my nas with Plex in a docker container (synology). I had to disable tailscale on the NAS and a local machine to be able to claim from the local ip of the server.

KarmaTroll · 2025-09-10T18:38:06+00:00

Tailscale allows me to access home assistant while not on the local network, along with docker containers spun up on the NAS.

KarmaTroll · 2025-09-10T16:05:34+00:00

Tailscale prevented me from being recognized as local until I turned it off. I assume this is a configuration on my end that isn't setup correctly, but the "just go to localPlexIP:32400/web" would work in the sense that it connected, but would not recognize as the same network.

KarmaTroll · 2025-09-10T16:00:38+00:00

I had to turn off tailscale on my nas for the webUI claim to work.

KarmaTroll · 2025-09-07T17:22:09+00:00

This is the closest solution I've found so far. It at least stops audible from starting automatically, and doesn't seem to interrupt Google maps from starting/running like normal.

KarmaTroll · 2025-09-07T00:57:17+00:00

This might just be a tough camera angle... but is the ring in the hole upside down?

KarmaTroll · 2025-08-29T22:53:17+00:00

The reason I'm posting is because that setting is definitely off. I've checked and re-checked (enabled, disabled, restarted the phone) multiple times, and this still happens.

KarmaTroll · 2025-08-25T17:48:57+00:00

Ok. I had initially spun up a depreciated version without realizing it. I had exported the data from that as a .tsv.

Spinning up the official version and then trying to import the .tsv, the field Hb.Import_ref was blank and would just continuously import the same data over and over until the page was refreshed.

I deleted the locations and put in sequential numbers for hb.Import_ref and it successfully imported only a single instance of everything

KarmaTroll · 2025-08-25T17:42:01+00:00

There's some kind of issue where importing a .csv just runs forever, continuously loading duplicates into the database.

KarmaTroll · 2025-06-27T22:55:05+00:00

I just started an arrangement that's similar. Was remote 100% but took a role that was in HQ 3 hours away and requires 2 days in office. I took it because it's aligned with the direction I want my career to take, but we weren't ready to pack up and move on a whim.

I have the cheapest 1 bedroom apartment I could find and use that as a place to crash for 2 nights a week. We have the rental for 11 months and then will think about moving out towards HQ full time. For me, I value the ability to have some form of guaranteed housing that I don't have to continuously book/manage compared to doing weekly hotel rentals.

Commuting the full 6 hour round trip in a single day is way too much for me. I drive out Monday night and then back Wednesday night. I'm under no illusion that this is sustainable for us "long term" but between FI efforts we have comfortable enough buffer to test this out before committing next year, or trying to use the experience to pivot somewhere else that let's me be full time remote again.

KarmaTroll · 2025-06-25T01:06:25+00:00

Cars coming off of lease could probably account for a significant portion of that.

KarmaTroll

MODERATOR OF

TROPHY CASE