skysight-inc/HackerNews huggingface dataset:
If you've learned something interesting by investigating deeper, feel free to share.

I promise I'm not being deliberately disingenuous, but I'm honestly not sure what you think I've done wrong. I've read the article she linked about how Linus isn't a nice guy. I've read the entire thread. I've now looked at her main feed, outside of the thread.

I maintain that she is not criticizing the document, she's insulting the people involved. Do you think that I should be elaborating on the particular forms of insults that she's using? It doesn't seem relevant to me that her insults take the form of accusations of abuse, but that's honestly the only thing I can think of, that you might think I'm being dishonest about.
< I'm very hesitant to even level criticism at the CIA on HN.

But that is the exciting part, pretending that the CIA is concerned about you, or even knows that you exist.
The fundamental problem with the Mac OS X Finder is that it tried to combine the NeXTSTEP File Viewer with the classic Mac OS Finder, but the designs are complete opposites of each other, so the combination doesn't really work.

In NeXTSTEP, as well as in Norton Commander and its clones, the view properties are associated with the window. You create a window, set the window size, adjust the sort order, set some filter and so on – and then you can visit any number of folders with those view settings applied. Another window can offer a different view of the same folder at the same time. This is the "browser" approach.

In the classic Finder, and in the OS/2 Workplace Shell, the view properties are associated with the folder. A folder can only be open in one window – the window is the folder. Other folders open in other windows. Any particular folder will always open its window in the same position and the same size (and in OS/2 have the same window background and various other properties). This makes it easier to find things (for reasonable amounts of files) because they stay where you put them and have the appearance you give them. This is the "spatial" approach.

If these very different approaches are combined they break down. If you try to use it as a browser, individual folders can suddenly override your view configuration. If you try to use it as a spatial file manager, folders will have their settings mangled any time you accidentally open two views of the same thing.

Windows Explorer has the same problem.
Boy, you're really going out of your way to defend some guy you don't know who already admitted that what he did was wrong.
Did you mean 10TB?
What were the more appropriate solutions?
Beware of "The Problem Of Schemaless" can occur with a relational DB when you start defining columns as nullable. You end up with the same problem.
SQLRally Nordic 2015
Interesting blog posts (it and the preceding one). It seems that reliably emulating the x86 architecture is made even harder by a few features not found in other popular architectures, like an extra level of indirection on memory access (segment registers and the corresponding segment overrides) and most instructions having a memory-accessing variant (instead of limiting memory access to separate "load" and "store" instructions, plus a few specialized atomic RMW instructions).
I sincerely still prefer mongodb syntax because:

- Fits well with a programming language; {a: data.x} is better than 'WHERE A="' + data.x + '"' (sanitize?) or similar which are harder to read. SQL queries are good for direct input, mongodb queries styles are better to be used with a programming language;
Yeah, having said all this I do really like Miller columns for navigation.
Google – Inside Search
That leaves you with 450 years of unenployment for many engineers.
Show HN: Zazu, your personal email secretary
>Finally, ask them if the method of contact they used was the phone or written (not email) letter.

why should we have to use the phone, or a paper letter, when email is as good, or even better?
Sexual advances? Did we all miss something?
The key thing is that size is not the most important measure of a dev community. A larger community of low-skill low-time-commitment devs may be substantially less valuable in practical terms than a few highly skilled and highly committed devs.

There's also the question of if the people to whom you refer would change their behavior if the item they point to was removed. As we all know, what people say they will do and what people actually do often diverge.
Nothing wrong with that device, but it's also nice to know about its big brother:

http://smile.amazon.com/Amprobe-INSP-3-Wiring-Inspection-Tes...

This tester can simulate a 10A or 15A load and measure voltage drop, which should remain within 5% of its unloaded value (this is the recommendation in U.S. code). This can identify situations where connections are weak, or wires are too long or too thin.

It has also helped me to improve my wiring practices. It turns out that keeping voltage within 5%, under a 15A load on a 20A circuit, is pretty demanding, and a series of (say) 8 or 10 twisted connections may not meet it, if you are not careful with your technique.

The device can also test GFCI outlets by allowing some current to leak to ground. This provides an end-to-end test in situations where the GFCI is not present at the outlet.
Because he needs to face consequences for his behavior. He's a massive liability to his company.
Also unavailable from Android devices…
Apple Watch – To buy or to watch?
Soda Light theme + Mac Classic scheme works for me.
If you need the ability to run 32-bit binaries on an amd64 install or have Linux binary compatibility, FreeBSD has options to provide these while OpenBSD does not.

I run OpenBSD on one of my laptops, but if performance or compatibility are important factors, you might look at other tools for the job -- the different BSDs have different strengths.
PostgreSQL is a very different beast to what it was 10 years ago.

So for a while it didn't support use cases as well as various NoSQL/NewSQL databases. However, PostgreSQL has also been built by great bunch of developers who are happy to adapt and implement the new, instead of harping on about the past.

So personally I adapt that advice to instead "use evidence to guide decisions".
Isn't this because China has had internal migration controls for over 70 years, which are unheard of outside communist countries? Actually I think it's unheard of outside China.
Interesting to read both the article and comments. It's cool to hate Mongo nowadays but we use it successfully (for PEPS, open source: https://github.com/MLstate/PEPS).

The version of MongoDb used is not mentioned in the article. The changes between versions is a problem with Mongo but it improved much recently.

One problem clearly identified is the lack of model. There are solutions to this. For instance, with Opa (http://opalang.org) we use strong static typing to generate a database model and guarantee that the whole applications sticks to it. That leaves out model changes, but there are solutions for that.

Also, there is no need to have the whole collections in RAM, but clearly enough RAM for the "working set" helps.

In the end, Mongo is no magic so do SQL databases which have their share of problems too.
> I actually think a big chunk of the industry encourages unprofessionalism, because professionals do really obnoxious things like negotiate compensation.

I don't approve of this situation, but I also don't buy your general argument (especially for things like ping pong tables and beer on tap). You seem to be referring to "professionalism" as some concrete normative standard, but in reality, what is considered "professionalism" changes over time and differs between people, industries, and geographic regions at any given time.
Well put. Another comment ITT[0] also pointed out the global surveillance arms race and the futility of pressuring the US to unilaterally disarm. This is particularly true in light of the many legitimate global threats to freedom mentioned in your comment.

Knowing how unpopular this opinion is here, I still feel the need to share... Lawsuits like these strike me as either incredibly naive or a cynical public relations stunt. I don't enjoy my donations supporting either kind of effort and unfortunately, will likely cease future contributions.

The NSA does not surveil domestic communications without a court ordered warrant and I have heard no arguments to convince me that this is not a legitimate use of authority. If there was a single change to the NSA that I could advocate, it would be stronger and harsher mandatory minimums for anyone found in violation of the existing prohibitions on domestic surveillance.

[0] https://news.ycombinator.com/item?id=9177073
Why 'strict'?
s/You can/Anyone with two brain cells to rub together will naturally/
Yes. I pretty much agree with you and am happy for people to use ORMs (or raw SQL if that's their thing and they are into maintaining it). It's actually the underlying 'throw away all this old SQL database stuff' that is the biggest loss for people because they miss out on the power and optimization that's gone into those databases.
The real issue isn't "newtech koolaid" it is the definition of the problem.

I find that people that don't understand the problem like MongoDB for the ability to be "flexible" in designing and modifying down the road. Though I like to argue you have flexibility in SQL also.
The Warburg is Britain’s most eccentric and original library. Can it survive?
Part of the benefit of tests is that they are a form of documentation.
> HR exists for addressing problems like this.

They address problems for this for the company. HR is there to defend the company, not the employees.

Letting HR know about the incident will likely cause this person to be terminated.

I'm not saying OP should or should not do it, just clarifying the consequences.

Personally, I think what this guy did is

- a bit creepy

- pretty mean since he probably turned her down so he could ask her out

Having said that, what he did is NOT

- sexual harassment (there is no authority relationship at play)

- abuse of power
Many on HN, including myself, are very excited about Starfighter. However, many HN readers are probably already employed or can easily find employment if they desire. You guys and gal know that maximizing outreach will be critical to your success. You aim to find buried talent, but that talent must first know Starfighter exists and understand it well enough to be enticed to try. I assume you want to both find talent whose ability is not accurately represented in a typical technical interview, but also those who have aptitude for these skills but whose resume wouldn't even be considered.

I grew up near a small town surrounded by family farms. I've really enjoyed manipulating code and finding bugs in games and other software since middle school, and I suspected I was the only one when I was younger. There were very few "nerds" at our school who focused on computers, and even those that did almost never discussed the discovery or exploitation of bugs. Although I stumbled upon a few communities online that shared my interests, I hadn't found one that just clicked. I happened upon HN while learning more about startups, and it was just right for me. I'm grateful I found HN, but I wonder why it took me so long to find the community I was looking for.

I didn't even know about CTF games until tptacek's recent hiring post, and it was another "How could I have been oblivious to this awesome thing for so long?" moment. There are many people who are a great fit for your clients, and they won't know about Starfighter unless you cast a wide or deep enough net. How do you plan to address this challenge?

Good luck, and thank you for building this!
I had a business based on another company's API years ago, and they started changing a lot of their systems to work with mongo. The data lost a few useful points, like IDs and the speed and reliability didn't seem to be improved. My thought at the time it was, how about you guys just use postgresql? My comment on the mailing list about that seemed to be taken as an insult or naïveté. However, sure enough two or three years later they said they had all sorts of problems with Mongo and were switching to… Postgres.
This is why gender imbalance is bad for everyone involved. Not saying there should be more women in tech so men can find dates. The point is being around more women at work will help people learn what is socially appropriate.
The problem of schemaless database mentioned in the article is then replaced with painful migrations.

The trend to go back to SQL databases now is fueled by the "same" poor reasons why people were going for NoSQL databases. You can't have everything...
I did, for nearly three years. MongoDB was consistently the number one reason for site downtime.
A programmer and artist used brainwave data to turn a seizure into song
Because there's more at stake here than just "some guy who admitted he was wrong." People are jumping on this as yet another example of how horribly "male" the entire industry, how hostile it is to females, etc.
Writing a GC is an iterative process and the Go team are taking the steps to implement a modern GC. You don't work for 2 years and then throw it all in at once.
I know, but I'm just saying that Apple is has a substantial markup on the gold watch so why not for it's gold colored laptop. Not unless their gold watch actually contains 8.3 ounces of gold, at the current price of gold ((10000 - 350) / 1163.14). Perhaps Apple's gold watch is much larger and much more heavy than the standard version.
If the API surrounding the ORM is well-designed, using an SQL wrapper like this eliminates the possibility of SQL injection. There are arguments for not always doing things the same way.
It's not sexual advances.

It's not in a professional setting.

Not saying that what he did is OK (it's not) but let's keep our facts straight.
Any link (or bunch of links) for specific tutorial that you have followed?
If you think income inequality is bad now - imagine how much power/money/prestige/knowledge a 400 year old Sergey Brin would have. The rich getting exponentially richer.
What if he's a 10x engineer? He's a massive PR liability because of our insane outrage culture, but he's a very valuable asset for, you know, his actual job.
> * Keep your own legal counsel on speed-dial.

What scenario are you envisioning where she might need to save the 15 seconds it would take to dial from the contacts app?
> The "no recourse for fraud" meme about Bitcoin is simply wrong.

OK, but wait:

> There are not many dispute-resolution mechanisms right now... If Bitcoin catches on among a wider demographic, dispute resolution... will get built. The technology is very flexible and can accommodate just about everything...

Ah, OK. So the fact that there's no recourse for fraud is actually correct. But because, in theory, there could be fraud detection, then there's no reason to worry about fraud.

Reminds me of: https://www.google.com/search?q=assume+a+ladder
That makes sense. I wonder though if there is a better convention than "self". That by itself (to me at least) does not say much about which "self" we are describing. Maybe it is just a matter of personal preference, but I like to be more specific and descriptive.

It reminds me of the practice of using "throw-away" variables in for loops. Personally I would still rather name the variable "loop" instead of "i".
I've read the redis source code as an example of excellent C programming. Very impressive work sir, hats off to you.

I think your advice applies especially to systems programming, and less so to CRUD type apps, or even any in higher level languages. On one hand, you can hardly do anything in 100 lines of C. It's "too low level." On the other hand, once a C codebase reaches critical mass with enough supporting logic and utility code, you can accomplish more in 100 lines of C than you can in any other language.

There's something deceptively powerful about programming at such a low level. The primitives you reason about are extremely simple. But when combined with the rest of the codebase, and supporting libraries in higher level languages, suddenly you can leverage the primitive logic to incomparable levels.

Redis is a great example of solid, fundamental low-level programming enabling high-level performance improvements.
multiple page cleaner threads - this is nice.
Apple Products May Have Been Compromised by CIA Mass Surveillance Program
Entity Framework still generates pretty crappy looking SQL. It's nice to get a project going, but every time I try to look at why we are having performance issues in production and see the horrible query EF is generating I cry.
Look at the grassroots, bipartisan, loud and successful cry from the public not to enter Syria.

How many months did that work?

It is true that the system must represent the people. If and when it does not - whose fault is it? It can not be the people. We don't design people. We design a system to conform to the people, to communicate with them and to represent them.
I was pointing out that the fact that this guy was conducting interviews was understandable in the context of a small company - I have picked up interviews for team members before when they were unable to make them.

I meant no implication about it being acceptable in small companies - it is unacceptable everywhere.
> He is clearly abusing his position of power

He holds no position of power over her after the interview is over.

Obviously, he would if he had asked her out in the middle of the interview (now that would be way worse).
5 Psychology Studies That Will Help Growth Hackers Achieve Real Results
Explain it? Sure. There's always subtexts in human interactions. Pressure doesn't have to be explicit. When a policeman tells you to pull over, there's an implied "or you'll be arrested" that we all understand even though he never comes out and says so. When your crappy boss asks you to come work overtime on the weekend without any additional pay, there's an implied "or I'll make your life at this company difficult, or maybe just fire you" that he usually doesn't need to state.

Your crappy boss might not mean it that way. He might be asking with absolutely pure intent, with the idea that you'll say no if you don't want to come in, and you'd work extra because you like it, or believe in the company, or whatever. But it doesn't matter, the implication is still there, because of the power he holds.

Now, you get rejected from an interview. Shortly after, the interviewer asks you for a favor. There is an implied "if you do this for me, I might reconsider the rejection." Again, he might not mean it, but it's still there, because he has that power. Or at least you have good reason to think he has that power.

Is this claim falsifiable? Beats me. Ask a sociologist if you want to get scientific about it.
That presumes that the outcome of an interview is set in stone the moment it's decided. That is not how things actually work.
> Just like any car can crash. However some cars are more dangerous than other cars, just as some programming languages are more likely to produce insecure code than other programming languages.

> and the alternatives are designed from the ground up with security in mind

The RMS Titanic was billed as one of the safest ships on the sea -- yet due to poorly implemented protocols and practices, negligent leadership, and disregard for best practices, it resulted in one of the most catastrophic maritime disasters.

Using the most "secure" programming language in the world, one can still design very insecure code. Conversely, using the most "insecure" programming language in the world, one can still design very secure code. This would boil down to the skill of the engineers, competence of leadership and adherence to best practices.
Google Calendar for iPhone
But Google's cars can't even merge on the freeway yet, and they need vastly detailed maps which must be kept 100% up to date. (The existing car companies are trying to avoid the latter drawback, but there's no proof that they will be able to achieve this any time soon - it's just an ambition.)
Show HN: Bailiff – Codecademy of Web App Security
Agreed, but it's important to understand what drove the adoption of NoSQL and schema-less stuff as well as the related trend of dynamic languages like Ruby and JavaScript.

(1) SQL server software itself was clunky, hard to scale, complex to deploy in a clustered fashion, and generally "old" in a bad way. This made NoSQL seem like a breath of fresh air.

(2) Startups! Ship now! MVP! Fail fast! The whole industry has been operating on this ship-fast-fail-fast way of doing things that prioritizes development speed and agility over correctness. That's because half the time what you are developing will be thrown away anyway -- it will fail, or you'll "pivot" and rip it all apart and almost start over. No point in static languages, SQL schemas, or other explicit design elements in that world.

#2 is I think the more significant of the two for things like schema-less MongoDB or dynamic languages. Once you get product/market fit, you typically end up taking the crap you wrote with no types and schemas and re-doing it in a "real language" with a "real database." But as they say in Startupistan, that's a "good problem to have."
Which would make sense because they may be set to use Google's Public DNS Servers (8.8.8.8 and 8.8.4.4 and the IPv6 equivalents).

Google Public DNS has been performing full DNSSEC validation since May 2013: http://www.internetsociety.org/deploy360/blog/2013/05/confir...
I have of course no idea if Watterson is capable of producing a new work of the same quality, and neither have you I presume. Some artists are one-hit wonders, but Watterson have on a daily basis produced original work of consistently high quality for a decade. This is far more than can be expected by any artist in any media.

In any case it speaks to the strength of his work that you hope for more, but it is disingenuous to call him selfish or a hypocrite because of this.
Seems like there are a lot of edge cases described in this article that could be confusing when using async/await. Is anyone else feeling ambivalent that async/await is actually a nicer syntax than just using promises?
Unprofessionalism, certainly.

Harassment, no. That's simply not harassment.
Because he needs to face consequences for his behavior.

Does he? Is "facing consequences" the only way for someone to learn?

If I "faced consequences" for every stupid thing I've done in my life time I'd probably have spent the last 30 years in jail. Because at the age of 42, I've done a ton of dumb, inappropriate and just plain stupid things in my life.

Most of the time, someone has explained to me that what I did was wrong and I was able to learn from it and change my behavior. And look at me today - gainfully employed since I was 14, happily married, three children.

These zero tolerance policies of "facing consequences" for any infraction don't benefit society at all. There is no true binary decision of, Bad Behavior = Punishment, Good Behavior = No Punishment. Bad behavior can be challenged, forgiven and forgotten without having to ruin someone's career over it.

Repeated bad behavior, on the other hand... Of course you need to escalate at that point.
The boxing optimizations are really interesting. Great work, mozilla team!
Andrew Morgan EUC, VWorkspace and Linux Desktops: Nutanix NEXT Community Podcast
I started with SQL in the 90s and completely agree with you. People who do not know SQL tend to reinvent it poorly in a language not designed to work with sets of data.

We have started using jOOQ and it strikes a great balance of raw sql/typed sql and result -> object mapping. I don't ever seen going back to a heavyweight ORM again. There is just too much magic and lost time spend figuring out performance issues for a minimal gain in ramp up for those who do not know SQL.