skysight-inc/HackerNews huggingface dataset:
IMHO... It’s not an absolute of one being better than the other for all people or situations. A CS degree represents a more rigorous curriculum than most. It also used to signal an interest in the field. (Nowadays it’s getting more like Econ or Finance - a path to money)

If I am hiring an engineer, and I have to sort through which 10 candidates out of 200 resumes to interview, the CS degree is one heuristic of many to make the list manageable. If a colleague I respect hands me a resume and says “This is one of the best people I’ve ever worked with” I won’t even look at the degree or anything else on the resume.

Several of the absolute best engineers I’ve met are self taught without the CS degree. That isn’t incompatible with saying the median engineer with a CS degree is stronger than the median without. (And many with the CS degree are self taught too)
Jobs could move west into New Jersey if New Jersey were better connected with where the other jobs are. That is, you could hop on a reliable train to meet with a client.
Just to be clear - the machines referenced in the article are the larger more precise machines at police stations rather than the field test units.

As an aside - I think geography/access to alternative transport needs to be taken into consideration, if you live in SF or NYC there is no excuse getting behind the wheel after a few drinks - if you live in west Texas or Montana these laws make it almost impossible to drink in a social setting legally
> If someone has ingested alcohol and it's not yet metabolized I don't want them driving. It's irresponsible, full stop.

Really? I had a glass of wine last night. There are probably a few molecules of unmetabolized alcohol still in my system. Is it "irresponsible, full stop" for me to drive today?
That's super interesting, and glad to get a sanity check from someone with direct experience; I'm just an interested bystander.
Humans don't get to "change the world" to meet our imagination. All actions are contingent upon things we cannot understand. We are constantly acting into an unknowable future. The man-made world (which is a much thinner veneer than we tend to think) is the result of a roiling, chaotic process.

That doesn't mean we shouldn't try to "make the world better". It only means we have to think about what we are doing and stop believing that we know the solutions (or even the problems). Guess-and-check is the only way to learn things and all parts of that process (the guessing, the implementation, and the checking) are unreliable because of the unlimited contingency of the world. How can you measure the current if you can't step into the same river twice?

Anyway, the kind of utopian protest culture you're talking about is the exact opposite of what is called for. That culture is creating a generation of people who are shockingly easy to manipulate. And they will be manipulated.
Certified Open Source Hardware Projects
Drowsy driving should be as much of a crime as drunk driving-- absolutely. There is no excuse for getting behind the wheel impaired and exposing innocent people to unnecessary risk.
Statistiques et faits sur LinkedIn (2019)
I am talking about when FOX News originally still hated Trump and his stance on immigrants and history with women. They told Megyn Kelly what to ask him. Roger Ailes was unhappy with his feud w her. And the founder of FOX criticized him on his stance.

It’s just a fact that the Media is compelled to cover controversy and attention is half the battle. Ron Paul and Bernie are too consistent to be interesting to cover. Thus they need others to come out for them.
They are branding it as socialism, however the way the operate reminds me of seasoned 70 year old bureaucrats in East Germany.

Also, the politics are all over the place, it's left wing if it suits them.

[Obviously not everyone is like that, but it's the 30% that are visible on the Internet. There are many totally normal millennials.]
We use chef framework. Each deployment has specific tag. If something goes wrong, we revert to most stable chef tag and redeploy to all the tiers.
> If someone has ingested alcohol and it's not yet metabolized I don't want them driving. It's irresponsible, full stop.

Some would say we put discretion in the legal system to account for incomplete empirical knowledge. This article is asserting incomplete empirical knowledge.
Can confirm, I tried it, didn't work at all. The courts aren't stupid.
Blue-green deployment is the only way to fly: https://martinfowler.com/bliki/BlueGreenDeployment.html

There are two identical prod servers/cloud configurations/datacenters: blue and green. Each new version is deployed intermittently on blue and green areas: if version N is on blue, version N-1 is on green, and vice versa. If some critical issue happens, rolling back is just switching the front router/balancer to the other area, which can be done instantly.
I totally get your point but this approach seems a bit dogmatic to me. Even with modern CI/CD techniques and agile methodologies in place, rolling back could still be the best choice.

For example, always marching forward means that any time an issue is coming up, certain resources must be allocated in tackling the issue. That can't always be the case.

Smaller and more frequent releases are preferable and most of the time a single line change will fix the issue, but other times rolling back may be the best option.
In Indiana, if you are tested at a hospital with blood test, then jurors are required to back-date the alcohol to the time of arrest and assume the highest reading. Proof be damned.

The law was passed in 2008, and I sat on a case as a juror that went over this very detail.
DNS cookies are nasty. The POC tracks you between normal and private tabs, even with the Tor browser.
You’re being downvoted but it’s a totally reasonable reply for normal vendor software.
I have received dozens of speed camera tickets (a "work zone" trap that was active even when the work zone was de-posted, 100% of them were thrown out) and the cal info for the radar was included with the ticket, probably to save everyone time for trying to argue up that alley.
Zuckerberg is known to rave about Emporer Augustus achieving 200 years of world peace through "harsh methods".

So they cherry pick whatever stories they want from history to justify their mistakes.
Have you really eliminated testing because you use the shim? Realistically in my experience you really haven't
So... since the lawmakers who are all always 100% ethical and moral people that would never do anything except protecting the common good, it's certainly safe to assume that the laws that result are equally moral and have no other negative effects.

And those who think otherwise are not really innovators, but rather more or less traitors who wish to destroy the public good? Like that pesky Grace Hopper. And Uber (and every other startup in the last 10 years).

Got it! Thx.
"Raising property value" is a positive externality. That's what the government exists for. If you only consider the bad effects of everything the government does and not the net, you're going to inevitably be an anarchist. Which is weird, because "externalities" started out being a way to attack private enterprise.
For most people in Middle Eastern/Southeast-Asian cultures, "grow as an individual" = knowing the right contacts to get promoted.

You either own the business, are chummy with the owners or their chums, or you generally remain where you were when you joined.

The concepts of personal growth and rewards based on merit are usually limited to Western-style organizations for employees with Western-style education etc.

Many middle/lower class people have been working every day for literally decades for less than US$1000 a month without ever seeing a raise.
Simply telling a happy story here:

97yo neighbor had hip locked due to arthritis. Dr was scared of full hip replacement risks so neighbor lived a year without moving much. He and his wife degraded a bit due to this. Last month they insisted in trying. The man survived the operation, just a week later you can see how more lively he is.
>Old age stretches from 65 onwards

Which with average life expectancy is close to 15-20 years of remaining life. E.g tons don't make it to 70 even.

>Early retirees may spend 50 years or more "retired"

Early retirees are usually people who saved money / hit the business jackpot, not people who expect some others to work to pay them a pension.

We're also forgetting that (at least in civilized pension systems) retirees at 65 had 30-40 years of paying taxes (along with the employers part) for their pension scheme.
You can twist the words anything you want and repeat oppresion ten times in a row. But this house of cards simply do not resist the tiniest breeze of logical reasoning.

You know that both the first and the second referendum were just clownery and embezzlement. Everybody knows it yet.

We know now that of the around 300 detained for violent disturbs, 32 were directly incarcered for their participation in the most severe disturbs. Of this 32 people 27 where Catalonian independentists. Not evil spaniards "infiltrats" as they claimed. The rest were well known foreigners "professionals of violence" (from Italy and France for example).

We know that the anticapitalists can't build a Tsunami democratic app. For common people is just technically too expensive to hire programmers for that and maintain the system running. Only relatively rich people with lots of money to burn could be at the other extreme of the app.

Enough is enough. All the lies were exposed again and again by proven facts. Nothing that came from separatism mouths is trustable anymore.
I don't know what "social jetlag" is, but the 'lag' in jet lag is the latency between a newly imposed sleep schedule and the body's circadian rhythms. You can't have a permanent "lag" - any "lag" effects will be gone within at most a week or two. Whatever the pros and cons of DST, "jet lag" is not the right way to describe them.
The next beast is OpenWRT + any modern hardware supported by it.
I'd think even more carefully about these plans - if you are focusing on entry-level, then the job seekers who need this are not the pool of people who the hiring manager needs. They are the pool of people who are not even landing their first jobs. No matter how smooth you make it, at some point your service to the hiring manager will be, "Here are all the people who nobody else wanted to hire."

It would make more sense to do this by excluding entry-level jobs. Then experienced people can watch it over time, and selectively apply for something that truly looks like their dream job comes along. That will result in a pool of people to the hiring manager of, "I'm experienced, hire-able, and specifically want to work with you."
Aliexpress. Amazon. eBay.
We need more growth in cities and less growth in "sprawl" areas.
Driving 40 miles/hour anywhere with pedestrians/cyclists is incredibly dangerous. If hit at that speed, a pedestrian/cyclist will almost certainly die.

Ideally, urban streets should be limited to 20 miles/hour, and should not have drivers impaired by alcohol. (This is obviously unrealistic in the foreseeable future in most of the USA, where automobiles are treated like royalty.)
For our Kubernetes apps, every merge to master creates a tag in GitHub. If there's an issue that doesn't result in a failed health check (these would be rolled back automatically), we can rollback by passing the older tag into a Jenkins job.
It never went anywhere, still used for what it was used...
Unfortunately, developers rarely learn to look around corners until they have been burned a few times by not doing so (and often burned everything around them in the process).
Ideally we'd have the problematic code behind a feature flag and we'd turn the flag off.

For other issues we press the rollback button in the Heroku dashboard.

Heroku has its problems: buildpacks, reliability, cost, etc, but the dashboard deploy setup is pretty nice.
I don't doubt this statistic, but this is only an argument that we should find a way to better disincentivize drowsy driving rather than to soften the drunk driving laws. A few states have passed laws to penalize drowsy driving already.
I think it would be fine to let the CDN mark the common shared resource as "Caching: shared" as an opt-in, and also allow the including page to override with another header as an opt-out. If you are including shared cdn resources on a sensitive page, you are already doing it wrong. The CDN could already control its header to only send the opt-in for very commonly used resources in order to avoid fingerprinting based on less common ones.
"Invest more in education" seems to be a bad pattern.

We need to invest in job creation; a lot of those newly "educated" people have only raised their fixed costs while competing for the same jobs (that don't require the degree)
Here's a good documentary about Stuxnet as well: https://www.youtube.com/watch?v=TGGxqjpka-U
I'm not a molecular biologist. I've edited my comment to be more precise in expressing the spirit of what I meant.
How many serious SMTP servers in the entire industry have DANE records with DNSSEC signatures? Didn't the major mail providers just push SMTP-STS specifically so people wouldn't have to bother with DANE?
>> after having a cocktail or two with dinner

A drink or two won't do it. For a 180lb male, it would take 4 drinks for them to become over the legal limit
Off the top of my head I can think of several ways to compromise on this by making shared caching opt-in.

One way is for the requester to specify if the asset is shared. A new 'shared' attribute on html tags and XMLHttpRequest would do this. Browsers enforce cache isolation _unless_ the shared attribute is set, in which case it comes from a 'shared' cache.

So if the attacker requests a www.forum.example/moderators/header.css from the _shared_ cache, but the forum software itself didn't specify it was shared so it never got loaded into the shared cache, then nothing is leaked.

And as it would only make sense to opt to share stuff like jquery.js from a CDN, the forum wouldn't naturally share that css file and so on.

The other approach is for the response to specify sharing, e.g. new cache control headers. Only the big CDNs would bother to return these new headers, and most programmers wouldn't have to change anything to regain the speedup they just lost from going to isolated caches once the CDNs catch up and return the header.

In either case, sharing can _still_ be an information channel if the shared resource is sufficiently rare e.g. the forum admin page is pretty much the only software stuck on version x.y of lib z. The attacker can see if its in the cache, and infer if the victim is a logged-in admin or not. Etc.
1. Farmers are bearing the cost of implementing tech.
2. They own field data but in fragmented data sets.
3. Data is valuable when it’s collected over contiguous fields and when in large datasets.(think 100k acres)
4. We can’t pass it on to the food/consumer because farmers are at bottom of supply chain and have thin margins.
5. How can farmers..big and small..make money from the tech we pay for...afterall, we already know how to grow, but we need ROI and not something that ..net net..eats into margins.
6. Tech is too expensive now. Investors make money. Farmers don’t. It might be right to say that Agtech is a sector that is newly birthed and has nothing to do with agriculture. Because returns go to tech sector and investors in it. How is it helping farmers in $$ terms..in any meaningful sense.
7. Tech should be easy as and as cost effective as a pencil. Because we can make most of our decisions..especially small farmers..with a pencil and paper.

Our problem is labour..we need physics and mechanical tech..not AI and ML and data driven tech that first dumps our field data in silos and then give it away to someone else to profit. It’s like Bizzaro World!

8. Big tractor and equipment companies (yes, I am looking at you, John Deere) won’t create affordable field because it would cannibalise their existing product line.

Ok. What now? Perhaps this is why Ag bots and practical Agtech comes from the EU/outside USA. I don’t know if I am right in surmising that. Thoughts?
We actually just implemented something like this. Our entire environment is AWS CodeBuild, CodePipeline, and Lambda-based, but the process would be similar for more traditional environments:

1. Developer creates a PR. To be mergeable, it must pass code review, be based on master, and be up-to-date with master (GitHub recently made this really easy by adding a one-click button to resync master into the PR).

2. Each commit runs a build system that installs dependencies, runs tests, and ZIPs the final code to an S3 bucket.

3. Once the developer is ready to deploy, and the PR passes the above checks, they type "/deploy" as a GitHub comment.

3. A Lambda function performs validation and then updates our dev Lambda functions with the ZIP file from S3. Once complete, it leaves a comment on the PR with a link to the dev site to review.

4. The developer can now comment "/approve" or "/reject". Reject reverts the last Lambda deploy in dev. Approve moves the code to stage.

5. The above steps repeat for stage --> prod.

6. Once the code is in prod, the developer must approve or reject. If rejected, the Lambdas are reverted all the way back through dev. If approved, the PR is merged by the bot (we have some additional automation here, such as monitoring CloudWatch metrics for API stability, end-to-end tests, etc).

TL;DR - Don't merge PRs until the code is in production and reviewed. If a rollback is needed afterwards, create a rollback (roll-forward) PR and repeat.
I am not quite sure that smaller companies can offer higher wages.

Also, keep in mind a story of Bell Labs - the innovation power house hugely responsible for tens of Nobel Prize winning inventions such as transistor and solar cells. You need an insanely rich and powerful parent company to fund something like this (only Alphabet is kind pf doing it these days)
Tool Familiarity?

I've been doing embedded systems large and small for decades but before this year, never put anything with an ARM into production.

AVRs are still my go to for most things because I know them well and have all the tooling ready to go.
Yup, can't beat blue/green. A big part of the reason I recommend it is because unlike most other rollback schemes, the actual mechanism for rolling back is the same as for a normal release (a load balancer flip), so it's continually exercised and validated. To roll back, you literally do a deploy, but you just skip the step where you alter the bits on the dark cluster. This is highly unlikely to fail, since the only thing that has to not go wrong is the part where the software update is skipped, which basically boils down to a conditional.

Any mechanism for rollbacks that isn't tested continuously is likely to fail during incident response. It's a huge anti-pattern to have 'dark' processes only used during incident response -- same thinking behind why you should also be continually testing your backups, continuously killing servers to verify recovery, etc.
The Difference Between Good Leaders and Great Ones (2016)
I served on a DUI jury. Everything wasn't all bundled up into a single charge. In addition to the DUI charges, he was also charged with a long list of moving violations. In your scenarios, the list of charges would be different in each case. They'd both include DUI but the other charges would vary greatly.
What's funny is if you try YouTube adblock has more requests and takes longer than just chrome.
Yes. It's often used in safety-critical systems as an alternative to C, though C is still significantly more common.
Well, maybe. But on the other hand, the biggest tech companies seem to pay the most? Why is that?
I think a lot of people are unclear on the threat model here. If I have it correct, there's no way around it: either you live with the privacy leak, or you disable the shared cache.

The threat is that when you navigate to creepy website, it loads some library and tracks the timing. They use that to infer that you've accessed some resource from a sensitive site.

None of the workarounds with extra attributes are going to help, because they rely on the web developer to

1. know about the attack

2. know that some library or asset is a realistic candidate for the attack, and take appropriate action.

Neither one is that realistic. We developers are just too lazy to get stuff like that right, even if we know about it. Cargo culting is the rule.

As for the effects, I suspect this will have a modest effect on the average website. The sources I've encountered seem to cast doubt on the effectiveness of share cache (https://justinblank.com/notebooks/browsercacheeffectiveness....). I poked around the mod pagespeed docs and project, and couldn't find any indication of how they'd measured impacts when they implemented the canonicalization feature.

I wonder if you'll see a big impact on companies like Squarespace and Wix, where there are a lot of custom domains that are all built using the same stack.
What has access to alternative transport got to do with whether you're safely able to operate a vehicle? The law isn't about how much you're inconvenienced it's about how intoxicated you are.
What are your thoughts on socialism/Democratic socialism, from Google's long term perspective?
Yes, this. I vote for candidates that will do right by my children, other's children, the future of our planet.
Yes, your party affiliation correlated to what party you end up voting for. But this has been deemed public information, ever since the government got into the business of administering party primaries.
Las 2 steps are merged (ci/cd is part of the deployment to prod, but generally yes.

Also worth to note, priority bug fix is not really about pipelines it's more about the ability to dynamically reallocate resources. Depending on the complexity of the affected area we should be able allocate as many devs as it is useful to fixing it. (similar to "Fast Lane" in Kanban)
I was responding to the parent's comment re: differentiating between different "degrees" of offense. If the breath test system is flawed it should be replaced by a better test.

I agree w/ the other commenter who says that sentencing is the place where degree of offense should be considered.
Silicon Valley used to be very Libertarian.

In the 2004 presidential election, the San Jose districts had the highest turnout for the Libertarian candidate nationwide.

San Jose is still fairly Libertarian (the San Jose newspaper is still the most conservative in the Bay Area with a very Libertarian slant).

But the nexus of SIlicon Valley has been migrating north for a long time. SF has always been very liberal, and as the nexus of tech moves towards SF, so does it’s politics.
Unless the libraries are bundled in, which is the case for most of the stuff I use?

Exception - the analytics stuff I'm obliged to add.
It's not intended. The fine article prominently links to a page that explains how it works:

https://sirdarckcat.blogspot.com/2019/03/http-cache-cross-si...
Standard Oil, Bell, etc. Anti-trust breakups have a history of being good for employees and share holders. I'm fairly confident the same would happen here.
Here's an interesting video on why these old toasters are better than the modern ones: https://www.youtube.com/watch?v=1OfxlSG6q5Y
A lot of flight and safety critical software has gone c++ at least in the US. Do178b approved g++ clones started popping up about 25 years ago and have made dramatic inroads.