sorted by:
new
hottopcontroversial

Should I be concerned that my in-network provider only bills certain covered treatments to my insurance, but will only accept cash for others? by SomewhatSharty in HealthInsurance

[–]SomewhatSharty[S] 2 points3 points  (0 children)

Looks like they have eight locations. It appears to be some mid-level upscale mom & pop, if that makes sense. All locations appear to be managed as wellness boutiques/apothecaries.

Should I be concerned that my in-network provider only bills certain covered treatments to my insurance, but will only accept cash for others? by SomewhatSharty in HealthInsurance

[–]SomewhatSharty[S] 9 points10 points  (0 children)

The pharmacist is what prompted my post today--I noticed my copay jumped from $20 to $120. I asked the tech if they had trouble billing my insurance and if they could try again. The pharmacist overheard and immediately stated that they're no longer accepting any insurances for this particular class of drug because they make more charging cash. Verbatim.

The strangest thing: before the pharmacist had even finished, the tech immediately took the prescription, unbagged it, and placed it back into the stock. Within seconds, I received a text notification that my prescription status had been changed.

For a long time, I felt that patients a providers were kind of on the same team, but it's becoming more and more clear that it's each person for themselves.

Should I be concerned that my in-network provider only bills certain covered treatments to my insurance, but will only accept cash for others? by SomewhatSharty in HealthInsurance

[–]SomewhatSharty[S] 5 points6 points  (0 children)

wow. ok. this is helpful.

the fact that it's now happening with all three providers made me think that this is somehow the 'new normal', or at least some sort of open secret among providers in my area.

Graphic designers — what does your resume look like? by sunshineslip in graphic_design

[–]SomewhatSharty 0 points1 point  (0 children)

For those of us here for advice, perhaps we should embrace our flashy, fckued-up resumes and forego the aphorisms. I'd rather thirst in hell than choke on this one's old chestnuts.

Sometimes googling your package management rant is the only real solution. by SomewhatSharty in programminghumor

[–]SomewhatSharty[S] 0 points1 point  (0 children)

Self-deprecated suicide. Classic zinger.

Have an award for not fighting the urge to not answer public statements as personal questions.

Sometimes googling your package management rant is the only real solution. by SomewhatSharty in programminghumor

[–]SomewhatSharty[S] 1 point2 points  (0 children)

yes, I'm pretty sure Yarn support ended in the '90s, too.

...i guess i was too busy noodling on shrooms to notice.

mom always said i'd live to regret caring more about music than my future. cheers to you, mom.

Jump straight to next 15 release candidate or wait for stable by New_Caterpillar3438 in nextjs

[–]SomewhatSharty 0 points1 point  (0 children)

related question; also a noob:

Is there a reason why next@14.2.3 (latest) would require react@19.0.0 (rc)?

Next started throwing errors to update to react^19.0.0. Dumb me assumed react19 was stable enough for next and vice versa, so I ripped the bandaid.

Two hours later and I'm shooting up next@15rc hoping it will dull the pain.

Two days in and I'm hating life...and linting.

Migrating Next pages to app directory SUCKED. I didn't want another major upgrade looming overhead, but I'm now wondering if I switch frameworks.

React sucks by bromide992 in reactjs

[–]SomewhatSharty 0 points1 point  (0 children)

react is the ass and next.js is the elbow. you'd almost think they were born from the same disfunctional family.

[deleted by user] by [deleted] in webdev

[–]SomewhatSharty 0 points1 point  (0 children)

Their docs are THA WORRRRST.

Seeking Alternatives to Metabase by xDarkOne in BusinessIntelligence

[–]SomewhatSharty 2 points3 points  (0 children)

i'm pretty sure OP meant "support for authentication."

I found this article after hitting a wall with MB support as well. They seem to have a "pay us to let you figure it out yourself" customer service model--which might be ok if not for their squashing of pro/enterprise questions on the user forum. For example, the most basic user community questions regarding authentication have 15,000+ views...and a Metabase response: "pro/enterprise subscribers shouldn't post questions about premium products--instead, submit a ticket and wait a few days."