TheHarpyEagle @ Theharpyeagle @lemmy.world

Posts

0

Comments

620

Joined

2 yr. ago

Anyone can wear makeup or nail polish or wear a skirt, doesn't say anything about their sexuality. Nor do all gay men do those things (I'd hazard that most don't).

To clarify, the paper (and rock underneath it) are not the structural part of the house, they just cover the actual structural parts (the studs) and provide a pocket to fill with insulation.

The biggest issue would be muscle atrophy. Even if you're pretty sedentary, your muscles are doing a lot of work each day just to move you around. Being bedridden for even a few days can cause muscle loss. You also increase the risk of blood clots and bed sores.

Medically induced comas also come with risk of permanent injury or death, so they really only do them in absolute emergencies.

And lastly, there are already surgeries and medications for weight loss that work much faster. The issue is, without matching lifestyle changes, all that weight will just come back.

Indeed, I hate it when people are like "you shouldn't pay that much, you need to shop around". Assuming you even have multiple hospitals to choose from, tell me you don't get "I don't know" 9/10 times when you ask about the cost of a procedure.

It's pretty confusing, but basically your insurance won't cover much until you meet your deductible for the year. After that, your coverage depends on the policies of your insurance company. Some stuff may be totally covered, some partially, some not at all. And there's really no way to know what costs what until you get it done.

Musk testified during the compensation trial in November 2022 that the money would be used to finance interplanetary travel.

“It’s a way to get humanity to Mars,” he testified. “So Tesla can assist in potentially achieving that.“

Yeah but you're not thinking of the BIG picture here, the very realistic goal of terraforming Mars and leaving all those poor sods behind.

There's many ways to point out the issues with the patch without being a jerk. The patch wouldn't have made it in either way, and maybe there could've been more useful conversations about the concerns (re: tar) that were brought up in the previous message.

Meh, maintainability is king. Sticking to the letter of the style law is probably not necessary, but ignoring badly structured code now is going to bite you in the ass when it comes time to change any of it.

Methinks more people need to read The Jungle.

Same, I feel like I never have enough time to do what I want. To have the time to indulge in all my hobbies, that's the dream.

I'm gonna guess this is mostly a ploy for registrations, so here's the full article text.

In an episode of “The Sopranos”, a popular television series which started airing in the 1990s, a gangster tells Tony, from the titular family, that he wants to retire. “What are you, a hockey player?” Tony snaps back. Non-fictional non-criminals who are considering an end to their working lives need not worry about broken fingers or other bodily harm. But they must still contend with other potentially painful losses: of income, purpose or, most poignantly, relevance.

Some simply won’t quit. Giorgio Armani refuses to relinquish his role as chief executive of his fashion house at the age of 89. Being Italy’s second-richest man has not dampened his work ethic. Charlie Munger, Warren Buffett’s sidekick at Berkshire Hathaway, worked for the investment powerhouse until he died late last year at the age of 99. Mr Buffett himself is going strong at 93.

People like Messrs Armani, Buffett or Munger are exceptional. But in remaining professionally active into what would historically be considered dotage, they are not unique. One poll this year found that almost one in three Americans say they may never retire. The majority of the nevers said they could not afford to give up a full-time job, especially when inflation was eating into an already measly Social Security cheque. But suppose you are one of the lucky ones who can choose to step aside. Should you do it?

The arc of corporate life used to be predictable. You made your way up the career ladder, acquiring more prestige and bigger salaries at every step. Then, in your early 60s, there was a Friday-afternoon retirement party, maybe a gold watch, and that was that. The next day the world of meetings, objectives, tasks and other busyness faded. If you were moderately restless, you could play bridge or help out with the grandchildren. If you weren’t, there were crossword puzzles, TV and a blanket.

Although intellectual stimulation tends to keep depression and cognitive impairment at bay, many professionals in the technology sector retire at the earliest recommended date to make space for the younger generation, conceding it would be unrealistic to maintain their edge in the field. Still, to step down means to leave centre stage—leisure gives you all the time in the world but tends to marginalise you as you are no longer in the game.

Things have changed. Lifespans are getting longer. It is true that although the post-retirement, twilight years are stretching, they do not have to lead to boredom or to a life devoid of meaning. Once you retire after 32 years as a lawyer at the World Bank, you can begin to split your time between photography and scrounging flea markets for a collection of Americana. You don’t have to miss your job or suffer from a lack of purpose. If you are no longer head of the hospital, you can join Médecins Sans Frontières for occasional stints, teach or help out at your local clinic. Self-worth and personal growth can derive from many places, including non-profit work or mentoring others on how to set up a business.

But can anything truly replace the framework and buzz of being part of the action? You can have a packed diary devoid of deadlines, meetings and spreadsheets and flourish as a consumer of theatre matinees, art exhibitions and badminton lessons. Hobbies are all well and good for many. But for the extremely driven, they can feel pointless and even slightly embarrassing.

That is because there is depth in being useful. And excitement, even in significantly lower doses than are typical earlier in a career, can act as an anti-ageing serum. Whenever Mr Armani is told to retire and enjoy the fruits of his labour, he replies “absolutely not”. Instead he is clearly energised by being involved in the running of the business day to day, signing off on every design, document and figure.

In “Seinfeld”, another television show of the 1990s, Jerry goes to visit his parents, middle-class Americans who moved to Florida when they retired, having dinner in the afternoon. “I’m not force-feeding myself a steak at 4.30 just to save a couple of bucks!” Jerry protests. When this guest Bartleby entered the job market, she assumed that when the day came she too would be a pensioner in a pastel-coloured shirt opting for the “early-bird special”. A quarter of a century on, your 48-year-old columnist hopes to be writing for The Economist decades from now, even if she trundles to her interviews supported by a Zimmer frame; Mr Seinfeld is still going strong at 69, after all. But ask her again in 21 years.

Joining via server invites that guide you through sign up, no dedicated server to host (I know, major downside for people who don't want all their stuff centralized to Discord's servers), GUI server admin tools, etc.

I think devs tend to vastly overestimate how tech-savvy the average person is. Bring up hosting, DNS, port forwarding, terminal, etc. and they're going to nope out pretty quick. Provide an option that lets you do everything from a single GUI and they'll use it. Enough people use it and eventually the tech-savvy folks have to follow because that's where everyone is.

That's absolutely not to say that it's a good medium for documentation. I will always prefer well-written and organized docs first and searchable forums/issue trackers/SO second. But that second group has a lot of tech elitism and devs who are (perhaps justifiably) short on patience, so Discord seems a lot more accessible to newbies who are asking the most basic questions.

I'm trying to get my feet wet in FOSS by making small doc PRs since I'm way too scared to actually touch code. It's not fun, but it is satisfying.

If it's open source and the license allows it, I wouldn't consider that stealing. If a fork gets more popular than the original, then it either addresses a major missing feature of the original or is simply more active. If this displeases the original dev, they can hopefully work it out with the maintainers of the fork. This is a feature of FOSS, not a bug.

Black hair often tends to be more coarse, dry, and curly than others' hair. A lot of black hairstyles are meant not only as source of self expression, but also to promote moisture retention, scalp health, and cleanliness since frequent washing can easily strip oil from the hair and damage it. It also helps protect the long but brittle hair against breakage.

Unfortunately, there's a long history of black hair styles being seen as "messy" and "unprofessional" in the US, owing to our colonial past. Many people don't really understand black hair care and believe the same rules apply to all kinds of hair, requiring or at least implying that hair should be relaxed/straight in a professional setting and anything else looks "nappy", unkempt, or "ghetto".

This is the feeling we get when seeing the rule about length when hair is "let down", the idea that, should George not wear this particular style, his hair would hang down to his shoulders. That's just not how that kind of hair works, so why is that kind of measurement being applied? "Length" is not deterministic for that kind of hair (ever seen someone before and after they pick their hair?) so the rule seems rather arbitrary. Is this rule applied equally to students with looser curly hair that naturally sits above their hairline when, if straight, it would drop over their eyes? How about people who wear a fro that can be pulled down to their shoulders? His hair is not to his shirt collar or over his ears, nor could it easily become so during the school day, so what exactly is the problem with it? It feels like this rule has been arbitrarily enforced in this case not because of the length of his hair, but because of the particular style of it. Intentional or not, it smacks of some of those old (but still prevalent) conceptions about certain traditionally black hairstyles.

For your vector issue, I'd go the route of some static examples if possible. Do you have a way to manually work out the answer that your code is trying to achieve?

For side effects, that may indicate what I referred to as tightly coupled code. Could you give an example of what you mean by "side effect"?

For unit tests, you should know the input and expected output from the start. Really responsible devs write the unit tests first, because you should know what you're going to put in and what you'll get out before you start writing anything. If you find yourself making the same mistakes in your tests as you do your code, you might be trying to do too much logic in the test itself. Consider moving that logic to its own testable class, or doing a one-time generation of a static set of input/output values to test instead of making them on the fly.

How granular your tests should be is a matter of constant debate, but generally I believe that different file/class = different test. If I have utility method B that's called in method A, I generally test A in a way that ensures the function of B is done correctly instead of writing two different tests. If A relies on a method from another class, that gets mocked out and tested separately. If B's code is suitably complex to warrant an individual test, I'd consider moving to to its own class.

If you have a super simple method (e.g. an API endpoint method that only fetches data from another class), or something that talks with an external resource (filesystem, database, API, etc.) it's probably not worth writing a unit test for. Just make sure it's covered in an integration test.

Perhaps most importantly, if you're having a lot of trouble testing your code, think about if it's the tests or the code that is the problem. Are your classes too tightly coupled? Are your external access methods trying to perform complex logic with fetched data? Are you doing too much work in a single function? Look into some antipatterns for the language/framework you're using and make sure you're not falling into any pitfalls. Don't make your tests contort to fit your code, make your code easy to test.

If ever you feel lost, remember the words of the great Testivus.

Back when I started using Linux, I really wanted something that was super different from windows (I used Gnome 3 for like 3 years). I decided one day to try out Fedora cause, hey, I can live on the bleeding edge.

Second day I had it installed, I was having issues with the audio. Decided to try reinstalling pulse. Apt autoremoved it and somehow completely nuked the entire GUI. Stuck in terminal mode, I found that I had no ethernet to connect to, nor could I figure out how to connect to a wifi network with a password or download packages to a USB. After a couple hours, I gave up, wiped the drive, and went back to Mint.

Nowadays I'm happier in my little comfort zone.

As a wise man once said, "you can't eat at everybody's house."