skysight-inc/HackerNews huggingface dataset:
Working class wages have increased, and that is clearly because of Covid relief. Or other Covid-related policies like halting immigration.

(I should be clear, this is still supply-side, but related to Covid relief. "Stimulus" money spent unproductively by the government is also supply-side.)
you have to take risk to earn returns. Sometimes that risk actually eventuates, and you have to either keep going, or take the loss.

That's why you must know the time horizon for your investments - if you know you need the money "soon", you cannot actually invest in the stock market.
They do wear their face, however, and governments seem to be all-in on using that too.
Really hope we see more amd in the mini pc space! This is such a neat system.
> I guarantee that would cause hearing damage.

You shouldn't be using your horn often enough to do that anyway, and if a single honk is loud enough to damage your hearing in this case, it's also loud enough to damage the hearing of a pedestrian walking near you.

I say do it. It'd be a strong disincentive to use your horn unnecessarily.
This might have been true in the early 00s, but not now: Based on satellite imagery analysis I've seen, large parts of the midwest are doing crop rotation with corn and soybeans in the main season, which more differences in the winder depending on weather.

The reason a US farmer chooses what to plant each year is the same as everywhere else: Given the state of their soil, the expected weather in their plots, legislative incentives and some guesses on crop value, they plant whatever they think will keep making the most money. The increase in soybeans as a useful rotation crop come from higher price per bushel vs 2000, and the increase demand making it easier to sell it in their local elevator. The extra $4 a bushel makes it much better than doing all kinds of extra treatments to the soil to keep trying to run more corn. As prices rise and fall, practices change to match.

And this is why modifying plants to lower the need of fertilizer can make such a big difference: A crop that before might not have been economical can become more viable. If a farmer has to risk soil health to have a somewhat profitable year, because anything else looks like losing money, they'll take the risk, in the same way that they'll cheap out in their pesticide applications. When the farmers are making good money with safer practices, they'll use them, and they'll keep investing. But for every 2012, when drought raised prices through the roof, and everyone else got their insurance payouts, there's many years where the farmer doesn't cover costs.

Always assume that the farmer is doing the best they can to make money, whether they have some organic apple orchard, or they are planting Monsanto soybeans.
My previous comment may have been slightly misaligned, but my point is that if tracking and personalised advertising were prohibited, and user intent via required browser features were legally mandated and binding, the question simply would not exist.
Jure Spiler was at a flea market and got himself a spectrophotometer

I wish I found cool stuff at flea markets. Best thing I ever found was a Palm TX for five bucks about four years ago.

he couldn’t get a readout frequency higher than 80 KHz – with the required IO readout rate deemed as 1 MHz, something else would be called for.

Putting aside the pin with serial data, I'm surprised the best solution wasn't to just point a webcam at the screen and OCR it.
Politics are everywere in life. I encountered tons of politics in grade school, from writing prompts to reading assignments, to history class, to the reading comprehension questions on the ACT. What is so special about math? Why are you more bothered about very tame politics than the obvious faults in the question?
> But in matters of taste, and specifically of wine-tasting, claims of 'expertise' have repeatedly been proven dubious.

I don't know about wine tasting but I've seen many claims that, in fields where objective data is limited, there is no knowledge, no quality, etc.; that reality is some extreme of relativism where everything is arbitrary preference. (What a depresssing, flat nihilism that results in!) For example, it's often applied to the arts and to things challenging, 'highbrow' - things that tend to make people feel intimidated or inferior.

The argument amounts to, 'if I can't measure it, it doesn't exist', and I think that is dubious. It's dubious not only on its face, but because most of what humans do requires subjective judgment; very little depends mostly on objective information. Finally, in fields where I've gained expertise (or more sophisticated perception), I've come to see that I had been missing out previously.

I've seen those claims many times - and people often believe what is repeated, regardless of evidence - but not proven.
For any decent employee, those are refreshed annually with a new grant that has a new four-year runway. If you're a good employee, the grants grow in size.
>Is it unusual for multiple outlets to publish the same article?

Quite common in publisher stablemates, and freelance written stories.

Edit, add: Stringer (Journalism) : https://en.m.wikipedia.org/wiki/Stringer_(journalism)
Arguably the best web development curriculum for children that I have seen from any of the top technology companies. Congratulations.

One question: Did you consider splitting up these pictures into smaller pictures? As an example, look at this page[1]. The picture seems to have a lot of things in there. Did you consider using multiple smaller pictures?

[1] https://microsoft.github.io/Web-Dev-For-Beginners/#/2-js-bas...
I don't think this will be solved until there is a radical rethinking of package managers, build systems, and programming languages.

Like the founder of socket.dev, I think that static analysis will play a role. However, I don't agree that that's the entire answer.

The static analysis has to be in the programming language used in the build. The language must have fine-grained permissions built into it, and those permissions should be able to be used both at compile time and runtime.

The build system should take advantage of the programming language's fine-grained permissions to allow the user building the software to restrict what the software can do at build time. It should be possible to decide, for example, that the build can only access files in a particular directory, and if that is violated, the build system will error. Same thing with network access.

The package manager should take advantage of the build system to build all software from source as far as possible, and to ensure that the package uses the build system and programming language to ensure the package cannot stomp on the user's computer at build time.

That is the minimum before these issues have any hope of being resolved.

But I still think that is not enough.

Say you have a dependency that you do not trust. If you could compile it into a form that could be interpreted by the same interpreter that the programming language mentioned above uses to enforce permissions at runtime, and if that interpreter had a way to transfer data to and from the code it was running, then you could have a system where you embed the interpreter in your code and use it to run your untrusted dependency. Then the untrusted dependency can be properly sandboxed.

Yes, you'll pay in performance, but you won't pay whatever you might pay if a dependency goes rogue.

That is the only way to "fix" these supply-chain issues until everyone actually vets their dependencies.

Disclaimer: yes, I'm working on a language, build system, and package manager with the above features.
I sometimes think that some Managers, and even primary founders, have such ungratifing gratifying social lives outside of work; They need the social bonding, and drama, that goes on in certain work settings

Kinda like my last girlfriend. I honestly felt if she didn't have an office to go to, and couldn't boss around someone beneath her in the organization around, gossip, and socialize; she couldn't sleep well.

Yea, if she couldn't make someone at work miserable--what's the point of it all?

She didn't even care about the money, it was an ego thing that I will never understand. That Bad Boss attitude who get things done. That, "Dam I'm good!" attitude.

This is not about her gender. I have met more than a few guys with the same flaw. I just didn't go home with them. I've had way to many bosses that loved the office "family".

I don't know how many times I heard we are a family here. Under my breath--I mutter, ya the Manson Family.

I get the social part, but why make everone miserable by dragging them into the office, especially if things get done at home?

I usually liked all by co-workers, and even enjoyed their company outside of work. I was single though.

Covid proved many positions could could be done at home.

If I had the power, I would offer financial benefits to companies that kept employees home.

Working from home, if you can do it, should be celebrated.

And I won't even get started on the rediculious commutes we did for the past 100 plus years. I've know guys who commuted 3-4 hours a day.

If global warming is a problem wouldn't those in power want us at home instead of driving. But dude--we have electric cars? Most of us won't be able to afford one for years, and even then. Most electricity is still not carbon neutral.
The moment you implement true Marxism is the day I will fuck off and play video games all day, and my feeling is many smart people I work with will as well. Why work hard to be the best at something if you aren't rewarded for it? I for one would not want to better the lazy bums in my community with my work and by your twisted logic in your post history that somehow implies all of Marxism is wrong as I'm a counterexample.
ah yes, the Balmer Peak. I'd say it saved me from missing a deadline or 2 in my youth.
The funny thing is though that for warehouse employees at Amazon, their job is so simple and all of their work is wrapped up and recorded for KPIs that if they slow down or become unproductive, they could be fired electronically without even assuming that the slowdown was intentional.

They’re hamsters on a wheel and the wheel isn’t going to slow down just because they’re upset about their situation.
"The employer sets the terms, where you work and how the work is paid. The employee either accepts the terms or walks away."

And employers can go on setting the terms of where people work; they are just going to have to do it facing the prospect they are going to lose a LOT of employees now that we've gotten the chance to work from home, made it work, and have spent considerable personal money optimizing our home offices and family lives around this WFH reality we've had.
In past few years, I got calls with offer to build artificial market making models (aka pump and dump) for crypto exchanges, with 7 figures payout per model + commission, I refuse to do such work, this is just disgusting, don't care how legal or illegal this is, it did not seem they have infrastructure for HFT in terms of Order Routing like it is on stock exchanges like BATS etc ...
It sounds like this is an example of things going too far, but I can totally understand a leader not wanting someone from a different department wrenching.

This bolt was probably inconsequential, but I'm guessing that he had to fill out paperwork enough times where some cowboy from the office fouled up a day's work.

I'm an engineer now, but I used to work on commercial boats. I came up with all sorts of semi-valid reasons to politely tell customers and superiors why they weren't allowed to do things (you can't drive the boat for "insurance reasons"). The real answer was: "I don't know how competent you are. The worst case scenario is that you injure a person or destroy valuable equipment. That probably won't happen, but a 1% chance of losing my job or having to deal with the aftermath is worth stopping you with a technicality."
Modern web development is dumbed down by shared APIs abstracting most of the hard problems into patterns (arguably a good thing as there is way more consistency in web dev than infrastructure), but the concepts are still quite complex. Heck, React alone is a fairly complex piece of software that 90% of its users take completely foregranted let alone understand why it became a popular choice. Low-level front end is no joke
But can the Poetry World tell the difference?
> The bits we don't enjoy (stop-start traffic and some motorway driving) have already been taken care off more than a decade ago.

Not really. You're referring to assistance features that require continuous driver attention. I think that highway driving, and perhaps even city driving in some parts of the world, could be completely automated to a level of safety that is far higher than humans can achieve.

I am deeply skeptical that we will ever see a system that can drive in all current road conditions though; I think it's more likely that road systems will eventually co-evolve with automated driving to a point that the automated systems simply never encounter the kind of emergent highly complex road situations that currently exist which they would be unable to handle.

I also enjoy driving, and my 40yo car doesn't even have a radio, let alone Autopilot, but I think it's likely that within our lifetimes, the kind of driving that you and I enjoy will be seen as a (probably expensive) hobby rather than something anyone does to get to work or the shops every day.
If I have a script I want to work on both BSD and Linux, and I do want to rely on uname, I usually do something like

bzip2 -dc 1.tar.bz2|tar xf -
Could you point me at the product from Sonatype you have in mind? I’d genuinely love to see it. I’ve seen their SAST offerings, but not much around SCA/SBOM/supply chain analysis.

It’s also worth pointing out that my original comment was probably less specific than it should have been—SCA isn’t new, but tools to help and mitigate risks around the digital supply chain have up until recently been fairly primitive as far as I’ve personally seen.

Many vendors can tell me a package has a vuln. Very few can tell me which vulns can actually be exploited in the context of applications I secure. Fewer still can give me a cohesive view over time of what packages or maintainers start doing things out of the ordinary.
> that an article's subject

or the subject's enemies...

There are a tremendous amount of defamatory hit pieces that show up too. I wonder in a S230 analysis if deletionpedia itself is the publisher of this material: after all, it wasn't the original author that went and dug it up and published it on their site. I hope they've received good legal advice.
TraceTogether is being phased out as the end of the pandemic nears. Haven't had to use it for weeks now.

As for privacy issue - they ended up stating that they would only use it for serious crimes e.g. they used it in a murder investigation. Seems like a reasonable compromise for better public safety.

(I recognize that not everyone will agree on that, but the level of safety and security in Singapore is mind blowing.)
I'd suggest that it is political insofar as money = power. Consider how valuable an editor could be to a company with an interest in keeping criticism of its product(s) out of the public eye — WP's lack of transparency makes questions about the above possible.

At the same time, note I also said or policy-wise — there are plenty of vested interests with government backing for standardized care policies, which can include prescriptions (side example — government diet standards trickle down into the food provided for everyone in Federal care of one sort or another). Standards of care put requirements on doctors, and maintaining those standards of care is of quite some importance to those who have built reputations and careers based on certain drugs and procedures, and to a host of other parties. If these sorts of things aren't political, and tied to political interests, I'm not sure what could be.
> anything that requires effort and "cultivation" to understand is not art.

Tolstoy said that? Where? His work require a bit of effort and cultivation ... so does an incredible amount of art. Emotional communication does not at all exclude effort or cultivation; in fact, you can 'hear' a lot more if you sharpen your perception.

Cultivation seems hard to distinguish from any learning. Who is uncultivated, a four year old? Is art only what a four year old understands? That greatly limits what it can communicate to people who have become cultivated beyond that.
These employees were management. They are explicitly excluded from union activities because they represent the company.

Bezos can fire management whenever they like.
Thank u for the help :)
Different pavements have different noise characteristics, and poor pavement decisions probably contribute the most to noise.

Will the state fine itself for loud pavement? Do they even have a standard they would hold themselves to for loud pavement?

I'm all in favor of reducing exhaust noise, but without going after loud pavement, it is a waste of time.
There are multiple different problems with different solutions of varying impact.

I think you can probably split the two areas of interest into:

1. A package maintainer's credentials are compromised

2. A package repository is compromised

And the two attack vectors into:

1. The build script(s)

2. The runtime library

You can cut off the "repository is compromised" path with signing. An attacker doesn't have the maintainer's private key so even if they can modify source/packages on the server they can't "trick" the client into verifying it.

(1) is harder. Let's assume we have package signing, we know that any package we have was signed with a key that we hope only the maintainer has access to. At this point, either the maintainer is compromised or malicious. We can make compromise harder in a few ways, but should ultimately assume compromise.

One way to reduce compromise is to have the signing key stored on a hardware token that requires proof-of-presence for signatures.

Still, at this point we have "build script bad" and "library bad". Both are much harder problems, with solutions that you've alluded to to some extent - that is, sandboxing behaviors.

What this requires is a way to say "this code can do these things". This is how browser extensions / mobile apps work - they have to declare their permissions and you have to ack them any time they change.

Doing this for build scripts isn't too hard. You can run the scripts in a "hermetic" build system and have each script execute serially in a restricted environment - if one needs networking, give it networking, etc. There's no native support for this but imo it wouldn't be that hard to add it in.

Doing this for libraries is much harder. You'd need a native capabilities system in the language, and changes to capabilities would break the API. But sandboxing entire processes isn't that hard. The vast majority of services don't require egress to the public internet, meaning that an attacker is already going to have a hell of a time if they just get a shell into some box that they can't even communicate with. So I'd say start there - limit processes to what they can do and that limits the impact of a compromised library.

So altogether, none of these approaches seem super hard. We have signing, sandboxed builds (they can be pretty loosely sandboxed tbh - do a 'fetch', and then cut off internet for build scripts/ limit fs access), sandboxed services.

It'd be nice to have something more robust, but today you can do everything above without a ton of effort.
So if I took a single slice of bread, and I put Welch’s grape jelly on half of one side, then I put Peter Pan crunchy peanut butter on the other half of the same side (rectangular halves, not triangular halves), and then I carefully folded the slice of bread over in half along the line where the jelly meets the peanut butter, then what do I have?

I rest my case.
I think part of the issue is the word "battleship" which laypeople think just means a "warship", but is actually a specific category of warships.
Never heard of violence upon someone for not paying a ticket. They might have their credit affected, their wages garnished, their vehicle registration suspended, and so on, if they continue to ignore bills. That isn't violence, but it is consequences.

But I'm curious how you'd prefer it be handled.

What if I don't pay rent? Should I be allowed to live there forever, simply because no one, not even the police, is allowed to physically remove me from the property if I refuse to pay and refuse to leave? I wonder how this ideal world you imagine actually works.
The combined total of Rust, C, and C++ is only about half of the Firefox codebase. So it's more like 20% (of the code that it might theoretically replace).

Because the code written in HTML and Javascript isn't going to be rewritten in Rust another language, probably ever.
Yes this seems particularly scary to me, vendor lock in seems to be more and more ubiquitous. I understand passwords have their pitfalls like phishing and reuse but FIDO's bluetooth / close device detection seems very invasive and potentially flawed.
I wonder if the flatter an organization is the more working from wherever works for them. The flatter the organization the less need there is for "management by walking around" by middle and upper managers.
People submitting crypto transactions to miners are their clients, as in the miners get paid when one of their transactions occur.

Index front running is not illegal and is based on public information. So, this may be a form of legal front running.
Having a home lab is awesome!

In my case it is hobby fun rapidly turning professional. The way to fund hobby / new work is to get your investment at home to pay for itself. Free tools and gear essentially.

Early on, as I picked up skills and scored deals on equipment, I ended up able to take side gigs and or take on special projects. Sometimes I would do these on a "keep the gear" basis. No money changes hands. Recommended.

Pros:

Picking up new skills

Research on ones interest and terms

Flex time working is possible

Reduced commute

Work when ideation is high tide, so to speak

Cons:

It can be expected to work more

Personal / company boundaries are less clear (IP and overwork)

Can be expensive

Need space

Summary:

Personally, I have always had a lab at home, and I rarely take company gear home. Sometimes I have, but I try to buy my own, or the gear from the company.

I have had to make a few career jumps and the next one has pretty much been made possible by what I had at home and what I could do with it.

Be very careful about IP. The reward for that caution can be a real opportunity for you.

It can be the place where you show young people stuff they would never see otherwise and or, until much later. This happened for me as a teen and it was a huge boost! And it was where home lab started for me. My bedroom was my shop.

Of course, you gotta sort this for your scene too. The CEO letting people take gear home is nice and maybe a non issue for people. Depends on what one is doing and or plans to do.

Overall though, I deffo recommend doing it.
It wouldn’t, I’m just commenting on the origin of those sound regulations.
You consume grocery bags, you dispose of trash, you buy floss picks, and you put fuel into a car, and those things alone put you way above a village dweller from a third world country, who buys no floss picks, owns no car, puts no fuel into a car, and does not buy groceries at a market that hands out bags.
SSO for your gov't ID is a no-brainer
Thank you! It's a particular style of sketchnotes that Tomomi, the artist, has perfected. They images all kind of fit together to give a holistic picture of the topic.

One thing, I did a lot of the smaller non-sketchnote art on https://aka.ms/ml-beginners, embedded as infographics. So that was a different art strategy.
I thought Nigeria was a major oil producer. No ?
If yes, why are they paying for fuel in dollars ?