skysight-inc/HackerNews huggingface dataset:
If your class is doing so many things that you can't reasonably test everything but through the private methods, how about extracting a helper for those things which has testable public (or package private, if you have to) methods!? Did I just sneakily bypass the rules, or make the code better overall? I don't know anymore...
More like, they bring the sushi, but also a pair of shoes. And when you throw the shoes on the floor because they are not what you ordered, they come back over and put them back on the table.

On iOS they only sell shoes, you don't go there if you want sushi. (and too bad if you find yourself locked into the apple ecosystem / restaurant, because shoes is all they have.)
mundane*
It's inevitable with a two party system. If the US had 20 parties there would be a political tradition to form coalitions. Liberals forming a government with far right Christians- the best medicine for ideology is Machiavellian pragmatism.
Ah. Good luck having stable economic life if your "national currency" jumps wildly due to random pump-and-dumpers or ransomware payouts and can go to zero the next day.
At $6,000, how is M2 Max the best bang for the buck?!

One could get two used 3090s and setup a decent PC at lower prices.
I feel like that script needs a few 'are you completely sure?' Prompts
My money is still on LK-99 being a finicky topological (only conducts in one direction) superconductor.

Its what the simulations suggest. It would explain why the replication attempts failed.

Its perhaps no world-saving bulk superconductor, but that still seems like a fascinating material for, say, microelectronics or high power electronics. For instance, what if foundries could align it and work it into a metal layer for microchips? Maybe they could take advantage of the directionality to make a gate out of it.
It's 2023 and I still can't get a Dell laptop with Linux pre-installed to sleep properly without crashing without editing things in the terminal and mucking about in the bios.

Even giving up on that and disabling sleep on lid close requires using the terminal. Sure the Gnome Tweaks tool has a setting for that but it's not installed by default and check the comments here, it doesn't actually work.

https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-...

https://www.dell.com/support/kbdoc/en-nz/000179566/how-to-di...
They definitely use it for more than that, because I'm sure I've seen it ship with Windows games as well.

Also there's exactly 2 ways to get a window on Linux, and those 2 ways are common to pretty much every modern distro. Same as audio.
How is the login experience, DNS, and routing related to the US Web Design System?
Nobody is advocating for synchronously importable modules in browsers. Also, people had already written support utilities like require1k [1] to support cjs in browsers. We don't necessarily need a full bundler - we only need a module analysis step between parse and execute which a native js engine is quite well positioned to facilitate.

Having said that, the fact remains that vast majority of pain points that people who actually need to maintain isomorphic libraries face today have nothing to do with synchronous vs asynchronous nature of cjs and esm modules.

It is the myriad pointless nuances like default export, namespace imports etc. that are sources of biggest headaches in day to day work. In cjs there is a simple model that a module exports an object and while importing you import that object. Instead now we have a situation where we need to deal with:

export default {
foo() {...}
}

is not same as:

export function foo() { ... }

and

import Foo from "foo"

is something different from

import * as Foo from "foo"

Plus the additional complexities introduced by import bindings being live etc. are just annoyances that one has to deal with over and over again every time module interop is involved.

[1] https://github.com/Stuk/require1k
> Actually, we made way less of Knight's $400m than we could have because our risk systems kept shutting strategies down because what was happening was "too good to be true".

Aren't a lot of trades undone anyway by the authorities after such severe market hiccups?
It starts with the Dylan/Cash bootlegs, and that is in fact one of the original "white cover" bootlegs I recall arriving in Scotland in the 70s. For Edinburgh residents you knew you had one of the first shipment if it was covered in mud: the parcel of albums had been dumped close to a puddle by the record shop door. I can't remember if we called it "40 red white and blue shoe strings" or "Motorpsycho nightmare" but they are the two I recall. The double "joker" album had Dylan on piano doing 'I'll keep it with mine'

The great thing about the Nashville recording (as I recall it) is that it has Cash singing lead on some of the songs on "Nashville Skyline" and he sounds fantastic.

The only more obsessive tragics than Dylan bootleg owners, would be Grateful Dead recording owners.
When was it deployed? (and other interesting questions)
Do you have, or wish you had a dashboard that showed you more than just surface level information about the status of your applications?

Do any of the questions below need answers?

How would you want some of these questions sliced (e.g. across Apps, Teams, Charters, etc)?

### Engineering Focus

- What is deployed (application/service name)?
- Where is that application/service deployed (environment)?
- When was it deployed (to that environment)?
- What version (semver, git SHA, combination) was deployed?
- What stages/steps occurred during the deployment?
- How long did each stage/step take?
- Where there any failures?
- If I see red, are we having an outage? Or did it rollback?
- Who is getting notified of these failures?
- Who owns these applications/services?
- Where is the code for these applications/services?
- What is the MTTA/C (Mean Time to Approve/Close) a Merge/Pull Request?
- What is the IRFR (Infrastructure-Related Failure Rate) Percentage of build/deployment failures related to infrastructure issues?
- What if I notice a problem that wasn't caught automatically, is there a "big red button" I can push to notify the right people to start an incident?

### Leadership Focus

- How often are we deploying?
- How long does it take to deploy (from merge to production)?
- What is the MTTR (Mean Time to Recovery) in case a deployment fails?
- What is the Defect Escape Rate? How often is code merged that causes failure? Do those failures escape Staging (show up in production)?
- How compliant are we towards our SLA's and SLO's?
- Are new features/fixes tracking towards our OKRs/KPIs?
- What is the RWR (Rework Rate) Percentage of tickets being reopened?

### Data-Quality Focus

- Is this data fresh? How would I know if it's outdated?
- How are the metrics above changing over time? Are there correlations that I can use to research if there's a causation relationship?

### Engagement / Culture Focus

- Do teams have a easy way to voice feedback (anonymously if necessary)?
- What is that feedback?
- How much of the feedback is positive vs negative?

### Proposal

- What if you could get all this information in 1 place for any application, any team, slice and dice the way you want it and it was all 100% automated?
- Do you already have a system like this? If so, please share!
- What other questions would you want answered?
> the deployment agent errored while downloading the new binary/code onto the server

In that case the build would never be pushed to production. The worst it would accomplish, and this is if your systems fail, is that it will break your staging area.

Sure this is in the the ideal world where people actually know how to set up their deployment pipelines correctly, so you’re likely still right in many cases, but you shouldn’t be.
> Insightful. And the next era will describe it in terms of quantum interactions.

Roger Penrose already talks about a theory of consciousness based on non-computable quantum effects in microtubules. http://www.consciousentities.com/penrose.htm
Yeah but a scan takes one radiology tech 30 mins, then the radiologist does the analysis, again not hours.

In surgical procedures all those people have to physically be there for hours
Still technically in a lab for now, but eventually not: https://en.wikipedia.org/wiki/ARC_fusion_reactor

> ARC uses rare-earth barium copper oxide (REBCO) high-temperature superconductor magnets in place of copper wiring or conventional low-temperature superconductors. These magnets can be run at much higher field strengths, 23 T, roughly doubling the magnetic field on the plasma axis.
The picture you paint is that homeowners are the independently wealthy rich people with tons of idle free time, while renters are all very poor working multiple jobs.

In reality the vast majority of homeowners are regular working professionals, working those 50-70 hour weeks to pay the mortgage.
Beyond Algorithms
What if you have no UARTs? Multiple UARTs?
Exactly the point I've been trying to make, thank you
> With current membrane technology, yes.

Equation 12 is the energy you need to counteract the effect of the entropy of the ions in solution and separate the initial solution into one that does not have the ions. It’s pretty much a thermodynamic limit and does not depend on process or technology.

They explicitly assume that they have a perfect membrane when they introduce the equation. The floor will never be zero, it is a physical limit.
Try the second set of instructions here https://www.intowindows.com/how-to-reinstall-microsoft-edge-...
With regards to the worth of the gadget... Is it better to be slightly more physically healthy but have less privacy, or retain privacy but miss the potential benefit? This is a question for present age.

You'd think that knowing the amount of steps you do etc in a day would certainly be your information for one's own eyes only, but no - corporations are heavily involved.
> it seems strange that the author EVER thought that no comments should ever be needed

That was a trend many years ago when people started seeing how comments are often out-of-date, sometimes been copied pasted around so many times it's not even saying anything useful about the code next to it, and sometimes the author is just a bad writer and makes it more confusing than the code itself. So people became pissed off and kind of decided that the code needs to be clear enough to be self-documenting: short functions with verbose names, good variable names etc. making comments unnecessary.

I do agree with that, but IMHO there's still a place for comments: as many others are saying: when you need to document why something has been written that way, not just what (which the code should be able to tell by itself)... and I believe OP is also claiming that, and you appear to be missing this context.
People who don't want kids are being selected against.

Sex drive will eventually be replaced with a reproduction drive.
> Unit testing private methods.

What if I told you that you don't need private methods?
Things are somewhat different now than 5, 10, 20 years ago.

There has been a wave of "individual accountability regimes" released by pretty much every regulator.

I have worked with the SFC the most, so that's what I will describe here, but all these regulations are pretty much copy/paste of each other anyway.

I was MIC under the SFC (HK) for various operational and financial resps for approx 8 years responsible for close to $3B exposure across equities, IRS & FX, and am now licensed with the FCA (UK) since approx 1 year.

Basically, on top of the usual regulatory framework defining a top level Operating Officer (MOO) and subordinate Responsible Officers (RO), the new individual accountability regime creates the notion of Managers In Charge (MIC).

The MICs fill the gap that, increasingly, a considerable amount of operational responsibility lie in the hands of non licensed individuals (i. e. tech people).

The SFC defines a number of responsabilites (e.g. DRP/BCP, kill switches, backups, fail overs, rollbacks, load testing, etc) and these responsibilites need to be allocated to one or more of the allocated MIC.

The SFC has a right to reject an appointment of MIC if the individual is not seen as fit and proper (that is assessed generally on an annual basis by a compliance officer, but can be re-assessed on the spot if you end up displaying unfit traits). The SFC also mandates a track record of experience and expertise on the assigned responsibilities, as well as a direct capability by the MIC to have control on his responsibilities. In clear terms, that means you need to have the actual power of saying "no", you need to have the power to hire someone if that is necessary for the safety of the operations, etc.

Once you get appointed as MIC, most of your responsibilities are based on _means_, not _end results_:

If Karen breaks production, that's not much of your problem (regulatorily speaking) as long as you can demonstrate that you had Karen attend 6h of training this year on how not to break production.

In terms of actual developer experience, the _means_ often take the form of trainings, code review, pre prod impact assessment, incident reporting procedures, etc.

So on one hand you have a very heavy personal and professional responsibility. But on the other end you are at fault only if you did not setup a proper framework for things to work.

In terms of the professional responsibility, there is not much to do if you are deemed guilty. You will most likely be temporarily or permanently barred from having a licensed position. Nobody will hire you anyway.

For the personal responsibility, it is usually limited to single digit millions, and most big asset managers have an insurance to protect you (otherwise noone would accept the role).

If you are interested in the actual additional responsibilities that were added after KC, then I suggest you have a look at MiFID II (the European régulation, well written and understandable), especially segment RTS 6 "Technical standards specifying the organisational requirements of investment firms engaged in algorithmic trading":

https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/1...
It could still be the other way round. (In fact, the other way around is definitely true.)
You can't de-construct the listed property value bubble inherent in the city centre office scape, all the jobs associated with construction, and the input supply chain without some consequence.

Frankly $1.3T seems low. I think 1/3 to 1/2 of all the value forward in capital and major trading cities worldwide has gone. No amount of conversion to residential is bringing back all of the property trust value.

We've just got to live through the unwinding. If you want to see hardcore solutions, go look for the youtube videos from China of neve-occupied residential towers being demolished: Thats what the future holds for the tall cities.
I've battled with CFS/ME multiple times in my life, each triggered by different ailments. First, it was Epstein-Barr at the end of my tenth grade, leading to two solid years of chronic CFS. Then, at 31, Chicken Pox knocked me out for roughly 18 to 24 months. More recently, from January to August 2021, I experienced "Long Covid," and this July, a bout with RSV left me grappling with CFS once again.

My symptoms include daytime fatigue, necessitating frequent 40 to 120 minute naps. The brain fog is especially frustrating, causing confusion and lack of focus.

This recurring condition has undoubtedly impacted my professional trajectory. Interestingly, the only regimen offering relief has been consuming two crushed garlic cloves daily, which I started two weeks ago. I have hypotheses about why this is effective — possibly related to garlic's blood-thinning properties, but no concrete clinical evidence to back it up.
They could and should, though.
I can recommend you look at ubuntu certified laptops, they all are more likely to work with suspend/hibernate/resume https://ubuntu.com/certified/laptops

Also the notebooks tested at phoronix.com are a good indicator to work (Lenovo Z13 for example). In the case of AMD a lot of work with suspend/resume just recently (August 2023) got patched, so generally with a recent Kernel you should be fine these days. https://www.phoronix.com/news/AMD-Linux-Fix-SR-Wakeups
> It looks like for Al Gore climate change is an opportunity to wage class war.

I believe the class war maneuvers are coming from the other side, in making climate change a "liberal issue"; therefore it is something to be dismissed and derided.

And your answer is carbon tax? That's it? It may help a bit but doesn't address the core issue which is we need to stop using fossil fuels, which means actively investing in alternative energy production and management.
> $1.3 trillion of real estate value in big cities around the world by 2030

who holds that value? why should workers care?
>Getting global menus set up in your DE of choice for example takes a surprising amount of twiddling and even at its best doesn't work with a lot of software.

And is one click and works with all apps in Windows ?
Twitter has “verified” the account of President John F Kennedy
To what extent does your regimen relieve your symptoms?
Edge is still Blink+V8. Just test Chromium or Brave & forget about Edge.
I can see a process of triaging and deciding that some code isn't worth testing (yet), but the broader idea of "this is just a prototype", I'd like to push back on, unless you work in the rare place where they actually start over after the prototype. "Blasting out an MVP," you say? That should be production code then, with production-grade testing. I too work for a startup, and well-tested code allows us to release often and with confidence. I am humbled every day by unit tests slapping my wrist when I attempt something stupid.
But also, since they’ve decided to use someone else’s icon system, taxpayers are not paying for yet another icon system, when an existing one under an Apache license is available.
Burn!

This is one of my favs that is all over out codebase.

private float chanceOfRain = 0.1f
public float GetChanceOfRain() {
return chanceOfRain;
}

Perhaps somebody can explain it too me because I'm too afraid to ask.
(not the OP, just my two cents)

(1) is the distinguishing characteristic of TDD, but it is not an end in itself, it's a mere way to achieve (2). You write the test after you have the API design, but before you have the implementation, and thus supposedly decouple your test from the implementation, since you don't have the implementation yet.

This approach never sat right with me.

* It makes design iteration more costly: if you want to change the API design as you're implementing the thing, now you have to change a bunch of tests to use the new API, and that's when you don't even have the implementation to test yet! This makes you subconsciously prefer quick and dirty design patches instead of making bigger but better changes to the design. So you're statistically trading potentially better design for potentially better tests. I'd rather have the former than the latter, because it's much more insidious.

* Just like TDD encourages writing tests for behavior instead of implementation, it also encourages relying on tests as the sole arbiter of code correctness. The supposed better quality of tests is offset by over-reliance on them, including by not adding tests to check the weak points of your implementation (because you already wrote all the necessary tests before you came up with it... right?). I've worked with some TDD-loving developers who didn't even feel the need to run the code they wrote on their dev box, in the application context. Tests pass, therefore straight to production. The bugs caused by this attitude offset all other advantages of TDD.

* TDD pretty much relies on 100% unit test coverage, because since you (supposedly) don't think about what the implementation will be, you don't know in which methods the bugs are likely to be. This causes you to over-invest in writing unit tests, but writing and maintaining tests is not free. The risk of bugs is not the same in all of the code, and same for the cost of bugs. Not to mention that some of the code is better tested at a higher level with integration tests or end to end tests, but IME nobody takes TDD there, probably because it's too annoying.

* Overall, TDD seems like an overly elaborate way to proactively "gotcha" yourself with various unhappy-path edge cases before even thinking about the implementation – thinking that would, in fact, expose more of such edge cases. I find that instead of this weird backwards overhead-heavy process, the usual development process works just fine. Start with the big picture, and leave messing with small details for last. Whereas TDD requires you to bring up all the small details / edge cases upfront (otherwise it's indifferent from regular testing).

Like with most ideologies, there are some good high level principles to take away from TDD, but at the end of the day, most ideologies like this are designed to replace unreliable thinking with reliable process. And while that process may indeed reliably produce some kind of consistent output, it's not necessarily better than what you'd have without this process, or with a different process.
I have had some plans on updating the SRFI to add some reducers I did not include because I never actually used transducers before writing the initial implementation.

I don't really understand what you mean by types (my implementation stays monomorphic so new types are easily introduced by TYPE-transduce) , but I have thought about generalising things like numerical ranges by having something like unfold-transduce.
Yes. North American dishwashers don’t heat the water during the prewash cycle because the duration in time is too short and the 120V electrical service can’t supply enough power to heat the water quickly during that time.

European dishwashers use 240V (like everything else in the house) and so they can heat water much more quickly.

This electrical difference is also reflected in the fact that electric kettles (for boiling water) aren’t nearly as popular in North America as they are in Europe. Technology Connections also did a video on this topic [1].

[1] https://youtu.be/_yMMTVVJI4c
Yes, a properly done full body scan interpretation will take hours. It's about 30 minutes to analyze a scan of just someone's kidneys when there's already symptoms and doctor's note on what to look for.

The longest part is often just the paperwork and noting what was not seen.
What should replace it?
On a hot sunny day, the blacktop beneath the traffic jam is radiating more heat than all the cars on top of it are creating.

And a car engine is producing far more direct heat than the increase in ground-level ozone from exhaust pollution is increasing heat (from that same car).

Also the fact that cars have air conditioners is a total non-sequitur. The air conditioner in the car requires negligible energy compared to the force required to move 4000 pounds and 1-5 people at 70mph.
FANG+
https://www.ice.com/fangplus
Often said of X509 CAs that they certify the person attested in the SSL certificate gave them $40 dollars.

I for one, look forward to JFK's take on Abraham Lincoln's re-election. Thats what the Lincoln project is, right?

(at this point if you're still on X/Twitter, the question is "why" because it looks more like 4chan to me.)
I'm curious what people think a fix to this would be. My suggestion would be to have regulations on who is allowed to take on a loan. The ultimate decision can be done by the bank but some basic requirements can be enforced via policy.
Fully agree. Another and more efficient path to prevent waste is to buy aftermarket (second hand) machines, and to use them the longest time possible. There are a few small vendors offering refurbished and modded hardware, for example https://minifree.org