skysight-inc/HackerNews huggingface dataset:
I agree. I feel using JSX for example to define application routes (a la react-router) or do any other type of non view logic is just wrong.
Good article, succinct and accurate info. Only thing though with the end where banking will adopt Ripple software but not use the native asset imo is very unlikely. It's also constantly used as FUD. Banking will certainly leverage the native asset to get real time gross settlement. Which as far as I'm aware is only available when you use XRP. So for a financial institution to pass on that is just not going to happen.
I've had few friends who tried methamphetamine. Two of them were completely turned off by it but one got addicted and very quickly disappeared (we still wonder what happened to him). They were all just hardcore dudes from bad homes hanging out with other hardcore dudes from bad homes.

It seems like the young folks who try meth do it because they know someone attractive or otherwise fun to be around who is doing it. It is my completely uneducated guess that the first person to get addicted to meth, had it perscribed by a medical doctor.
Hi, I'm a Redux maintainer. If you've got some suggestions on how we can improve the API and usage, please file an issue!

I'm currently looking at revamping our WIP React-Redux v6 branches to use hooks internally. Looks really promising so far, but I'll have to keep playing with it and see how it turns out.

Our goal at the moment is to publish React-Redux v6 that is basically API-compatible with v5, and then open things up to discussion about potential alternative API approaches for a future v7.
FDA approves new drug to treat influenza
I was always better last year :D

I am reminded of this article, “A brief history of who ruined burning man”

https://journal.burningman.org/2016/10/philosophical-center/...
Some key differences [1]

> ply, by Tobais Waldekranz, is another front-end to BPF. I like it. It isn't complete yet, but has some interesting differences to bpftrace: ply emits instructions directly, whereas bpftrace uses llvm's IR API (which can be fairly difficult to code in). ply is also C, whereas bpftrace is C++.

> It's possible that ply will find its users on embedded Linux and minimal environments, whereas bpftrace will be popular for large server Linux.

[1] http://www.brendangregg.com/blog/2018-10-08/dtrace-for-linux...
Agreed! I always come to this conclusion as well.

A product that I've been keeping an eye on is Subform [1]. Apart from Flash-esque design tools, it includes more or less "novel" ways of defining the layout of the app. I think the layout tools set this product apart form similar offers. One of the main developers has a talk about the philosophy behind the UI of this app [2].

The same team is working on an app to use state machines to define UI interactions, which is also super interesting [3].

1: https://subformapp.com/

2: https://www.deconstructconf.com/2017/kevin-lynagh-choosing-f...

3: https://sketch.systems/.
> The CEO ... believed that regularly letting people go was a way of eliminating bad apples and forcing people to work harder and smarter.

Microsoft called it Stack Ranking.
The pay is extreme - top of market, but I think more than people realize (even people in silicon valley).

I've heard 400k cash is not that uncommon.
that's five.
God yes. In many aspects writing AS3 apps was so much better than writing modern JS.
Welcome to English as it is spoken, vs, English as it is defined.
That author is Andrew Clark, who's also a React core team member and helped design and implement hooks in React :)
> Do you mean something like this?

:r! lshw | grep network -A2 | grep : | cut -d: -f2- | paste - -

Not exactly. More like:

- Open vim with the output of `lshw` as content:

lshw | vim -

- Examine the raw data

- Send the whole content of the buffer as standard input to the given command and rewrite the buffer with the data read from the standard output of it:

:%! grep network -A2

- Examine the returned dataset. Iterate:

:%! grep :

- Examine & iterate:

:%! cut -d: -f2-

- Examine & iterate:

:%! paste - -

This way, you can examine the output of each step of the pipeline individually, so you can construct your command incrementally. And it is up to you to decide at which point a command will be run instead of it being run automatically following every keypress.

Since the dataset returned by the last command will be visible in the current buffer, you will be able to examine & play with it full screen. You will be able to clean or transform some parts manually (this is frequently needed in data science).

You can always return to the previous/next dataset by pressing u/Ctrl+R (for undo and redo), and examine your command history by pressing ":" and then Ctrl+P/Ctrl+N. (Or you can open the command history quickfix menu by pressing "q:" to view/copy the last several commands at once.)

And since you are in a full blown text editor, you can take advantage of other helpful features such as folding, saving the current dataset to a temporary file, etc.

If you are comfortable with more than a few UNIX filters, VIM can be a very convenient and fun tool to play with data.
Actually even then, if you value your employment, I feel like this is a sacrifice you make when you cross the rubicon to director-level and above.
Software Mechanic is a great brand. I'm stealing it :)
Is this able to run on webasm?
> trying to find people who can work in Groovy on Grails projects - it's not easy.

That's because many of the people who used Grails to build a website didn't intend sticking around to fix the bugs or maintain it -- they just wanted to get paid and move on to hawking themselves as experts in the next fashionable technology. Others chose Grails because they saw they could introduce loads of technical debt thus giving themselves an opportunity to charge a high hourly rate later on.

> I won't be making the Groovy mistake again any time soon

Oh, so you didn't choose Grails so you could skim an agent's fee from sourcing these people? Many did.
UT Austin was much like that for me. Highest possible ratings from the previous manager, and then the new manager was hired.

Technically, I was caught in the campus-wide 10% across-the-board layoffs, but it's very clear why I was made eligible for that list.

Funny that it happened to be the same month that I was recovering from surgery to remove my cancerous thyroid gland.
Talking about lookup tables without using constexpr is like pissing away performance.
Why are you accusing the parent of suggesting Apple is in the wrong for hindering GrayKey's efforts? They didn't say that. The question is whether an employee has an ethical obligation to their former employer to disclose security vulnerabilities discovered after their employment was terminated. I agree with the parent; once your employment has terminated, you do not have any moral obligation to disclose information gained after the termination. I would argue you do have an obligation to disclose security vulnerabilities discovered while still an employee, or at least refuse to exploit those security vulnerabilities, as knowledge of them is essentially privileged information that belongs to your former employer. But any knowledge gained after termination is fair game.
An interesting video on free ports
https://www.youtube.com/watch?v=vsA_L1t4vXY
I studied Latin in school, and we studied Catullus 85 and 5 (which is mentioned in 16).

We discovered there was a book of English translations of Catullus in the library, which we used to "help" with our homework. I'm pretty sure it didn't contain 16, because we would definitely have noticed. :p
The most important part to note is that fentanyl analogs are being used along with other inert substance to increase the mass and potency at street level. The problem with this is people easily underestimate the potency and use too much on top of the issue of varying amounts of fentanyl used to cut increasing risk.
Good points... But same as MongoDB replaced as database of choice for developer training it can be replaced again
About 30 years ago, I read a book about lottery winners and the stories read very similar to Mr. Whitaker's, back when a mere million dollar payout was a big deal.

Though it's possible the book had a selection bias - because who would read the stories that ended happily ever after?

I'm not sure regular schmoes can avoid problems with large sums of money because we're not used to dealing with wealth or the problems it attracts. Rock stars, pro athletes, and even heirs to family fortunes have similar problems.

Given the likelihood of winning, I've already spent too much time thinking about what life modifications might be needed but here goes --

1) If you know or can access someone who has tons of money (e.g. Bill Gates), ask them. Though people such as Bill Gates probably have most of their wealth in investments, not cash.

2) Get a second address or at least access to a place under someone else's name. Assume your driver's license info will become public knowledge.

3) A couple of lawyers on retainer is good, at least one who specializes in defending against frivolous lawsuits. Maybe one who specializes in such lawsuits, just to knock them out of the pool of possible attorneys who would come after you. I heard Michael Avenatti might be available.

4) Having a friend or two in the police might help, they can find people willing to pull security details. The key phrases here are POST-certified, sworn officers. I'm not as big on hiring military-grade "operators" but maybe if you find yourself dealing with kidnappers or other hard-core types...

5) I prefer lump sum, because governments have a reputation for altering plans. Not to say a government wouldn't just confiscate one's holdings, but it's usually easier to not give something than to take it back.

6) If you are a man, seriously consider a vasectomy. That won't stop the paternity suits but you'll sleep a bit easier. Apparently celebs have doppelgangers who bed women on the reputation of others. That may be a harder scam to pull off in the age of smartphones.
Okay, so I will pee in the cup -- on stage, right in front of them.

Now let's see if they drink that lemonade.
I think this was a good read and well written. It is hard to summarize such a concept as our banking system is allowed to print money in the form of paper assets (loans) and then cash it in for low interest debt through fractional reserve lending. The part left out and where I'd like to see the article go if expanded, is the public company stocks and bonds. People are separated into the haves and have nots through the accredited investor distinction and have nots are mandated to use the 401k type retirement plan which is usually backed by another form of printed asset called a stock. Then some dude/chick is appointed control over that empire as a CEO making a huge amount of that stock guaranteed win or lose with the company. He pays the labor force, which can be quite substantial, with cash derived from selling those paper assets to the workers 401ks and then borrows on bonds backed by it from the banks who turn those loans into fake money at the fed. I saw one comment about a tin hat scenario. I may not be spot on 100% with how it works, but this is how it appears to work to me. This broken system is what I think crypto can fix. When you think about how much actual power crypto puts in the peoples hands... basically the power of a federal reserve, it is not that hard to imagine the restof the infrastructure forming around it. Only this time it has something that the fed does not - a true intrinsic value. As ridiculous as it sounds that computers processing power values the currency - is it not a lot less ridiculous than the concepts outlines in this article? After reading the bitcoin whitepaper and realizing the hash protected the network and turns would be bad actors into a support mechanism, I realized that crypto is so much better than a central bank system. As we decentralize the surrounding industries to this new type of federal reserve we might be able to get the value back into the money we use.
How to disrupt the brogrammer vibe with 1 simple change
It is a management problem. I have been pushing back since I joined the team but the problem is that there's so many execs and people screaming for this app to be released.

As senior developer on the team I am having to fight bad software practices and "just ship it " mentality.

In a way I am panicked because I don't know what the product owners want and they in turn dont know what the business want.

Therefore I am trying to engineer against management's incompetence and I don't see that being fixed anytime soon.
Which idea are you thinking of? (Flash was very similar to tools that had been on the scene for many years before, like Director and it's predecessor VideoWorks.)
The X hole
Reed thought he was creating a high performance culture without accounting for the very nature of humans. The Netflix culture deck became a blunt instrument for managers to fire people in the name of performance and radical candor. I can’t wait for the lone Netflix engineer to write a great article tomorrow about the great Netflix culture he/she is personally experiencing. Kind of become a standard PR response these days.
I'd think the correct solution is better project/product management, but as I know that isn't always an option...

Overall, given the information I am not sure NoSQL is the right path, but there are some inherit flexibilities it gives you with a constantly evolving data model. But that doesn't come for free, and your coding has to evolve to support a dynamic data model which can be challenging on its own.

Simply based on your limited description, I'd avoid Cassandra, not because it isn't awesome, but your use case doesn't seem to fit. Plus with mostly newbies and skeptics it would most likely fail in implementation. Cassandra requires a lot of design planning up front in general to get it right, it is not the most flexible of the NoSQL alternatives in terms of dynamic data model and querying, but it provides other trade offs that make it a great tool.

You can stick with SQL and just use a data migration toolset to help you manage field updates etc. Set a policy for allowing additions but restrict column removals etc. It has been done for years as this isn't a new problem, just means you have lots more to manage and data migrations become a key aspect, so data access code also needs to be isolated and flexible.

Alternatively you could still use something like Postgres or MySQL and properly use JSON storage and index it which would let you have some benefits of NoSQL without moving the entire app. For those tables you can define well, do so in proper sql, those you can't do so in JSON storage.

And of course you could move more to a full NoSQL solution using something like Mongo. Mongo is solid if used properly, but again comes with some trade offs, so you'd have to evaluate those.

Personally, depending on how much data exists already and how complex the app is at this stage, I'd opt for pushing back on project management some and/or moving to a more toolset driven SQL solution with planned data migrations as part of your sprints. That plus make sure you add a flexible data access layer to isolate the changes to the application as best as possible. If you or someone on the team had more NoSQL experience or even a different team makeup my recommendations might differ.
After working in organizations where terrible performance is tolerated, this seems like a breath of fresh air. We've all worked with some asshole/fuck-off who we wish someone would fire. It starts to eat away at morale. I'd rather take my chances an not have to work with the problem children.
I feed the API a URL to an old XML web service WSDL. It determines how to re-org the methods available on the WSDL into RESTful API friendly resources.

Hey, you asked for what I wish existed, not what was readily doable :D
That code might produce two byte reads and a shift and the bitwise-or to reformulate the 16 bit value in memory . In the original code the 16 bit read feeds directly into the lookup table.
Working with China is more in the "maybe" category.
Ten ways to make voting machines cheat with plausible deniability
I'm a software engineer and I do most of my own car work. Can't do everything though, I don't have a lot of room for tools that I'd rarely use.

Paid someone to fix my air conditioning vents though because I'd have to half disassemble the interior of my car to do it and I knew it would take me longer to do than I could have the car out of commission. I really hate the vacuum controlled vents in mid 2000's Ford trucks. I had a vacuum leak - somewhere.
I nearly had a heart attack today when there was a sidebar banner image about this that I mistook for a banner ad.

As punishment for scaring me, I blocked it with uBlock.
Yes, lots of startups need external funding, say, venture funding.

But the US is awash, from border to border, in successful businesses, say, Main Street businesses, that never got external funding. They were, say, bootstrapped.

Maybe if pick an information technology (IT) project carefully, then can bootstrap it or start it with just own checkbook and no external funding.

Really, an IT startup should need less money to start than a lot of Main Street businesses. E.g., can quickly need $100,000+ in spending to get to the first $1 of revenue in an auto body shop, auto repair shop, asphalt driveway paving company, dentist's office, pizza or Chinese carryout restaurant, etc. Heck, in my neighborhood, the guys mowing grass show up with $100,000+ in equipment.

In contrast, for, say, a Web site, can plug together a quite powerful server for less than $2000 and can get a lot of relevant software tools and infrastructure software for free or nearly so. Can run ads from ad networks. If people like the site and keep a $2000 server busy, then in a year can have more in pre-tax earnings than could get from a venture seed round.
Is Computer Science Really All About Math?
FoundationDB Summit Program Announced
I don't review grants for my friends. This is a strong community norm. It's unethical to do so. This causes a shortage of qualified reviewers, but that's less of a moral hazard than conflicts of interest.
I've never seen an employee getting fired "because their manager didn't like them".

I've seen plenty of employees getting fired because their manager, who didn't like them, gave them a bad review.

In fact, across companies and even industries, being disliked by your manager is the single most reliable way to get fired.

Anyone claiming you can be disliked by your superior yet reliably keep your job - is BSing you.

Since this is, essentially, what the spokesman is stating, then I call typical PR BS.
Rare genetic sequences illuminate early humans' history in Africa
A problem with that old saying is it ignores the vast amount of sugar needed to make lemonade.
Since I started using Mobx I'm actually enjoying using React purely as a rendering library and user input. No Redux, and certainly no setState.

I really don't see the point in hooks.
Don't test implementation details.
This dude set up a "this is for free" sign and then some other dudes just swooped in saying "we'll take all of this" and then just replaced the sign with "$500k".

The problem with this is that it disincentivizes the sharing mentality. Nobody wants to be the guy who gets taken advantage of, yet everyone benefits from free sharing of knowledge. And then once in a while you have dudes who swoop in and make everyone look stupid and make them re-think whether they should ever share their findings with others again.

Obvious could make this right if they wanted to. Yet they are standing their ground on Twitter, it seems.
2/3rds of that article, including everything under "Deep Dive Austrian Economic School Principles", could equally describe Keynesian economics.

Economic laws are the same no matter your ideology and aren't disputable. But there's a whole universe of dynamics that are poorly understood. I think what distinguishes the Austrian school is an ideology that considers state intervention invariably negative; and separately that we should all use a gold standard. (I'm not sure how they square the passive, descriptivist perspective wrt market volatility on the one hand, with the prescriptivist preference for a gold standard.) But the arguments behind these policy preferences aren't falsifiable.

The basic argument for Keynsian interventions is reflected in Keynes' famous line, "In the long run we are all dead."[1] From a policy perspective, it doesn't matter that a free market will eventually return to equilibrium (or is by definition in a stable cycle regardless of volatility) if in the short term people are starving and will never live long enough to see better days. Keynes was railing against the gold standard and effectively deflationary monetary policy which manifestly was causing severe deprivations in Britain.

The Austrians counter that volatility is induced by interventionism. No doubt that can be true and has been true, but it's also true that intervention can reduce volatility; indeed, all forms of human organization have sought and ultimately succeeded in reducing extreme volatility. Austrian vs Keynesian seems more like a debate about normative social policies than concrete economics.

[1] Longer quote: "The long run is a misleading guide to current affairs. In the long run we are all dead. Economists set themselves too easy, too useless a task if in tempestuous seasons they can only tell us that when the storm is past the ocean is flat again."
Other than your opinion, do you have any arguments to offer?

Otherwise I can just tell you my opinion as someone who works in academia: It makes perfect sense, and so far I haven't met anyone who was able to offer any better alternative to peer reviewing.

That being said, there are some reasons why there are more shady papers and journals today than there used to be.

The #1 reason is that many policy makers and science administrators got this unhealthy obsession with merely counting indicators, which leads young researchers to chase publication after publication regardless of the quality.

The #2 reason is that there are way more researchers competing for tenure, but jobs have barely increased and public spending on education and universities are overall low in comparison to other areas. You get what you pay for.

So there you go, another opinion, but at least a qualified one.
DNS deployment - see Infrastructure as Code.
Redux is based on the Flux Architecture. In particular, it carries on the idea of describing events or state update requests as plain objects. One of the key insights of Redux is that you can then write additional logic to act on those actions as they progress through a centralized pipeline (ie, middleware).

I've seen lots of Redux-alikes that are "Redux, but without reducers/actions/etc". They mostly claim that they're making things simpler, and in some ways, maybe they do. But, what they're also doing is throwing away the ability to act on those actions as they get dispatched. If I "dispatch a function", I can't programmatically inspect its contents, modify it, log it, attach additional info to it, or all the other myriad of useful things you can do with a plain object.

As for the type strings, you need some kind of useful identifier to distinguish different action objects. You could use Symbols, but those don't serialize well. You could use numbers, but those aren't very meaningful when viewed in an action history log. Ultimately, you want your app's reducer logic, middleware, and the action history itself to be readable and semantically meaningful.