skysight-inc/HackerNews huggingface dataset:
It's just not that simple. I'm not making a value judgment on the book (I haven't read it), but a person can say two things in the same sentence and the broader context can make it clear that they're just covering their ass, for example. Perhaps that's not what's going on here. Perhaps the book does constitute "malpractice." But...I think the situation is more complex than you're giving it credit for, and I wouldn't be comfortable drawing conclusions without a greater familiarity with the book and the responses to it. I also don't give a lot of credence to the blog you linked, since they use (as one of their two pieces of evidence) a critique which openly admits it hasn't actually read the thing that is being critiqued.

To your last point, plagiarism, for example, definitely counts as malpractice and humanities professors lose their jobs for it.
> different people learn in different ways.

That just avoids the discussion altogether. We can’t evaluate any form of education or presentation or description because “different strokes for different folks” — but we know some styles are almost-objectively bad (beating you with a shovel once a minute while I teach you is an all-around terrible idea, even if I can’t prove it — different learning styles!), which means we have an metric we can evaluate by and discuss on, even if it’s largely driven by intuition and anecdotal experience.

The question here is, for a novice, does this trick you into thinking you’ve learned something, when you really haven’t? A novice also doesn’t have the knowledge to effectively judge that, because, well, it’s a novice.
> Personally I wish F# had more resources assigned to it at MS.

This absolutely. Or that they had avoided the usual NIH MS is prone to, and just supported another ML variant (thus reducing the load to match the resourcing).
Cool project! Can probably integrate with SimpleML (author) to add persistence and versioning. Happy to help if you're interested
https://github.com/eyadgaran/SimpleML
Yes, battery cells don't have any software. But we are also designing and producing whole battery systems, and that includes creating in-house software for our battery management system, our IoT gateway and our battery fleet management platform in the cloud.

We have two software engineering at Northvolt, one working on automating our gigafactories, and another working on battery systems as described above.
Feature creep, though in a way in which that feature creep is used to keep people hanging on and reel in new investors. It has in near on become it's own business model. Difference from releasing and then adding updates every so often, they just keep tweaking, tuning and when you keep going on feature creep, you end up striving for perfection, which makes getting a balance right very hard. However, they seem too of done all-right as a business, even if they have a rolling beta. Though as it's beta - people are more accepting of bugs than they are if released and they await a patch/update to fix bugs. That in itself makes things different from a user perspective in a way that advantages the writers, also less pressure.

Elite Dangerous took the more release and then add updates to maintain momentum. A more common approach and how many investors would hang on for all these years, yet for Star Citizen, when the investors are users and the extra's the offer sure do tap into that Whale momentum income and really does seem like a whole new approach to business the way it is panning. Though Kickstarter seem to of coined that.
I am in agreeance by the way. I think perhaps my comment came across as trying to soften the seriousness of dark-patterns when really I was just trying to say that there are lots of different perspectives on different types of coercion. It's not that it's unclear when something is coercive, it's that it's unclear how much coercion and trickery is unethical, as it depends on who you ask.
Things you'll care about on a daily basis:

* Rear hatch will occasionally just open by itself. There was a TSB from the dealer to resolve this where they reprogram your keys and adjust the sensitivity of the kick sensor but I'm still skeptical. The audi app should alert me if the hatch has been left open for more than X minutes with the car off.

* Audi App in general is very slow and unresponsive. Sometimes I'll try to precondition the car and the app just spins for minutes and then silently fails.

* The onboard charger can run with either 50% of 100% of a circuit, nothing else. If you are at a shared 240 or 120v system where there is a lot of load (RV camp ground for example) your car simply won't charge.

* Electrify America is a mess. You can google this and see thousands of examples.

* There is no regen or one pedal driving. You can manually activate regen by pulling the levers on the steering wheel but the behavior isn't consistent and the regen isn't strong.

* There is no way to enable "creep" mode like how a traditional automatic ICE car behaves.

* There is a feature to schedule charging for those who have off-peak rates. You have to set this every single time you use the car.

* The virtual cockpit and 360 camera occasionally fail to initialize so you just have blank screens.

* Consumption is extremely high. For reference for Tesla people a good day in an etron is 400wh/mi.

* Vehicle nav map shows me gas stations, no way to search for charge stations.

* Vehicle still has ICE based service reminders built in.

---

Now for things that are going to get someone killed:

* The vehicle rolls backwards on hills. This + lack of creep means that you have to feather the gas. There is a "hill hold assist" which will randomly kick on but it's not reliable. Stop and go traffic in a hilly area is very annoying.

* When parking the vehicle will roll backwards or forwards for about a foot until the brake catches. This could easily entrap someone in an enclosed space.

* If the vehicle is "on" or "off" isn't completely clear as a user. If you put it into accessory mode it looks exactly the same as the vehicle being on sans one small green line. I've accidentally put the vehicle into neutral with the vehicle in accessory mode while parked on an incline and it began rapidly rolling away (the thing weighs almost 7000lbs) while I tried to pump the non operational brakes.

* Vehicle automatically shuts off climate control after 30 minutes of idle. I'm glad I learned about this while waiting for someone instead of when I had left my dog in the car.

* Getting out of the driver seat shuts off the car completely when in park. See prior points about climate control and rollback.

I could go on. This is just what came to me off the top of my head.
On the flip side it sounds like Tesla may be suffering from a Not Invented Here syndrome which would seriously hamper their ability to innovate quickly and inexpensively in the future.
A step and a half actually
God forbid people are happy for an hour, we've got to raise their insurance premiums. You know in Indiana, it's actually not even legal to have any happy hour promotions wherein the drinks are cheaper but only during a certain window. If you want to make people happy with drink specials, you have to offer them the same drink special all day long. (And so that's how we do...)

Happy hour here is just when you can get a $2 cheeseburger, or $0.50 wings on special. I had never even considered something like a happy hour being reflected on your insurance premium.
First, nothing about "y'all have to thank" suggests that they consider the person they are responding to responsible for Brexit, which is a requirement for it to imply that they are putting some sort of blame on the person (or the collective group they represent).

But let's for the sake of it accept that "it's your own fault" is what was meant by it anyway. That still doesn't imply bitterness.

If parents explains to their child not to run with scissors because they might hurt themselves, the child does so anyway and ends up hurting themselves, and one of the parents says in-between consoling their child "but do you see how you only have yourself to blame for it, if you decided to do this anyway after we warned you this would happen?", then that might not be the most considerate timing for sharing a harsh truth, but there's nothing bitter about the statement.
LinkedIn will suggest people from the same IP address. If you accessed LI from your doctor’s office that would explain it.
Surely not image compression.

Sounds like your screenshots are being conveniently uploaded to MS servers so you could share them (Yay!).

Getting such enormous delays when performing otherwise simple operations usually means that network requests are being made, and servers aren't normally snappy when it comes to free storage.

Here is my example of enormous loading times: it takes a few minutes to clear browsing history on the android version of Chrome browser. Quite outrageous.
Doesn’t appear to work on my tablet… so goal 110% achieved!

Edit: oh, heck, it does work—I completely missed the obvious misdirection!
Foundation Will Debut on Apple TV Plus in September
Forgive me, I forgot criticism amounts to sacrilege.
So no point on keeping your existing old laptop / PC (If you're using Windows) and no point on keeping an existing Intel Mac (Because Windows 11 won't run on there anyway.)

Here are a few options for Windows users:

1) Use a hacked ISO that removes the TPM requirement

(Quick hack for unsupported machines. This will probably break on an update, unless it is only applied on install, but comes with a possible risk of tampering of the ISO)

2) Fit a TPM 2.0 module to meet the hardware requirement (Good luck doing that on a laptop. Probably pay a technician to do it properly)

3) Buy a new PC / Laptop that is Windows 11 ready. (Effortless but expensive)

4) Sit on Windows 10, until it is out of support.

Enthusiasts and early adopters will go with (1), security guys will go with (3), hardware hackers go with (2) and most will give up with (4).

For existing Mac users, there is ZERO benefit in purchasing an Intel Mac anymore. Would much rather wait and get a M1X Macbook Pro or Air at this point.
This is one of the main reasons I feel like the current culture of never disagreeing with anyone so you can never possibly offend anyone is ultimately toxic.

As a person with (currently treated and doing fine) psychological issues I don’t expect any single comment to get through to you, but if there are never any negative indicators that you are the problem, rather than everyone else… there is a mathematically insignificant chance you will ever realize something might be wrong.

Particularly so in the case of the unfortunate stereotype of lonely loser who lives in his mother’s basement and spends all his time on the computer.
The most common way those exit-intent popups work is to check for when the users' mouse leaves the viewport e.g. https://stackoverflow.com/questions/923299/how-can-i-detect-...
Machines learn that Brussels writes the rules: The EU’s new AI regulation
> No, my point is precisely that py2 and 3 are not compatible.

Which still misses the point, py2 and py3 not being compatible is different than them being completely incompatible, because there is a useful, workable, common subset of Python 2 and Python 3.

The entire issue with Python 3 was that there originally was not, the core team had to be dragged kicking and screaming into carving it out through backports and reintroductions because their original strategy was not workable.

> Py2 and Py3 string apis are not compatible. They cannot be made compatible. They can never be compatible. There's no "from __future__" that could make them compatible without a stupendous amount of work.

So?

> Not to be pretentious, but I'm developing the opinion that anyone who thinks that the Python team could have just shimmed their way between 2 and 3, does not really understand the Python compute model.

How can you claim that when "shimming their way between 2 and 3" is exactly what ended up happening?

> Google literally invented a py2 to go transpiler (grumpy) to avoid converting. Do you think for a second if there was a way to just "from future" their way to a compatible str object, they wouldn't have taken that route?

Have you considered stopping beating up your strawman?
The lab leak theory is nonsense and a distraction. If you compare where the mutations of sars-cov-2 are, relative to a wild type bat coronavirus, they are distributed randomly across the genome. If you were to genetically engineer a virus, those mutations would not be random, there would be a discrete chunk of edited base pairs that had been spliced in from somewhere else but that isn’t present. It seems unlikely that in this day and age a virology lab would be doing gain of function experiments without crispr since it’s far easier than the alternative.
Fascinating article -- amazing that Ukraine only has one exit point that goes through Russia.
But vanishingly rarely are diagnostic tests given and then the results ignored. That's not how consumers of healthcare nor clinicians work.
Lots of oppressive governments and controlling entities are not happy about it.

Kudos to Telegram team!
The app my credit union uses for online banking and card control functions is only 81MB.
The article's actual title is "Are Twitter trolls mentally ill?"

It makes me want to talk about how the concept of the troll has evolved from something specific to something very general. I glanced through the article and none of the behaviors it listed are what I'd consider troll behaviors. They're just the patterns of mild mental illness.

Trolls, in my old-man's definition, are almost a type of hunter, looking to bait and confuse their victims.

Trolls wouldn't be the hoards suffering from "sanctimony, emotional aridity and ideological orthodoxy", and exhibiting BPD/DID behaviors. Trolls would be the people trying to provoke the above.
There needs to be a Rust translation of Learn Go With Tests[1]. It’s the best programming book i’ve ever used.

[1]: https://quii.gitbook.io/learn-go-with-tests/
I have a feeling you might already have a good hunch about the answers to your questions, but I’ll bite:

If you see in a data set that Danes are tall, and that Kenyans are fast, and that Ashkenazi’s are smart, then it is a valid hypothesis that should not be thrown out outright, that the reason that’s the case is due to actual differences inherent to the population groups and not any other confounding factors.

As for your second question: mostly progressives, leftists and liberals.
This isn't only present in "newer versions" of iOS — iOS has worked like that since day 1.
That seems to muddle interface with implementation. What if your underlying architecture creates new versions of records when they are edited. That wouldn't be idempotent but you wouldn't change your API.
The main problem for me is the old "fish rots from the head down" effect -- when the rude and entitled behavior comes directly from the top, it's no surprise when everyone else starts acting like that and gets at each other's throats. It should be obvious by now where this weird sense of entitlement and refusal to understand other people's culture is coming from.

>feel free to fork it and start up a parallel project without the problems you see

Most Linux distros are basically already doing this. They all have their own patchsets. It's well beyond correctness and hygiene at this point, if you actually look at the changes that are being disputed, it already falls a lot more in the "cultural differences" category.
That repo is over 7 years old. It’s exploitable, but I’m pretty convinced that this info has been out for many years.

https://hackaday.com/2014/02/25/using-sdr-to-read-your-smart...
Peaches 'n' Stink [1] uses ltree for nested comments. All the PostgreSQL is here [2]. The first query that uses ltree is on line 452 [3].

It was hard to decide on the ltree "path" format. There's a "path" value for each comment and it is what sets up the hierarchy. What I ended up using was this (root level comments):

1.aaa

1.aab

1.aac

1.aad

.

.

.

1.aaz

1.aba

1.abb

The "1" is the post ID. Sub-comments under the first comment above would be:

1.aaa.aaa

1.aaa.aab

1.aaa.aac

The reason why I used this "path" format is because if I sort alphabetically then the comments will be in the correct "vertical" order to display chronologically.

[1] https://www.peachesnstink.com

[2] https://github.com/ferg1e/peaches-n-stink/blob/master/db/ind...

[3] https://github.com/ferg1e/peaches-n-stink/blob/master/db/ind...
OMG. Thanks for bringing back that Onion classic. The sentence suggestions are legendary Onion.
> I'm just shocked at how resistant people are to new technologies and ideas that could make things so much easier

> I see how so many things we take as standard in the industry are incredibly slow, overcomplicated and inefficient, but when I try to introduce new ideas or patterns at work they're unfamiliar and therefore "too complex"

Almost everywhere I've worked there is always resistance to change - but not always because people are too lazy to learn new things. There's an inherent cost for a team to adopt something new - there's no free lunch. Especially when it comes to new technologies, if your team doesn't have the chops to dig into the source when things go wrong, you're probably not
going to have a good time even if they do adopt it. And new technologies can be incredibly complex - can your team manage the complexity? Who will support and own the builds, the deployment process, troubleshooting, etc? People who cry at the first sign of trouble will continue to do so.

You have to justify it to the team, the manager, or the business. Oftentimes if you ask for permission to add something new, you'll probably never get it. If you go ahead and prove empirically to everyone that it works, and it works better than the old stuff, that's a great way to start adoption.

Of course, if you still can't get adoption without legitimate reasons for pushback, I'd say the team culture is the real problem. People on the team think learning new things is more work, and why work more for no pay increase - especially for a job they don't really care that much about anyway?

If you work on one of these teams, you might as well just power through objections and just do whatever you want. What do you have to lose? Even if you get fired, big whoop - you weren't gonna last long there anyway. Of course, this is all predicated on the fact that you are competent and not just automatically dismissing real concerns of teammates - if you go full cowboy and actually break everything, you deserve the consequences.

I've worked at awful places like that too, but I've been able to find the top 5% of competent folks and work with them to make life more tolerable. It's hard to find a place with curious folks that dig super deep into stuff. You have to really grill the interviewers or ask to see their codebase, or know someone who already works there. I only interview with places where previous coworkers I trust already work on the team now to avoid this problem.
...though once this kind of attack became common, the utility meter manufacturers started adding anti-tamper features like hall effect sensors that record the presence of an unusually strong magnetic field near the meter equipment. You'd get some questions next time the meter reader came around and the tamper indicator was lit.

Utilities have a lot of financial incentive to keep people from (at least blatantly) manipulating their billing.
LinkedIn is not a Covered Entity or the Business Associate of a Covered Entity and as such does not fall under HIPAA. They have nothing to worry about. The doctor on the other hand...

HIPAA is, contrary to popular belief, not about medical information but about specific entities that process medical information. In this way it differs from a law such as GDPR.

edit: This is also why a company like Fitbit or Apple do not fall under HIPAA despite having your medical information. They are not a health plan, clearinghouse, medical provider (that does electronic billing in specific formats), or the Business Associate of those entities.
Im a senior dev in the US and my company just said we have to come back full time in the office. This is even after we've had record revenue months.

I would be totally fine with hybrid, but they said they investigated that and decided against it (don't know why). I'm looking around at my alternatives, but the pay is just not there for both hybrid and remote. So I dont know where all this demand is, unless it's the same demand that's always there when they won't pay people anything. I may end up taking a pay cut just to do hybrid/remote which is really sad, but my well being may be worth it.
They do, and I signed up for it. I literally just haven't bothered canceling the BoA CC yet. It's not been used since I got the USAA card (which is only used when the AMEX isn't accepted).
Those people probably wanted to pay with cash. Walmart self-checkouts[0] switched to electronic payment only[1] when the national coin crisis hit in June 2020[2].

[0] https://corporate.walmart.com/newsroom/2020/06/30/new-checko...

[1] https://www.quora.com/Why-are-Walmart-self-checkout-register...

[2] https://www.frbservices.org/news/communications/063020-feder...
Do note that there is very little current use of Filecoin storage. Right now it's not too different from Chia.
So we can't discuss trans people as a category and their correlations?

There's a line between avoiding harmful stereotypes that lead to unfair discrimination and willful ignorance or misrepresentation of facts in service of political correctness.

It's extremely hard to say where this line is.

But we still have to be aware of its existence.
Good theory, but it's factually wrong. "Maintainers" in this context doesn't refer to Linus personally, it refers to individual maintainers of parts of the kernel. You can check the kernel MAINTAINERS file, and note that such a file has been there for years.

There has been a longstanding problem of people submitting low-quality patches to maintainers - not to Linus personally - and that problem predated Linus stepping back for one release.

Linus was not ousted and continues to have nearly absolute control; he has, for decades, chosen to exercise that control by delegating ownership of parts of the code to other people. Those people receive and review patches and incorporate them into their repos, which Linus pulls in bulk. (This is the origin of the term "pull request," which predates GitHub's use of it.) He quickly reviews those patches to make sure there's nothing weird, but he generally trusts that his "lieutenants" are making good decisions.

That means that the time being wasted here is the time of individual maintainers, who are reviewing the patch, making a full judgment on it, and pulling it into their tree. Linus sees all such cleanups once per cycle and looks at them fairly quickly.

Almost all of those maintainers have been "normal employees" of various companies for many, many years. Again, take a look at the MAINTAINERS file.
IMO part of the problem is that Greg KH publishes this annual 'state of the kernel' that is just a list of metrics to game. Which feels like it was started to shame non-RH companies to contribute more often. So, kinda maybe beware what you wish for?

Example: https://www.youtube.com/watch?v=SIQr2-Dh0es