The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
As with anything else: it depends…
Looks like you’re in the US., so it’ll depend on what state you’re in, how much you have in assets, and how old you are.
If you’re 65 you’ll need to apply for Medicare.
If you have no assets and are under 65 you may be able to get Medicaid.
When I retired, I was under 65 and had too much in retirement savings to qualify for Medicaid, so I had to go to the healthcare exchange for my state. If your state doesn’t have it’s own exchange, then you’ll need to go to the Federal site.
In my case, if I had ‘some’ income (a low amount) the state would pay part of the premium. So I draw a minimal amount from my retirement account to show some income.
Again, it all depends.
Good luck. It’s complicated.
Time is the differentiation of eternity devised by man to measure the passage of human events.
- Manly P. Hall
I don't have any on purpose. I find it far easier to maintain a high level of health and fitness, and any pop-up issues can be paid out of pocket for less than a month's premium. I wish I could get a health savings account without also buying a policy, but that was only a dream even before the ACA ruined everything.
It's interesting to note that all medical procedures not generally covered by insurance (laser eye and plastic surgery) diminish in cost until they reach what the market will naturally bear, but when a third party pays costs soar because that market bears far higher price tags well in excess of actual cost or benefit.
So I've been bitching lately about BSODs and Microsoft and what have you. I have in the works a book about debugging problems. Chapter 1 is "Your assumptions are wrong."
I'm a big proponent of calling a turd a turd. Not to belittle anyone, but if you want to solve a problem you have to be honest. Own it. Your code is crap? Own it. you got lazy? own it. It's not personal it's reality. Part of that reality is admitting when you're an idiot.
I'm an idiot. JSOP go away.
I have worked on a high end laptop for almost 5 years. It's had heat issues, random crashes (careful with drivers), high cpu at times etc. When I bought it, I purchased the minimum RAM because oems always jack up the upgrades on order. So I ordered 2 32 GB SODIMMs, popped them in and 4+ years later support told me they were incompatible. In fact, I have 32GB under my keyboard that I never knew about.
Correct memory on order, we'll see what happens. if you want a good laptop with NA first person support, check out Eluktronics.
Jeesh, read the manual.
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
if you want to solve a problem you have to be honest. Own it.
Absolutely! If you don't acknowledge your mistake, you can't prevent it happening next time. Everybody makes mistakes: the measure of a person (or a company) is how you deal with it.
But having said that ... in development, the hardest lesson I had to learn was "this is not going to work, throw it away". The urge to tinker with almost working code is ... considerable. It very hard to admit "this whole idea was a mistake" and go back to what you had before. Microsoft has never, ever learned this lesson, which colours every product they produce.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
I have to work with a credit card processor outfit whose track history is not very good. Recently I blamed them for something, turned out it was my code. Time to reset the prejudice, lol. Not all the way, mind you, but I do need to tone it down a bit, if only for the sake of not embarrassing myself!
And yes, I owned my mistake, apologizing to all involved.
but not as ports, as connectors on the motherboard
Yeah, I guess port isn't the exact best word.
Here are some wordnik defs which probably describe port as an ok choice:
noun A porthole.
noun Archaic A cover for a porthole.
noun An opening, as in a cylinder or valve face, for the passage of steam or fluid.
noun A hole in an armored vehicle or a fortified structure for viewing or for firing weapons.
noun An entrance to or exit from a data network.
noun A connection point for a peripheral device.