stcredzero

In fairness, the spike in cholesterol is a legit piece of data to be concerned about. But then again, there's other data that supports the idea that the higher cholesterol is an adaptation which doesn't increase the risk of heart disease.

Something as complex as the human metabolism is going to require a higher degree of nuance. (Also works this way for climate.)

This is simply "vertical integration" applied to "regulatory capture."

Sounds a bit like what happened in newsrooms and at newspapers in the past decade and a half. (Except in that case, it was bottom-up, not top-down.)

It just so happens, that many of the interfaces one has to deal with are somewhat low bandwidth. (For example, many spend most of their time stepping over, stepping into, or setting breakpoints in a debugger.) Code completion greatly cuts down the number of options to be navigated second to second. It seems like the time has arrived for an interactive voice operated AI pair programmer agent, where the human is taking the "strategic" role.

Let's unpack this even more. A quite potent problem, is when something else is posing as or sneaking into activism and movements like Open Source and FOSS. This something else can take the form of cliques, hipsterism, or the use of movements to vent anger or aggression.

The best way to hurt a cause is to represent it badly.

> FOSS was founded on the principles of openness and collaboration, something that we need now more than ever, as the largest companies of the world have managed to weaken that resolve through slick marketing and anti-competitive practices.

Some of the best open source software was developed, open sourced and maintained by the largest companies of the world.

Scapegoating people and groups merely by taxonomy has had a bad record across history. Hold people and companies to account for the things they do, not for their characteristics. That's the only fair form of accountability.

Also, saving money and time by epoxying the hinges into other Macbooks, instead of using fasteners.

Perhaps my experience is atypical, but I had way more issues (not just hassles) with my last Toyota Corolla.

No it doesn't so much bearing. I was talking about the situation with communications in relationships in the present day, not back in the 80's.

If AMD invented the analogous to x86_64 for CUDA, this would increase competition and progress in AI by some huge fraction.

Basically, people don't want to do the lawsuit, because they don't know how and to pay for the expertise, it would cost more than the paycheck.

The most straightforward way to fix it, is to make the expertise low or zero cost.

An "AI assistant" that was effective would be telling you the same thing.

No, it would tell me how to conduct the lawsuit.

Below is what ChatGPT-4 just told me. Had I known back then, I would have just done this. (And I note that the lawyer who told me it would cost me more than I would get back didn't tell me a lot of this!)

User

I have been shorted $4000 on my last paycheck when I was let go by a software company in Columbia, South Carolina. What is the jurisprudence on being shorted pay, what do I have to prove, and how do I go about bringing the lawsuit.

ChatGPT

In a situation where you've been shorted on your final paycheck, the specific steps you can take and the jurisprudence around it largely depend on both federal and state laws. Here's a general overview of what you need to know and potential steps you could take, specifically tailored to Columbia, South Carolina:

Jurisprudence on Being Shorted Pay

Fair Labor Standards Act (FLSA): At the federal level, the FLSA requires that employees are paid for all hours worked. If an employer fails to pay you what you're owed, you may have a claim under the FLSA.

State Laws: South Carolina has its own labor laws that complement federal laws. While South Carolina does not have specific laws governing the timing of final paychecks for terminated employees, employers are generally expected to adhere to the agreed-upon terms of pay. If no specific terms are set, then they must follow the usual pay schedule.

What You Have to Prove

To bring a successful claim for unpaid wages, you typically need to prove:

The Amount Owed: Documentation or evidence of the agreed-upon wages and the shortfall in your final paycheck. Hours Worked: Evidence of the hours you worked for which you have not been paid. This could include time sheets, emails, or other records. Attempts to Resolve: It's often beneficial to show that you've made reasonable attempts to resolve the issue with your employer before resorting to legal action. Steps to Take Review Employment Agreement: Check your employment contract or any official documentation regarding pay rates, schedules, and termination policies.

Gather Documentation: Compile all relevant documents, including pay stubs, employment contracts, correspondence with the employer about your pay, and any records of hours worked.

Attempt to Resolve Directly: It's often recommended to attempt to resolve the issue with your employer directly. Sometimes, pay discrepancies are due to clerical errors and can be corrected without legal action.

File a Wage Claim: If direct resolution isn't possible, you can file a wage claim with the South Carolina Department of Labor, Licensing and Regulation (SCLLR). While SCLLR does not handle wage disputes directly, they can guide you on the process and what state resources might be available.

Consult with an Attorney: Consider consulting with an employment law attorney who is familiar with South Carolina's laws. An attorney can advise you on the best course of action, whether it's negotiating a settlement or filing a lawsuit. They can also help you understand your rights and the strengths of your case.

Small Claims Court: For amounts under a certain threshold (which varies by state), you might be able to bring a claim in small claims court without the need for an attorney. In South Carolina, the limit for small claims court is $7,500.

Federal Claim: If your case involves violations of federal law (such as FLSA violations), you might also have the option to file a complaint with the U.S. Department of Labor's Wage and Hour Division.

Each case is unique, so it's important to get personalized legal advice. An attorney can help you navigate the specific procedures and ensure your rights are protected throughout the process.

EDIT:

Top comment as of my writing:

I mean, the obvious solution is superhuman sexbots, right? People aren’t breeding anyways, they don’t really seem to like each other much for relationships qua relationships given “divorces and mutually unhappy marriage” rates, at least when given options and interesting Western lives.

My take on the divorce rate, is that people no longer know how to talk to each other in the context of a relationship. Instead of actually substantively talking to each other, so many accept a substitute. By this, I mean shutting down one's partner or letting one's self be shut down. This is also connected to an erosion in society's teaching people about accountability.

My partner and I are accountable to each other, and we know how to actually talk about everything, including uncomfortable things. From what I see, we are an uncommon case.

Is this something which could be addressed through the use of a specialized AI assistant?

The biggest barrier to uncompensated workers is the cost of litigation. If the worker could represent themselves effectively, then this would stop.

More objective looks at reliability put Teslas as a class very far down in any ordered ranking.

Really, you should look more closely at automotive industry rankings. This is basically fodder for the legacy media, which has deservedly lost a lot of credibility. For that matter, take a close look at media covering these things. So many of these things are gamed. Also look up what Peter Thiel says about incumbency, ossification, and lack of true innovation in today's industry. It's not that the emperor has no clothes, but things a lot skimpier than they're supposed to be.

[Citation Needed]

There's a long history of such rankings being gamed by the auto industry. If you follow Tesla closely, it's quite obvious that so many of the rankings are simply designed to exclude or disadvantage them.

What's interesting is the despite this Teslas often rank near the top for owner satisfaction.

I can believe that both are true.

In automotive history, when there's disruption and car adoption shifts so massively, has it ever turned out that large numbers of people were deluded? Has it ever turned out that large numbers of people saw real value where complacent incumbents dropped the ball? (Example: Japanese imports disrupting the US market.)

That answer to both is yes. However, the 2nd has been more often the case. Also, the instances of the 1st simply don't last multiple years.

So if you consider automotive history, it's far more likely that loyal Tesla owners are onto something, and you simply want them to be deluded.

There's just far less to go wrong on an EV. Corollas have a reputation for reliability? The Teslas following the S/X super luxury models, the 3 and the Y, look to beat them at this game.

Our household used to exclusively drive private party used Corollas. We've switched to Teslas. If your time is valuable and you factor time and money together, the savings on hassles is already worth it in spades.

On a couple of occasions, I dated women who were considerably taller than me. One of them had a very big, toothy smile, and liked to wear horns when she went to Renaissance festivals. I used to call her my "wild thing," in reference to the Maurice Sendak book.

EDIT: Come to think of it, there's Robert Crumb's drawings of his getting piggyback rides with his wife at the time. Kind of similar in spirit.

https://en.wikipedia.org/wiki/Doggerland

Neanderthals, Sapiens, and other close relatives like Denisovans could serve as analogues of fantasy races, like elves, dwarves, and hobbits. Non Neanderthals and Sapiens would have to be on the rare side to explain how they haven't been discovered today, but the fact that the entire region was submerged helps with that.

Perhaps certain factors could have made the region extremely prosperous by standards of the time and a nexus of prehistoric trade, giving rise to a rich culture attaining legendary status. However, none of its architecture used stone, and all of its knowledge was carried through oral tradition.

We made code coverage a part of CI, and we've been using that to drive up code coverage. It's been working. Our tests have gone from ~25% to ~50% coverage. Breakages making it out to staging have gone down.

Also, some incentives are well aligned with this. If people see that things aren't easy to test, then they get rearranged to make them easy to test. Not all incentives are aligned, but not everything is perfect. This is why reviews are useful.

When I've looked at the reports I keep finding trivial code that would be hard to test for little gain.

If your trivial code is also hard to test, then this indicates architectural code debt. Why isn't the trivial code trivial to test?

I prefer to think of them as the underwear gnomes, just more widely read and better at BS-ing.

What happens when everyone gets to have a tireless army of very knowledgeable and AVERAGE common sense interns who have brains directly wired to various software tools, working 24/7 at 5X the speed? In the hands of a highly motivated rogue organization, this could be quite dangerous.

This is a bit beyond where we are now, but shouldn't we be prepared for this ahead of time?