jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
The problem is inline with what venture capitalists seek for: a technological solution for something (so it can be repeated ad nauseum).

And the root problem is that some things cannot and should not be automated. There definitely is a need - but the software itself is racist, sexist, and more because it is badly trained with data whose origins are racist and sexist... But the key is that 'its software so it doesnt have a bias and therefore we trust it'.

And what do we get when we have this software subjected against us? We end up with black and darker skin people not being identified, we end up with software that discriminates against those who wear face coverings, and more... And when those maleficent softwares 'flag' people, the bias is that they have no bias and are to be completely trusted. And then the professors fall in line.

Whats the solution here? Well, it's ugly. Most universities are just paths to a degree for a better job - and those uni's know that. People demand a return on investment and will cheat so they don't lose their money. So cheating will happen. But the ProctorAI and ilk are setting themselves up for company-breaking lawsuits. And until we have enough people vaccinated, in-person is going to be pretty discouraged (for good reason!).
Tech recruiter here. The biggest issue is that people are random and often lie.
I heard that it was because helium filled drives have less drag on platters (thus, are more efficient) than air filled drives.
There are dirt cheap HD dash cameras that would work nearly as well.
oh wow, thank you. You are comparing us with giants and I feel we still have a lot of work to do on the editor to catch up with them. But we are working hard to ship improvements fast! Feedback are always welcomed, that's how we improve, so, much love for our early adopters <3
Straight up hilarious.

> Flush a toilet without assistance?

( ) Yes

( ) No *NOTE: If answer to any of the above is yes, please answer YES.
I spent over a year doing a full migration from AWS EC2 + ECS instances to GCP + docker + kubernetes. It was a huge task that has paid off very well.

1) Costs per customer are lower because you can fit more containers per VM due to kubernetes doing the scheduling for you. Customers also include developer environments.
2) The number of deploys is way up because there is a simple and established pattern that everyone follows.
3) The speed of creating new services has increased because of the established patterns with containers, kubernetes resources, and deploys. Thinks days vs weeks to get something running.
4) The number of Ops issues are lower because kubernetes handles so many things for you. For example, if a deploy is incorrect for some reason, the old service is sitting there running. No outage = no escalation = everyone sleeps at night.

Even if I was a tiny startup, I would still recommend using Kubernetes. The patterns, tooling and insight that Kubernetes gives you will save you TIME. The time saved is worth more than the tiny cost of a 3 node Kubernetes cluster. That is time you can use to develop your product and sell it vs time spent ftp'ing binaries to your Digital Ocean instance. :)
A 2-person game also is also just a good match with the fact that there are probably a lot more situations where 2 people want to play a game with each other than there are situations where a group is available to play. (Depends on the environment of course--school or a social gathering vs. a couple or a couple of friends--but I suspect 2-player opportunities are a lot more common in general.) That doesn't directly explain the high ratings for 2 person games given that 3 is even higher but I suspect it's one reason that higher player counts tend to have lower ratings.
> It is de facto a more complete test suite than the ad hoc one they've been making.

This is a _huge_ stretch. It's hardly surprising that the suite of tests MRI is running against aren't failing against a _released_ version.
The hard thing about Extreme Programming is that it depends on 12 practices, the practices are independent, and some of the practices make management and/or programmers uncomfortable.

The obvious one here is pair programming. Many programmers love pairing and immediately get the value, but many others find it exceedingly uncomfortable - so uncomfortable that they aren't willing to do it.

And on the management side, practices like "The customer is always available" are hard to do in practice, as they challenge organizational boundaries.

But without pairing, without a customer rep directly integrated into the team, without TDD, without collective ownership, without sustainable pace - it falls apart very quickly. And what do we get instead? Scrum. And not even real Scrum, but the BS pseudo-scrum that is pretty much tv and dessert first for authority-centric management and lazy uncommunicative programmers alike.

So how do you pull that off? Well, you hire a bunch of "scrum masters", who are basically just busybodies with no actual authority, to go around pestering people all the time and calling meetings in order to get anything done at all. There's no control, everyone is miserable, old-timers pine for the days of Waterfall, and it just sucks.
>But when I see benchmarks that suggest Python is 10 to 100X slower for critical server code, I have to wonder why anyone would use it for enterprise development.

Because CPU cycles are cheap and bugs are not.

>Dev costs are relatively small compared to operating costs.

Uhh, not in my experience.
For me, the reason is that things are never done, they're just "done".

Once I got past that mental obstacle and started releasing things that were done enough, then I got a bit addicted to it.
What?! Neural networks are explicitly designed to work in the fashion of - you guessed it, neural networks. Like, retina and optic nerve.
The guy who ran on "hope" was elected President twice, and then continued doing the same things his predecessor did that we "hoped" that he would stop.
I am pretty sure it has nothing to do with the average population being biased.
>would enable people to volunteer their time in areas like elder care, child care, culture and the environment.'

We recently went through a several year period of mass unemployment where many people had free time and those things didn't happen.
This article points to an attack that applies to AES-256, but not 128.

https://www.schneier.com/blog/archives/2009/07/another_new_a...
Is this related to the old lifehack about smearing toothpaste on your watch's sapphire crystal screen?
I am not sure if wirecutter reviews can be trusted anymore.

https://news.ycombinator.com/item?id=25993512

I like consumer reports. You pay money for subscription and they provide you a non biased review.
> Changing HW once the first prototype is done is expensive and it takes a lot of time for you to get the second iteration.

Sure, but minor fixes soldered in place aren't uncommon.

My experience is with firmware for embedded and consumer electronics, maybe video cards are sufficiently complex that none of the things I saw are even possible!

Lots of issues resolving power states, clock trees, monitoring buses, docs from suppliers were always subtly wrong, power management chips never quite worked how they were supposed to, things like that.
Docker and Redhat were both founding members of OCI. CoreOS probably was responsible for a lot of the initial conversations. They wanted a standardized container runtime after finding some limitations in docker which caused them to create rkt. Docker inc wasn’t super into changing anything and as history as shown, wasn’t terribly into working well with others. The industry was going to move forward without them but they were offered a spot on the OCI if they played ball.

OCI would have made docker inc entirely irrelevant if they didn’t join it. They donated runc (I was wrong originally, dyslexia sucks sometimes) as the reference implementation so docker continued to stay at the forefront.

They donated a very minimal implementation of containerd to the CNCF when kubernetes wanted to do things with the container runtime interface (CRI) to make it more pluggable. As a more purpose built CRI, crio is better suited for k8s.

Docker did not create OCI any more than Redhat did. Redhat and a collection of other orgs did. Docker and Redhat were besties after Alexander Larson added device mapper support to docker. This is what allowed docker to run on any Linux distro that didn’t include the out of tree aufs. Look it up. Redhat then made a lot of money doing container multihost orchestration with openshift v3, which deprecated their own tool, geard. When Docker inc accepted a ton of VC money, they realized they actually had to monetize things. This is the part where the relationship started to seriously sour. The company that helped make them so popular was now suddenly a huge competitor. This is what lead to the problem.

It wasn’t a grudge from Redhat I mentioned in the linked tweet. It was docker inc thinking docker was anything other than commodity. It just is some very nice UX and cli tooling with a container registry around Linux namespace and Linux control groups. They just put it all together very nicely for developers to ship code faster. Podman is also a commodity. At its core, it just is some json parsing and pretty wrapping around Linux namespace and cgroups. Redhat knows this, and they don’t hide it. They monetize openshift and quay, not podman.

Sorry if this is a bit scrambled. Long posts on mobile are difficult.
I guess it depends on your definition of "at scale" but IMO with Hashicorp's stuff and maybe something like Backstage you get all the benefits k8s but in a package that's much simpler to reason about and manage.
Your comment sent me down a research hole. Turns out, stock ticker symbols can be reused but I can find no evidence that NET was used before, which seems impossible.
Some of us aren't young enough for that :)
I find it very strange that people are voting this down. I mean seriously, we're talking about whether someone writing about development is "ordinary"... Given the above credentials, you're seriously arguing that PG is in the same category as ordinary random dev writing programming articles? Seriously? He's just not. That's just wrong. He's got stellar academic and business credentials - that combination is not common. I guess haters gonna hate and all that.
Even without recording too loud, room can have a HUGE impact on recording. As can mic, pre-amp, mic placement, speaker cabinet, pickup selection, pick choice, string choice, playing style.

I'd try to minimize or at least make transparent those choices. Either:

* Suggest an ideal circumstance (SM57 close mic'd as a reference or something), and note how this recording differs from the ideal

* Make people list all of the components that went into the recording

It's still going to be hard, because individual playing style can have a really big effect on sound (ie, Jaco is always going to sound like Jaco, even if you give him someone else's bass).

That being said, I think it's really useful to hear lots of examples. Just be careful about misleading people with regards to why things sound the way they do.
Completely agree, but that's missing the point. Lots of people apply who have published 100+ apps. The problem is that they're 100 variations of the same app, which has no value at all.

Most startups we know would prefer three bullet points on how you can help them win as opposed to a three page resume.
Hmm ... this was ranked #7 on the HN homepage a few moments ago, and trending up ... but now it's disappeared.

Wonder what happened.
It's all part of DocumentCloud, which means API access to the text of all that Guantanamo data. See how easy this can be:

curl http://www.documentcloud.org/api/search.json?q=group:nytimes

"total": 2821,
"page": 1,
"per_page": 10,
"q": "group:nytimes",
"documents": [{
"id": "86275-isn-10015-abd-al-rahim-al-nashiri-jtf-gtmo",
"title": "ISN 10015 - Abd al Rahim al Nashiri - JTF-GTMO Detainee Assessment",
"access": "public",
"pages": 15,
"description": null,
"source": null,
"created_at": "Sun, 24 Apr 2011 15:50:19 +0000",
"updated_at": "Mon, 25 Apr 2011 15:12:53 +0000",
"canonical_url": "http://www.documentcloud.org/documents/86275-isn-10015-abd-al-rahim-al-nashiri-jtf-gtmo.html",
"resources": {
"pdf": "http://s3.documentcloud.org/documents/86275/isn-10015-abd-al-rahim-al-nashiri-jtf-gtmo.pdf",
"text": "http://s3.documentcloud.org/documents/86275/isn-10015-abd-al-rahim-al-nashiri-jtf-gtmo.txt",
"thumbnail": "http://s3.documentcloud.org/documents/86275/pages/isn-10015-abd-al-rahim-al-nashiri-jtf-gtmo-p1-thumbnail.gif",
"search": "http://www.documentcloud.org/documents/86275/search.json?q={query}",
"page": {
"text": "http://www.documentcloud.org/documents/86275/pages/isn-10015-abd-al-rahim-al-nashiri-jtf-gtmo-p{page}.txt",
"image": "http://s3.documentcloud.org/documents/86275/pages/isn-10015-abd-al-rahim-al-nashiri-jtf-gtmo-p{page}-{size}.gif"
}
}
},
...
]}

Look at documents[0].resources.text:

curl http://s3.documentcloud.org/documents/86275/isn-10015-abd-al-rahim-al-nashiri-jtf-gtmo.txt

There you go. Now go build that tree and report back. :-)
I've been interested to see AWS status page misrepresent this through its icons while annotating the continuing issues.

1) Long before EBS API was returned, AWS adjusted the "Amazon Elastic Compute Cloud (N. Virginia)" status[1] for 24 April to show operational (green). This has since been corrected in the "Amazon EC2 (N. Virginia)" Status History.

2) Their own RDS service, which is instances backed by EBS, remained unavailable for its users, proving that #1 was false. If they couldn't operate a service (RDS) built on themselves (EC2) normally, the underlying service (EC2) should not have been considered Operational in the status page.

3) At present, the icon for "Amazon Elastic Compute Cloud (N. Virginia)" is Green for "Service is operating normally" instead of Yellow for "Performance issues", though the text description is not "Service is operating normally." but "Instance connectivity, latency and error rates."

4) It seems from anecdotal observation they're using the status page at least as "median status", or perhaps closer to "20th percentile status", meaning >80% of something can be down before it toggles to "Service Disruption".

[1] http://status.aws.amazon.com/
Yeah, survey monkey does $40M/year in revenue. The company took $100M in debt financing to pay the founders, and put cash in the company coffers. The $100 million was more of a tax-arbitrage deal than anything else. (In the US equity payments are double taxed, but debt service isn't)
I'm not as generous as you are in allowing that this just might be an issue of communication. As I understand it, he is a lawyer and also quite clever. I believe that he knew how it would be interpreted when he wrote it.
Any company that has a ton of eyeballs can make a Groupon Clone profitable. It makes complete sense for Google to do this.

#1 Google already has a ton of small business using their products (Google Places). They can easily create "deals".

#2 They have access to a ton of ad inventory (adsense, google.com, maps, gmail, etc) to gain a ton of subscribers easily
If these events didn't actually transpire the way that the author of this story suggests, does that make the story any less valid?
I don't understand, you ate nothing but juice and assume that is no sugar? It would be a lot of fructose, which would be glucose after getting through the liver.

Fruit and vegetables contains very little fat or protein (most of them anyway) so were do you think your calories came from? There is only one source left.. carbohydrates
I think it's important to note that the Times had an intro offer of only 99 cents for the first month.

Wonder how many will continue paying once they're charged $15 or $20.
I was surprised how easy it was to circumvent by deleting the cookies. I'm a big news reader so I might have been tempted to pay but now I probably won't. I don't know if that makes me a scumbag but I'm ok with it.
The last release had some big performance gains for the encoder: http://blog.webmproject.org/2011/03/vp8-codec-sdk-bali-relea...
No, the Offers team will have a marketing budget and bid through adwords just like everyone else.

Google has promoted their own products on their own sites outside the ad system in the past, but they got a bunch of greif for it. There is a Chrome ad on the homepage today that targets old IE browsers, but that is the only exception I am aware of.
> Boosting learning velocity/capacity/efficieny should help. Why must we replay histroy when teaching? But maybe we are not doing such a good job at consolidating/compressing knowledge as we used to since there is so much.

I think we are boosting our learning capacity and efficiency by better understanding how our minds work, and how this giant web of knowledge that we have created can be simplified. I'm absolutely dumbstruck that we still teach the majority of children using the same methods used for at least a hundred years, despite the (information) world being a completely different place than it was even a decade ago.
Guilds | Boston and UK | Remote | Full-time | Full Stack Senior Software Engineer

Guilds is building xbox live for crypto games, starting with a crypto wallet made for play-to-earn. We make it easy to discover new games, get the tokens and NFTs you need to join and create a guild to play together with friends. We’re creating a high momentum environment for engineers to do their best work, and if you’re passionate about building something unique and fun, this is the best time to join. We’re VC-funded, backed by the same investors as SuperCell, MoonPay, and Voyager.

About the role: You’ll be the first engineering hire outside of the CTO, so you’ll have a lot of autonomy and directly contribute to the product’s success. The ideal candidate is frontend-focused, but comfortable jumping in anywhere in the stack. We’re using Reactive Native, TypeScript, & Elixir/Phoenix. You’ll help build out a rich, responsive & engaging frontend interface for our gamer wallet. You’ll spend most of your time on the frontend, but should be comfortable building and integrating with backend APIs to implement features end-to-end. We’re looking to push the limits on our React frontend and build an ultra-responsive and highly engaging experience for gamers.

To learn more about working at Guilds, see http://guilds.finance/careers
To apply, email us careers@guilds.finance.
We need boots on the ground. We need people installing Linux rather than making excuses about why they can't.

Obviously what you describe is a problem. If Valve is going to spend the money getting games working on Linux no one, trying to make money, would port their game. It will hurt. It will hurt groups that specialize in porting Linux games.

Without the installs, whatever we do today is unsustainable.
A lot of smart people do dumb things. The Enron guys were pretty smart and went to jail. The people who blew up the financial markets in 2008 were very intelligent. Actually they were the smartest: made the public believe the world would go under if they couldn't keep their bonuses and receive a bailout.

I consider myself pretty intelligent and I have done plenty of dumb things although with some thinking I could have known they are dumb.
The chart shows a slight negative for the very poorest (that are eligible for benefits - it doesn't seem to take into account the people that don't pay taxes, aka the very very poorest, who would presumably not see such a loss).

Although this is fixable by taxing more the middle class if that's what we wish to do (aka, not being "budget-neutral")
Glp and G9a are ubiquitous as they are import epigenetic regulators (histone methyltransferases). Sounds difficult to work on, and hard to supplement if they play an important role in many cell types
That's in the short-term. It could be disruptive in a negative way.

There are probably already a number of EU companies in the space that could quickly be filling in these gaps. It would take some time to settle and have a dominant popular destination/network.
Cancellation dark patterns are endemic at this point. Case in point: I recently cancelled Dropbox Pro subscription. I didn’t record the entire process so what follows is my rough impression. I had to go through screens after screens of urging me not to leave. On the penultimate screen, at a glance I had no idea if I have successfully cancelled, there were something like two big primary buttons luring me back, I had to read very carefully before I noticed a secondary or unstyled button tucked in a corner that’s actually the cancellation button. Honestly felt like fishing out the real download link on one of those scammy file hosting sites.
or dont have a battery in your computer so it dies when they grab and run
Canned reports typically require you to have some level of knowledge about your niche. Different users need to see different data in different ways. You might consider taking a look at competing companies to see what they offer in the way of reports. It might make you a viable option for your potential customers.
Yup, that was me who asked the question there. :-)
Me neither. Nevertheless, the commit rate plays a role.

If the last commit is months old, you should be careful. If it is years old, you should stay away from it. (Example: The original Qmail mailserver was rock solid and djb's masterpiece of security. But you had to add custom patches for even basic features such as SMTP Auth. Why? Because at the time Qmail was written, SMTP Auth wasn't common yet.)

If the author then says that this is not due to lack of time, but because the software is "ready" / "done", this is an even worse sign. (Yes, I'm looking at you, Tilecache.)
Github does check if it's able to merge to the head of the intended branch automatically, and enable or disable the merge button.

But the point of the article is that the context shown in the files (diff) view on github is that of the common ancestor, and doesn't include later changes to the branch being merged into. In addition to not showing merge conflicts if they exist (even though it disables the merge button), it also hides logic conflicts. These are situations where a clean automatic merge is possible, but the result will be incorrect logic due to the slightly distant interaction of those not-shown later changes. The simplest example of this was in the blog post.

All that said, even the bitbucket diff view doesn't show you logic conflicts caused by changes in completely different files, or otherwise more-distant. Nothing really does, it would be too much.

So, in an ideal world, you thoroughly test the merged result (in addition to the feature branch itself) before actually merging into the upstream branch.
Thesedays, if it doesnt solve multithreading issues in a novel way, I'm not interested.
I didn't waste my time. Of all the kids that came one actually cared. We've kept it touch and I now consider him a friend. He just started comp sci in my country's most prodigious uni, which while it was obviously his own doing - I'm a little proud of :)

Then and now, I'm glad I focused on the ones that cared. The investment in them and subsequent payoff for them is extremely valuable. With the others, it wasn't even clear if you were doing more harm than good.

I was probably more cutthroat than most because I was the only mentor who showed up week after week, so I had to have strong boundaries.
The $80k from Bloomberg was possibly a PR move for both parties as well. I don't think the Edge was ever supposed to succeed - pretty clever though, Indiegogo as a marketing platform.
Please read the article, he's arguing that that is not enough, and would not be enough either under the spirit or the letter of the law.
Yep, the mentioned 7-14 table makes this very clear: it's a big-ass table of timing names with a column for minimum and a column for maximum (and a bunch of other columns for e.g. timing unit), where either column may be empty (and for many timings only one of them is filled).

In that table, TRSMRCY has a minimum value (of 10ms) but no maximum.