skysight-inc/HackerNews huggingface dataset:
I would agree that culture is a major factor - we briefly implemented Slack a few years back at a company before I left, and I watched it drive our Senior Programmer nuts, as we didn't really have good solid rules or behavioral standards for Slack. I'm not talking about a tome of laws and regulations, but just a few simple things like "Don't spam chats with non-work related items", "Don't spam looking to get someone's attention", etc. The Senior in question was an older guy who had a lot on his plate and and a bit of a short fuse. It absolutely ended up driving him nuts as now instead of relatively quiet and ignorable chat messages, he was getting spammed and pinged by absolutely everyone at once, and those in the office with less on their plate definitely treated Slack like their own IRC channel for shitposting.

Poor support from our management in general, and a poor delineation between private channels and public channels resulted in a lot of private rants being exposed publicly (not just from the Senior), and the end result was Slack was shelved for the time being and the Senior Programmer left the company.

My new place of employment utilized a multi-tiered approach, using Skype for quicker questions (with rooms dedicated to specific topics or aspects of the work), and anything requiring more than a sentence or two of background being regulated to an internal message board system. Our management is quick to shut down too much spam, and everyone in general is taught about the expected etiquete of the chat.

Without such precautions, I think it's too easy to fall into the more casual "shitposting" that is common for message boards and the chatrooms of old. Workplace chats are meant for very narrow and specific purposes, and it needs to be enforced that these are not the places to be spamming the latest gif you found on reddit/imgur.
Loading a single, large file into Redshift? I get the impression the author has a passing knowledge of Redshift at least. I'm not too familiar with BigQuery, but for Redshift, loading files in batches of total slices in the cluster is the recommended approach. No wonder it took 9+ hours to load that file.
And the author also doesn't mention distributing the data on a particular column. I wonder if he did random distribution.

And his problem with the field delimiter really shows lack of experience; of course you can't use a multi-length field delimiter. I've never seen anyone use a comma+space for a delimiter. That file could probably be about 75% of the original file size if he re-created it with just the comma as the field delimiter.

Sorry to bash on the author - don't mean to sound harsh but a lot of people are trying to do benchmarks but with minimal context and whatnot
I cant help but draw parallels between this and NNTP. This is essentially a really nice skin over newgroups, and thats not a bad thing at all. We have seen just how successful a modern UX can be on a old protocol with slack providing a UX to IRC. It is funny that we are slowly reworking the tools of the early computing community in slick modern ways.

It is also interesting that we as a community have completely sold out federated independent operators with a common standards defined protocol for soloed tooling.
That's not what a 90% reduction in the incidence of degenerative disease means. If degenerative disease occurs to 1 in 1000 people, a 90% percent reduction would be from that to 1 in 10,000 people. There's no need to make that claim.
Perhaps at a certain age, maybe 80, I could just turn
over my retirement for a guaranteed payment until I die?

Here in the UK, you can buy something called an 'annuity' - in exchange for a lump sum, a company offers you a fixed monthly payment until you die.

Some have extra features - like paying out for your spouse's life after your death; increasing the payment annually based on inflation; and even partial refunds if you die in the first five years.
no, if you look up official FAQ they say all calls placed abroad have domestic prices, international call from home country is not regulated yet, hopefully they will fix this nonsense soon
the text editors/ides I use today have bracket matching and with eslint it's been easier to track missing/extra bracket bugs, the example you have is heavily exaggerated, nesting like that is bad code with or without brackets
I would liken it to a newsgroup more then a mailing list, but they are very similar.
Congrats on finding a real problem and building something to solve it. You're about to fight an uphill battle.

Here's my feedback (from someone who currently leads the leads of 7 remote engineering teams):

• Not knowing if someone is available and if they will get back to you soon is very very bad for many conversations. For example, when you have a C-level asking for rapid turn around on something that needs to be done by someone multiple levels away from you.

• In remote teams, sometimes people disappear (e.g. car accident or civil unrest in a random country), and if you have no way to know, you'll eventually get fed up.

• The feeling of cohesiveness that comes from having realtime conversations, brainstorms and other collaboration is very important to managers (especially in remote teams) and convincing them that realtime talk is not a good default is going to be quite hard.

• As a result you will never be their default communication channel - at most you'll be the place they discuss bigger problems. But because you're not the default, you'll get destroyed by slack, who is the default. Most times people use the tool at hand that they are most familiar with, not the best tool for the job. I would encourage you to write a slack bot that reminds people to use you & helps them easily experience value from your product without you having to win the default spot.

• Finally, most people will have serious difficulty seeing the difference between your product and other product management tools that allow commenting in detail on issues being discussed.
PH has always limited who is able to post things, primarily for this reason.

I know people have called them out for being elitist, but they have always been very responsive to their community about posting things people make when you reach out to them.

Yes it requires a little bit of work (and a good product), but it's not really hard if you want to take advantage of what PH offers.

[Disclaimer: I'm a big fan, and very active user of PH for a few years now]
> old-school forums

Most open source projects still use mailing lists, which are even better than forums in that everyone can read and write emails in whatever client they prefer.

And yes, it's far better than chat for serious discussions, with a global group of people. You don't want to exclude the Americans from important decisions when everyone in Europe is awake and on the chat in the morning, and vice versa.

I think both systems have their places - if I have a quick question, chat is usually better. For longer more serious discussions, perhaps with code included, email wins.
Too much overhead. FPGAs normally have dedicated memory blocks, since making memory out of "normal" logic cells needs way to much space (registers, temporary buffers for single values, ... can often be embedded in the logic design, but not larger blocks of memory)
> The difference is that I'm not retaining any data when I do this

But if your guests knew you were retaining their data, and still chose to go in your house and give you their ID, it would be perfectly fine to retain their data.

> The analogy would be more apt if you let someone into your house, they hung out for a few hours, and then you physically remove them, and don't let them back in unless they show you an ID

What's wrong with that?
More realistically, assuming you have some experience as a developer, you can retire in 10 years of work if you play it right and are not against a move to a low cost of living location (country). That's much better than a life of toil until you're 65.
This relies on cookies. Just open the article in a private browser session and you will be fine.
what has this to do with roaming? they just lowered the fees, functionality is exactly same as before
I need to give this another look, but isn't that what a Google Group provides?
I'm curious about this as well. I was evaluating Athena a few months ago and was surprised that there was no good way to get my data into Parquet or ORC format without spinning up an EMR cluster and loading into a Hive table of the desired format.

My guess is that in the past there was no real use for these formats unless you already had a Hadoop cluster running. If Amazon wants these "Hadoop as a service" concepts to take off it seems like it would be wise for them to make it easier to get data onto S3 in a better format than CSV.
Nice to see a breakdown of the myriad of AVX-512 instruction sets. This isn't something Intel was saying much about prior to official launches.
I have to say I've never come across that usage of "PoC" before. "Proof of concept" and "piece of crap" I have.
Here are the 18 tech CEOs going to the White House today
10 years is also quite optimist on this type of mattresses. Their compositions are usually very poor with low density foams that deform easily with time. I'd be surprised if models marked that cheap last more than 5 years on average.
I'm sure it's not dead simple, but that doesn't mean it's worse by any stretch.

On further thought I wonder how much of the problem I have with slack and similar services (of which I actually tangentially happen to work on one) is more of a problem with process and expectations than anything else.

1. You are expected to be on chat, otherwise you suffer the appearance of not working - counter-productive since you are now subject to distracting notifications. If do-not-disturb settings and turning off notifications wasn't frowned upon this might be less of an issue.

2. Important information should be distributed through a more persistent second channel, email or a web-viewable email-list may actually be suitable.
When the tooling works, it has some really great things mostly related to IDE functionality. But when it doesn't it's a nightmare. It's more than just quirks. It's not hyperbole either, I just had a different experience with it than you.

I sincerely hope it doesn't die on you after you convert your codebase. I wouldn't wish that on anyone.

It's far worse than "the definitions for external JS libs are not perfect;" it's that the TypeScript compiler throws a tantrum when they aren't perfect, which is >50% of the time, to be generous. AllowJS is relatively recent and didn't exist when I started using it - which is shocking, because integration with the JavaScript ecosystem was a major selling point (just check the TS project site's front page). CheckJS is very recent and VS2017 doesn't even support it yet - for a language whose main selling point is tooling support, it's shocking that VS2017 doesn't let users update their TS version.

Another selling point listed on the front page of its website: ES2015 features. Except it doesn't provide Promises, Map, Sets (and I can't remember if they added Object.Assign support, but it also was not supported when I was using it). When you provide your own polyfills, TSC complains unless you provide typings and add specific config values informing it what you polyfilled.

Its 3 main selling points were JavaScript ecosystem integration, ES2015 features, and tight tooling/IDE integration. Each of those things failed me when I used it. The IDE part hurt me the worst, preventing my project from compiling altogether for a while. Every one of its main selling points has been a pain point for me.
One interesting challenge with this real-time vs. async communication challenge is that different job roles have different needs. At my company, most of our employees have been on the customer service side until recently, and Slack is great for them. Almost everything they need to talk about is urgent (even if it's not important) and temporary. They rarely have long-lasting high-level conversations.

Now we're starting to hire more developers and I'm realizing how disruptive it is for them to be pulled into Slack conversations all the time. So I've started using email more for communicating with the devs, and that seems to work reasonably well.

The questions I have are: (a) is it possible to have a single communication tool that handles both real-time and async properly and (b) does that even matter? Maybe email+Slack is a perfectly fine solution. Either way, it's obvious that only using Slack isn't a viable option.
1609 Map of Manhattan
> of course you can't use a multi-length field delimiter

It is indeed a non conventional format but thats how the source CSV was formatted on https://sdm.lbl.gov/fastbit/data/samples.html
Blue Apron will raise $587M in its IPO, valuing itself close to $3B
it was process updated every year for very long time

same as with depreciation of old Wolfram (?) light bulbs
Virtue signalling is only a subset of this problem. It's an important one because of the way it interacts with human psychology, but it's not the whole story. This goes into things like "not being able to post those photos of me getting blasted last weekend", being unable to partition one's identity such that you might be able to keep your sexual orientation details away from people you may not want to know them, and all sorts of other things well beyond the political issues of the day. (Sexual orientation may be a "big political issue" too, but in this case I'm referring to the personal dimensions of those issues.)
> Have a git repo for each package

Bad idea, because you don't want to lock all of Debian into one technology. Suppose Debian had similarly had one cvs repo for each package 20 years ago. Progress happens when people have the opportunity to independently build and test out different solutions without first having to convince the world that theirs is the best.

> with a simple issue tracker

Dunno what you mean by "simple", but there is an issue tracker for all the packages that's as simple to use as it gets, you don't even need to create an account!?

> Also move away from message boards and IRC to more user friendly tools.

I haven't seen message boards used by Debian!? As for IRC, what would you consider a more user friendly tool?

> Currently, it's too hard to report bugs

So, running reportbug on your machine is too hard?!

> inspect debian source packages

So, running apt-get source on your machine is too hard?!

> propose fixes

See bugtracker above?

> many open source projects has old infrastructure

What is wrong with old infrastructure?
In my experience what military-grade crypto really means is crypto that complies to requirements stipulated by various laws and directives related to protection of state secrets. This includes widely used cryptographic primitives (AES, SHA...), various NATO, or NATO member specific primitives (often with weird interfaces, eg. DES-like checksums in keys and such), complete cryptosystems for particular usecase (often with questionable security under security models used by academic cryptographers) and various utter nonsense that only exists in order to comply with aforementioned legal framework (eg. various "solutions" for connecting two systems with different security classification without actually connecting them)

In other words, military-grade means used by military, which has no meaningful correlation to security.
> The blue mountains and I imagine Tasmania where it gets too cold to hang your clothes up in the winter.

Clothes get dry regardless of the temperature: if it's cold enough, the water will freeze and then the ice sublimates into the lower-humidity atmosphere.
I've dreamed of Rackmacs for a while now.

Racket seems like a near perfect match for the domain. Start with a hacky one-off script. Augment with unit tests. Code base grows and starts becoming more stable? Progressively migrate to Typed Racket.
I see, thank you for the clarification.
Creating truly universal React component systems
Well that's it, they don't last as long.
"Software estimation is a chicken and egg problem. So I will try to solve it from first principles: how long did it take for dinosaurs to evolve into chickens?"
You bloody legend
Don't you only need to make that claim for those with degenerative diseases?
Inside the Largest US Voter Data Leak
Higher suicide rates and higher risk seeking is tied to how people treat men as much (or more) than how men themselves behaves. Studies have tested medical professional have a default assumption that all men are strong and healthy and thus men are less likely to get treated for psychological health problems compared to women.

Similar, in dating statistics it is very clear that women will preferential choose well earning men over low earning men. This pushes men in general to take high risk high reward professions.

Unless you redefine masculinity to include how people perceive and treat men you can't define it to be the causes for higher suicide rates and higher risk seeking.
That's correct. I will do it and try to update the article tonight. Thanks for the feedback
An Analysis of Civic Identity Verification Ahead of Their ICO
> You see, we are looking for the very best Recruiters, and it has been proven by major companies that the people that are able to do the job best have a very solid foundation in spreadsheets for quick applicant tracking.

Doesn't the punchline hinge on the above quote from the interviewer being false?

In other words, if the research really did show that testing on spreadsheet desiderata would get you the best recruiters, there would be no joke here.

edit: clarification
(0x15 suggests the 21st or 22nd issue, but the intro says it's only the sixteenth.)

edit: title's been fixed, this is no longer relevant
Yes but they also compare mid 1800s with late 1800s. No data readily available, but I assume it was still quite high in the late 1800s, especially with the working classes.
Except it is impossible to prevent it from typechecking node_modules; so if you have a dependency that was checked with a different version of flow than you are using, you may see errors that are impossible to silence.
Even if offset by trains and dirigibles?
Deploying a Static Blog with Continuous Integration
Would you recommend Laravel and PHP? I know PHP is seen as outdated by some people... But now that that NodeJS/MongoDB hype is finally receding, PHP actually seems like a sane alternative.
4 Ways to Boost Your Vue.js App with Webpack
Or maybe - and this is what I'm honestly inferring from your comment, it's not snark, it's just a hunch based on 16+ years of web development experience - just maybe there were issues with your teams code quality that means TS has been a huge win for you. Looking at that stack, it seems like someone in your organisation likes sticking plasters over problems.

I'm not a Javascript apologist by any means. I think Typescript makes an already quirky and clunky language worse.
Where? My inbox and outbox.

Obviously, people use email in different ways. This thread seems to have attracted a large number of people who exist in a text-only email world, but nearly every email I send or receive includes at least some rich formatting, and it's very common for us to include inline images of screenshots or other graphics as part of these emails.

And we're not web designers. We make project management software.

So: for me, mostly work email, though I certainly get no small number of personal mails with photos attached.

Again, that YOUR experience with email doesn't include rich text or inline images outside your spam folder doesn't mean those features are valuable and useful to other people.
Just a low-effort initial observation: "Works in IE8+, FF, Chrome" but the demo depicts an iMac display :-)

EDIT: Seems to work fine in Safari too!
wasn't sugar fairly expensive at some time?
We're touching on the limits of my understanding. Could you please elaborate?
Generally I've found that any forum project that also doesn't include reply-by-email functionality is a waste of time.
It's a comparison between people aged past 5 in both populations. It's not that unfair.

If you want to talk about unfair comparisons, you should look to all the people aged past 5 who wouldn't be alive without modern medicine (e.g. most terminal patients, some severe burn patients, some people with congenital defects, etc) and who inevitably lower the average health measures of our current populations. There's some seriously strong self-selection bias at work here: as medicine advances, the difference in health indicators between earlier and later adult populations would always be increasingly favorable to the latter.
When a problem that seems like it might drive FPGA adoption becomes sufficiently popular, it gets dedicated hardware instead. That's why we have GPUs, AES instructions, and CPU-hardware-based random number generators, and not onboard FPGAs. FPGAs basically get evaporatively-cooled out of the CPU.
From the README:

Why?

rqlite gives you the functionality of a rock solid, fault-tolerant, replicated relational database, but with very easy installation, deployment, and operation. With it you've got a lightweight and reliable distributed relational data store. Think etcd or Consul, but with relational data modelling also available.

You could use rqlite as part of a larger system, as a central store for some critical relational data, without having to run a heavier solution like MySQL.

Performance

rqlite replicates SQLite for fault-tolerance. It does not replicate it for performance. In fact performance is reduced somewhat due to the network round-trips.
For every one of these projects someone spent a considerable effort do the paperwork to get it pushed out, have it signed off as sanitized, non-embarassing, etc. It is a lot of work to get that done in bureaucratic and risk-averse organisations.

If there had been a community contributing back I expect that there would have been more activity, but if it seems like noone will, would you spend your time pushing out regular updates?
Could the difference here be that you're in environment where team boundaries are poorly drawn? To me, a team is a group of people who are playing the same game, who win and lose together.

Often I see "team" mean to use something much hazier, like "group of people with same skills" (e.g., design team) or "group of people in the same office". But I mean it more like "basketball team" or "soccer team".

In that environment, there is no team conversation that isn't pertinent, because we're all working to the same goal, and we're all jointly responsible for the same outcome.

That isn't to say that team members shouldn't work to be respectful. E.g., a team conversation over by the whiteboard is easier to let pass by than one where people are standing right behind me. But if we're on the same team, their problems are (eventually) my problems. I'd rather know sooner than later.
It proves there's nothing special about Casper — their market sways entirely amongst competitors by who has the best deal on an almost identical product.

It's like selling entry-level Windows laptops. The average consumer doesn't give a shit.
This discussion from 6 months ago brought together a bunch of introductory info and example applications:

https://news.ycombinator.com/item?id=13101924
I use Laravel and PHP for my job at a trendy start up. We use it to spit out JSON. I have no complaints, it's an absolutely fantastic framework - good support for the set of actions common to most web apps via the community and libraries.
This thing made me use React in 2013 (when JSX was still weird): http://blog.vjeux.com/2013/javascript/react-coffeescript.htm...

Now JSX is not weird anymore, it's just horrible.
^ OK so I was wrong about yarn being a server, but you can see how I got confused because "yarn start" does start a server in some invisible way.
It is still confusing. Look at how clear python files are for example.
Facebook shadow profiles: a profile of you that you never created