jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
Depends if you're B2B, or B2C.

For both, though, giving some incentive to be an "early adopter" is a must.

My company is SaaS; to get some initial momentum, we offered early adopters their first year at a discounted rate, additional functionality at a fraction of the normal price, and an account credit if they connect us to another customer that ends up working with us.

We actually still do the latter; nothing is better than having your customers be your evangelists.
Also, think like a winner.

(Yay, games with life.)

Be careful with this when there are actual status labels in play. Like rank or position. Act like you're an Ace around a boss or slight superior who's not an idiot and you may find yourself wearing that person's patience down very fast.
I really like your litmus test based on the clarity of a developer's explanations...I will definitely try that.

So for example, discussing the merits of a competitor's site in terms of how they are or are not achieving results in the background is a good start to understanding what the developer may be able to bring to the team?
Jason Fried has a great piece on this idea: http://37signals.com/svn/posts/575-but-theres-only-so-many-w...
This is why many experienced entrepreneurs tell you to ask someone who has money, or a business owner if there's anything you could do to improve their life... because they'll be your first customer, and they'll be spreading the word about you even when you're building the prototype.
For Samsung semi process part, it's just only TSMC is too good, isn't it? Intel, Samsung, and others can't catch up now.
I've just spent 5 minutes googling this claim. It seems totally unfounded. There are stories about how Google engineers, including Rubin, were nonplussed when Jobs first demoed the iphone, because they had no idea what was coming.

https://forums.appleinsider.com/discussion/161257/googles-re...

There are official explanations for Schmidt's departure from the Apple board that acknowledge the ios/android conflict but do not imply any malfeasance on his part. There are stories that Schmidt even left board meetings when iphone issues were discussed, precisely because of concerns about this.

I'm not saying you're wrong about this, but the evidence for such a claim isn't as obvious as I would expect if it was true.
I mean, among other things, Spain has a social safety net for people who don't work at all.

There are obviously shitty jobs in the world. There are obviously people whose choices do not include, you know, the ideal of material well-being plus fulfilling days. It is certainly a defensible position that the world owes it to people in that position to try to make their choices better.

Conflating those things to slavery makes you fundamentally an unserious person.
Lol this right here. This is it. "all skepticism is equally valid". A crock of nonsense. One side has pointed out, repeatedly, how that statement is true. If you don't know better, that's on you. This whole "aww my subjectivity" completely ignores the wisdom of the crowd of "no, really, this is snake oil, can we fucking not".

But as usual, people are looking to have an opinion spoonfed and are upset when it's not the narrative they wanted.
Its probably pretty common to use q for one of those commands. It is also easy to accidentally enter an errant q into the shell.

Call it qdns?
Couldn't disagree stronger with this. In fact, I love this problem, in that it gets rid of most of the complaints about engineering tech interviews: (1) it's "real world" (for the job in question), (2) can be reasonably done in the time alotted, (3) involves a task that is most common for developers (modifying existing code), (4) shouldn't require extra preparation.

I have seen many times where a user can actually explain the solution to a problem, but the translation from algorithm-to-code is extremely slow, or not done correctly at all. There is real skill in being able to output code quickly, even if you already know the English-language description.
I think I've ended reseting the password word everytime I've bought something online.
But there are people that stupid and the need to check such sites is just one more bit of overhead.

Hmmm, I suppose it's unfortunate that a final exam does not lend itself to requiring the use of a computer to demonstrate that you truly can program your way out of a paper bag.
Along those lines; TFA: "There's a creepy line we don't want to cross," Schmidt said. "For example, we could track people in real time, or use face recognition -- but we won't."

... presumably, because that would be 'evil' and we can trust that they won't do that?
Check out the book "Imperial Grunts" by Robert Kaplan. The US military also has forces in Kenya, Yemen, the Philippines, Mongolia, and Columbia.
As the founder of CloudFab.com (doing 3D printing as an API service, but originally targeted this market), I know first hand it's very rough going to get conservative prototypers, etc. to use something like this - I've done tons of leg work and sales.

This is definitely more of a maker offering, and so I wish them the best with with. Also worth a mention is the mostly dead 100KGarages.com initiative which did much of the same with a worse interface.
For all those looking for a compact guide to Linux kernel compilation:

http://www.kroah.com/lkn/
In the full example at the end this is used twice actually.
You can just sell the bitcoin for monero, then sell the monero for btc.

also, as time goes on, the proportion of btc that are "dirty" approaches 1, so these chainalysis strategies become less effective, assuming you aren't stupid enough to do some criminal act then cash out at a kyc exchange the next day from the same wallet
That's very sad and very true.

For some reason, I stumbled upon Hubbard & Hubbard Vector Calculus a few days after first reading this essay and it stroke me as the opposite to this wrong math teaching.
Also: https://twitter.com/teozaurus/status/518071391959388160

:D
There are so many interesting things in this video. Why would you choose to concentrate on race before anything else? There are some subjects where skin color is a very important dimension of the analysis, such as the political history of the post-Reconstruction US South. And there are other issues, such as the production of the world-changing Ford Model T automobile, where race played at most a very minor role.
Go to school, get a good education, go get a good job and live happily ever after. Guess what the world changes and that doesn't cut it anymore. Now I believe in making my own future.
Totalitarian or not, it is still a tyrannical regime.
I have heard that certain mid-size to large technology companies in Silicon Valley actually ding people on "culture fit" if they wear a suit to the interview. This was actually one of those pieces of advice my mom gave me that turned out to be bad advice.

Instead, I'd suggest "Know the culture that you're entering, respect it, and do your best to adhere to it."
GINA could be repealed. It was legal for gay couples to marry once and now it isn't. (at state level here in CA, admittedly - but laws can be repealed at any level)

Given that the health and the insurance industries have some of the most powerful lobby groups around, I'd be concerned that GINA isn't a guaranteed law for the rest of the life of this data.

If I do this (I'm considering it) then I would do it as John Doe with my PO Box, freshly created email address, etc. Getting kinda OT but there is a similar chain of thought when you get STD/HIV testing that you should do it as a John Doe for similar reasons.
The physical limit is still irrelevant to the debate: the number of people who want to use the lake could easily be far less than the number of people who potentially could use the lake. In this situation, the lake is artificially scarce according to the owner's property rights, not because of any physical limitations.

The physical basis is just an incidental detail. The ethical basis is that individuals must use their minds to survive, meaning they must have ownership over the produce of their minds to survive, meaning they must have property rights. To say that somebody who creates a work, whether intellectual or otherwise, should not have control over its access/distribution, is to argue against property rights and indeed the right to survive.

As the previous poster argued, pirating/stealing my intellectual property amounts to removing my ability to profit from my creation/property, which amounts to direct (physical) harm to me, the copyright owner. True, it doesn't stop me using my creation, but that's hardly the point. What if I invent a perpetual motion machine, should just anyone be able to then tap into my non-scarce energy source without permission? Besides, saying property should be granted on the basis of physical scarcity says nothing about why it should be granted to a particular person - it's a poor criterion all round.
Currently testing a CPU intensive algorithm I need for my current research project. Hoping it will save me some time. When I am done I will post the results!

[Edit:]

Pretty good so far!

~/stuff/Programming/faultire/src/
hendersont@glycineportable src $ time pypy sleepytree/test_metricspace.py
.......
----------------------------------------------------------------------
Ran 7 tests in 39.621s

OK

real 0m39.675s
user 0m39.150s
sys 0m0.170s
~/stuff/Programming/faultire/src/
hendersont@glycineportable src $ time python sleepytree/test_metricspace.py
.......
----------------------------------------------------------------------
Ran 7 tests in 69.442s

OK

real 1m9.483s
user 1m8.970s
sys 0m0.110s
I agree that as a practical matter it does what you want a majority of the time but generic collections let you mandate that an author has thought about equality for his object at least a little by implementing IEquatable. Particularly since a default definition of equality doesn't always make sense (as in the case of the fs).

As with the case of explicitly sealed/unsealed classes, it seems like Jon's MO is to make programmers think about some of these things more carefully rather than have a "correct 90% of the time" default; a sentiment which I can definitely appreciate. :)

Anyway, he discusses it at approximately the 36 minute mark. Well worth a look.
"randomly assigned to one of five different low-fat diet types"
- so most combinations weren't tested at all?
Ugh. procmail is disgusting. Consider maildrop instead (part of the courier mail server suite: http://www.courier-mta.org/maildrop/ )
>12 dozen eggs = 750ml of egg whites

I just want to make sure (12 and dozen right next to each other confuses my tired mind) is this 12 Dozen (as in 1 gross) eggs or 12 (a typo)?
Evidence for your assertion that our ancestors ate mostly fruit?
Tried the code and it didn't work. Can you mail me one at mmaunder at gmail? Tnx.
Because they're misinformed about the benefits of eating saturated fat.
Please do. I'll gladly pay for it.
Assuming that you're referring to working x% of full-time for x% of the money, then yes. I could easily live off $300 per week, but even minimal wage gives me NZ$500 per week. A well-paying job should give me about $1000 per week. Under those conditions, I'd choose a 12-hour work week in an instant.

However, you refer to a 4-hour work week. That's not a lot of time. Assuming that I'll still make at least $300 dollars per week, then yes. Any less, probably not. I still have to eat.
To me, an average citizen, this sounds absolutely insane. Why is there a need for such secrecy? How does that benefit us?
>This creates a scenario where a dollar into the insurance budget yields more than a dollar worth of value

Using this same logic, a better use of that dollar would be spending it on taxes as the even larger government can negotiate even better rates with healthcare providers, providing even more value to the employee.

Instead, the company fights to keep that dollar so they can spend it as they see fit, and the employee wants that dollar so they can use it as they want to.
Yes if a company does something that is not in the core specialisations, they would be expensive. Who guessed?
This is a really beautiful way to demo this feature. Thanks!
That's very strange. Can you file an issue or send me more info on how to replicate that issue?
assuming sarcasm?

if not, 40m people in CA -> this is $1.25/person/year. or 14m estimated cars; this is $3.57/car/year.
Does Japan really want foreign entrepreneurs? It's always been very conservative and while they may be polite to foreigners, that's very different from allowing non-Japanese to expand a business there. I think it's ingrained in the culture, and some of these bridges Tokyo is building might be too little to catch up to SK or Germany.
Real minimum wage was already $12-$14 pretty much anywhere. It basically just removed the 7.25 training wage for the first 3 months.
> It shouldn't be that shocking that Microsoft doesn't cater to your use cases if they can't gather telemetry to know that you exist.

User research isn't limited to, and existed before, telemetry. Telemetry, if used, should be an additional channel of user research, not an excuse to be lazy.
In the general case actions such as these are quite rightly prohibited--it's so easy to engage in self-dealing behavior. The best solution would be a waiting list of people to be notified. However, this was the initial rollout, glitches are to be *expected*. He found one and scrambled to do the best he could with the situation. There was no right answer, he picked the least wrong one.

We have seen other places where the rules were followed and doses thrown away. As far as I'm concerned any bureaucrat who ordered that should be thrown in the same dumpster.
I think if you time your destructive interference to the source of the audio perfectly and cancel out the sound, you haven't gotten the whole picture. As sound travels away from the source it reflects off surfaces and some of those reflections also reach the microphone. Those sounds have traveled a different distance than the original source and are no longer timed with your interfering element. Imagine holding your hand to block your direct view of a person in a house of mirrors but you can still see them in the mirrors. On top of that these reflections won't contain identical audio as the surfaces will absorb different spectral content, so now even if you had infinite perfectly timed anti-signals for each reflection, your anti-signal has spectral content that is missing from the incoming reflected audio and now your anti-signal is a signal unto itself. In order to create a signal that perfectly cancels out all of the copyrighted audio you would have to have knowledge about the form and materials of the physical environment as well as the position of the microphone within that environment.
Of course. The more they break Python compatibility, the more reasons new projects have to use the nearest competitor.. which is Go.
My personal experience is that I never used 10% of the features ShareX had, or so rarely It never made sense.
And large improvements to the language could result in millions of dollars of productivity losses! :-)

I'm not a big fan of "Now this language has gotten popular, let's add all the features to it that made our other language so unpopular."
Looks great thanks for sharing
Ah, that 3rd image reminds me of trying to send images to my ESC-POS darling. I think I've got an entire roll of garbage from Linux Bluetooth glitches corrupting the output (macOS works 100% reliably on the same binary stream.)

Will definitely try this library.
I'm a Principal Engineer at a big tech company, so I think I fit your description. But I don't think the phrase "technical specialist" applies to me. From being at a big tech company, I know of some technical specialists, that have an amazing depth of knowledge in one area. For me though, I got to where I am focusing more on knowing a little about a lot of things and being able to tie things together.

In our company, Principal Engineers (PE's) have varying responsibilities, but they usually revolve around (1) reducing ambiguity in projects and (2) proactively looking out for technical challenges that can bite the team in the long run. That can mean a lot of different things. For me, it's mostly involved writing design documents to come up with strategies for solving problems (and all that's needed to do that, such as getting iterative feedback, doing deeper dives in particular areas, reading industry or academic research, talking to people who have knowledge in more specific areas) and writing code to tackle more challenging areas. These problems are usually ones that would span multiple development teams.

The question of "transferability" that someone else brought up is interesting. At least in my career, I've jumped in to some pretty niche things that have proved in the end to be transferrable. The fact that I had experience managing a data science team before helped me get my 3rd job. A major factor in getting my 4th job came from the fact that in my 3rd job I had worked with Erlang. And my current role I got at least in part because of my experience at a telco startup. What I've found is that in any job, some stuff is completely dead-end knowledge (my domain knowledge about number porting will probably never be used again), some niche knowledge that might come up again (knowing how to do Bayesian probability analysis or write Erlang code), and some things that you'll apply over and over again (how to learn a new domain; how to work in an area where you are not an expert; how to understand customer needs; how to effectively communicate your ideas).

In any case, even if you aren't managing people, as you advance as an individual contributor, mentoring and helping other people grow will still be a large part of your responsibilities. In our company, the senior individual contributors often advise managers on how to think about the performance of individuals.
I see what you're getting at, and NPR definitely could have worded that better, but I think they're getting the point across fairly well. From a layman's perspective, ad tracking is the packaging and selling of user data.
I removed the facebook app years ago. If people insist on using facebook they should use it from the browser, in private browsing mode.
It would be great if you had extensions for LinkedIn and Twitter that eliminated posts like "Person X liked this" or "Person X commented". I hate that there's no way to use these platforms the way we used to: just to see stuff that was posted (or reposted) by first-degree contacts.

I now use both Twitter and LinkedIn via the web because I find the apps to be annoying (and for the most part, unnecessary). It would be great if you could take the functionality to the next level by allowing content blocking that removed the massive cruft that these platforms bombard us with.
I'm especially interested to see how this would affect funding for startups. What types of exits would be possible? Would investors be willing to fund in this environment. The net effect might (I say might, because I really don't know) be to actually cement big companies' hold on things because it may prevent potential challengers from even getting started.
None of it requires kubernetes, kubernetes just does it out of the box better than any hand-rolled custom stack that tried to do the same. Its a true joy to work with compared to the cobbled together stuff I've built and/or used in the past.
This looks super cool. Discussion amongst some friends of mine - how are you handling trust? I trust Vanguard not to pull a fast one after I've invested my money in one of their indexes, how do I trust JoeShmo when I invest in JoeShmo/dreamindex ?
What are you talking about?

I am responding to someone calling Apple a hero. I did nothing other than to point out the fact that like many things in life, it's not that simple.

There is no attempt to help Facebook or whatever you had in mind, that was your own projection. We can talk about 2 issues at the same time.
Pros: great news for value app developers. Unfair competition won't be as big of a worry and users will finally have to start valuing their apps (with money!)

Cons: small retail sellers will find it hard to advertise and won't be able to compete with big ad spenders that use more wholesale ad strategies
21. for a company that wants to piss-test you
Are you kidding me?

Currently:

<ul>
<li>Hello!</li>
</ul>

By your suggestion:

{
"tagName": "ul",
"children": [
{
"tagName": "li",
"children": [
"Hello!"
]
}
]
}

(and, yes, it has been attempted... JSON.stringify(document.body))
Anyone who was alive 20 years ago will tell you it's not a conspiracy. How much does health insurance cost now vs 20 years ago? Rent? A university degree? We can see the massive inflation with our own two eyes (and feel it in our wallets).
Congrats on the job!

We've already compiled a very good chunk of Racket to JS. It's called Whalesong (http://cs.brown.edu/~sk/Publications/Papers/Published/yk-wha...). The initial version of Pyret was in fact built as a #lang in Racket, and used Whalesong to obtain an in-browser implementation.

We ran into two major problems with this.

1. It was really slow. Whalesong faithfully implements Racket, including delimited continuations and all sorts of other fun stuff. But it suffers in performance. See the paper—we went through three different implementation strategies. But for all of them, Pyret proved to be too slow.

2. We wanted an entirely in-browser experience. The earlier Pyret implementation used Racket to do initial compilation, and Racket itself is not designed to run in the browser (it depends on its own virtual machine). Though Whalesong went a long way, it could not go all the way without substantially reimplementing Racket, which is an enormous enterprise. Absent all that, we would always have to rely on a "compile server". This was an obstacle for us in a previous system (http://www.wescheme.org/) so we didn't want to repeat that experience.

Ultimately, however, bringing Racket to the browser was not what we were setting out to achieve in Pyret. Rather, we were out to build a new language based on what we've learned from (a) teaching, (b) building systems, and (c) doing various projects on scripting languages. Pyret is our attempt to condense all that experience into a language that represents our needs well (it's still a work in progress). It just so happens that one of our (externally-imposed) constraints is to run in the browser with minimal server support.

In terms of effort, Whalesong was about four years of work by primarily one person, and it's still nowhere near done (because of how big Racket is). The initial Pyret was about 1.5 person years (though some of that was also spent building a peer-review system: http://cs.brown.edu/~sk/Publications/Papers/Published/ppkf-c...). The new Pyret is about two person years, and much farther along than the original #lang-based Pyret was. Indeed, the new Pyret is solid enough to be used in several classes without noticeable problems. So no, I would not agree with your assertion that the "same effort" would have brought Pyret to the browser.
FB is a marketing tool that is operated by a company that want's to make money.

I decided to take the marketing in my own hands and now have more control over it and reach the right people.
It's human nature to want more.

You pulled this out of your ass, and it's nonsense. Any anthropological study will tell you that hunter-gatherers are/were satisfied with what they could get. Anecdotally, there are vast amounts of people around the world who don't "want more".
Sure, it makes it even more deniable, but on the balance between 'well thought out conspiracy with I know-you know-I know you know I know' logic, and a fuck up, I'd err towards it being a fuck up.
> If Intel got rid of its ARM license, how do they build all these?

You're right - I misread what happened with StrongArm.
I'm building one. gitpush.com. I don't have anything up yet but send me your email and i'll let you know when its done.
Any more info on your Hacker Lab?