skysight-inc/HackerNews huggingface dataset:
But I-495 is not signed as such; it is simply called the 'Falmouth Spur' ;)
There was a comment on the original thread linked here about TS 2.1 likely getting support for "partial objects" that will help with both Redux and Immutable Records.
Because there is no user story for "make it performant", and there is little thought put into dynamic design vs static design. If money comes in with crappy performance and it is hard to predict how much more money will come if the developer improved performance, then it won't be a business priority.
And yet social mobility and wealth inequality in the US is among the worst in the developed world.

Weird huh?

And if you really are interested, short afternoon sleeps are positively correlated with lower stress levels and increased personal wellbeing.

Life does not have to be a constant pursuit of ever-higher GDP, which is skewed towards those with large amounts of capital anyway.
Show HN: Primitive Pictures
> I urge people to think deeper up front about performance.

That's part of "making it work." If you're writing backend trading code, then performance is among the first consideration.
Openssl ciphers – SSL cipher display and cipher list tool
>I'm really fascinated by the idea that physics might be completed in my lifetime.

? Unlikely, given the current situation where there isn't much real progress toward unification of QM and gravity..
Easy Solutions Releases Report Calling for New Approach to Cyber Security
My personal approach is to do some order-of-magnitude performance testing as early as possible, to validate that the approach chosen to solve a particular problem is at least tenable.

If you ignore performance completely until late in the project, you can paint yourself into a corner. This includes cases like knowing that performance is 50x slower than will be acceptable throughout development, but saying "we can add X later for an easy performance win". If you don't actually test that X gets you within reach of your performance target at an early stage, you can end up with a fully built system that is unusable.
That may be a valid concern, but isn't that how we learn about all things? Generalize "chairness" from many examples of chairs we've seen? I feel like visualising is really helpful while getting to the point where you actually "feel" the concept of a triangle in your mind. Animation sounds like good way of doing that too.
Why alien abductions are down dramatically
First steps with GitHub Atom
Whats happening in Germany?
Since couple days I am getting messages on AWS that t2 medium and large instance can not be provisioned. Now I just tried to book servers with Hetzner and wanted to ask a short questions but there support is overloaded since hours. On the HostEurope website its saying they got less than 80 dedicated servers of one type left and all others are sold out. Any idea whats happening? Just my subjective feeling something is going on?
Could be, kinda weird he got banned from all of those places, though I'm not familiar with Quora or autoadmit.
I don't see how a better Nuclear plant even touches fusion. Fusion is sort of like the perpetual motion machine, nearly free energy.
One source of panic: turning left now you can be faced with 4 or 6 options of where to go, instead of two. If you just get it wrong, you're going the wrong way on a one-way lane.
GoDoc: package letsencrypt
If the security services target you, and truly wish to kill you, current methods will more than suffice.

The Israelis like magnetic mines, the Russians polonium, the Yanks... Well to be perfectly honest I'm not sure, but it almost certainly involves some combination of clandestine airpower, special forces operations, OCO, and morbid obesity.

Right now, the chain of devices that can track and kill you is enormous, from your router to your standard ICE Jeep. You're most likely already being tracked on traffic camera, the electronic toll system, cellular towers, passing Wifi, and the endless set of embedded Linux devices that you don't even consider.

If you are targeted, there may be many obstacles to your removable from the board, including political, economic, or legal ramifications.

But technical means will not be one of them.
I would add another law: Code organized in small, easy-to-read chunks >> code organized in long, dense chunks.
Less parts, more smarts.

I love this design.
Amazon Says It Puts Customers First. But Its Pricing Algorithm Doesn’t
I've seen this conflict junction in paris before

https://vimeo.com/57972903
If you chase two rabbits you will not catch either one.

Little bit of background here before I begin. I did my comp-sci and mathematics degree and even though they have been useful in some degree or another they both were mostly a complete waste of time in my experience. For the vast majority of the clients and projects that I've had since finishing my university they've all revolved around fixing framework problems or bugs within large code bases. Just today I fixed a massive Land Titling (Enterprise Java/Oracle) bug where the original underlying framework would leak connections/memory until it fell over after 3-4 hours of usage. Other bugs such as off by 1 problems, data translation, data encoding. The vast majority of the time its been incorrectly designed frameworks or replacing frameworks with another framework.

For most of the work out there (I would guess 90% of it) its maintaining and supporting clients to achieve their business goals. Completely un-interesting stuff but get a good reputation of getting stuff done and they don't even wink at your asking price.
Mikel admits he is considering leaving Chelsea
Edit: Misleading charts, figures and conclusions ahead, see @nathancahill's reply

https://npm-stat.com/charts.html?package=babel&package=types...

Babel has faltered since the V6 release, TypeScript is still growing fast, so I'd expect the React world to follow suite, even if Facebook itself pushes Flow...

NPM downloads in August (rounded):

typescript: 2,000,000

babel: 620,000 (down from 890,000 in November 2015)

flow-bin: 120,000
...most people will want to vote for the person who made the most points.

This is true, and baffling. I try to vote as if the process matters, although I'll be the first to admit it's largely a waste of my time. Meanwhile, the morons who loudly declaim the fundamental importance of voting, care only about being "right". SMH.
If your intersection is busy enough to justify some of these rather large and expensive intersection designs (like #5 and #13 from the article) -- then you might as well spend the cash to make it into a real freeway interchange and have zero intersections or stoplights at all.

That will handle even more traffic, be even safer (by their geometric conflict metric), have no stoplights for drivers to deal with, and no one has to learn anything new to navigate it safely.
Call it emotional if you like, but I won't use a language that has an off by one error built into its specfication :-)
At least in the US the base level of wealth (poor) is higher than half the countries on earth. True that the higher levels (the 120 people that own half of America) are way out of balance.
If an engineer is not familiar with the problem space, he should learn more before he writes more code.
The US was kind of like starting a game of Civilization on Chieftain difficulty with industial tech level, with oceans on two sides, natural resources abound, peaceful ally to the north and weaker country to the south.
What are they being replaced with? Even a roundabout with traffic lights regulating traffic entering it seem safer and more efficient than a pure traffic light intersection.
I disagree completely with your 80% number. I haven't worked on a project that had 0 performance work ever.

Performance is a first class design constraint just like development time, budget & functionality, if you don't treat it as such from the beginning you are asking for trouble.
A pure function can't call a non pure function. So you can pass in a non pure function so long as you don't call it.
Interstates don't usually spring out of thin air, they're often existing US Highways or state roads that get relabeled or upgraded to interstate standards and relabeled.
Faster Firefox: Sweet cheat sheet with all the shortcuts
This is a very hard problem to solve. The longer the interval between interventions the bigger the chance that the 'driver' will not be able to intervene in time because they no longer have situational awareness.
Except I also see crud apps that take 8 seconds to load, and you can't just fix it with a cache. EVERY app has performance considerations. Literally every app. Some may be very loose.. but then spell it out, and use that to think about it.
Conclusion: The most powerful force behind the rise of the new giants is technology. But two other forces are pushing in the same direction: globalisation and regulation.

- Premise (support)

- Big companies benefit from supply chain economies of scale/network effects (Pankaj Ghemawat calculates that America’s top 1,000 public companies now derive 40% of their revenue from alliances, compared with just 1% in 1980)

- R&D in countries with cheaper cost of labor/materials (PwC, an accountancy giant, produces an annual survey of the world’s 1,000 most innovative companies. It found that last year those that deployed 60% or more of their R&D spending abroad enjoyed significantly higher operating margins and return on assets, as well as faster growth in operating income, than their more domestically oriented competitors)

- Regulation inevitably imposes a disproportionate burden on smaller companies because compliance has a high fixed cost (Nicole and Mark Crain, of Lafayette College, calculate that the cost per employee of federal regulatory compliance is $10,585 for businesses with 19 or fewer employees but only $7,755 for companies with 500 or more)

- Small companies can't game the tax code like large companies can (The country’s tax code runs to more than 3.4m words. The Dodd-Frank bill was 2,319 pages long. Big organisations can afford to employ experts who can work their way through these mountains of legislation; indeed, Dodd-Frank was quickly dubbed the “Lawyers’ and Consultants’ Full-Employment act”. General Electric has 900 people working in its tax division. In 2010 it paid hardly any tax)

- Large companies have a "buffer" during poor economic periods and can simply buy out smaller companies (the mortality rate for all American listed companies over a five-year period is as high as 36%, but for companies worth more than $1 billion it is only half that)

I was surprised not to see a mention of the evolution of the legal treatment of corporations discussed, as well as a discussion of the decline of unions and the weakening of the average employee's bargaining power. But otherwise a better article than I was expecting from the economist.
That's why backers are anonymous by default!
Publicly accessible API then.
I get an HTTP 404 not found

>The requested URL /fourten was not found on this server. That’s all we know.
The internet comes to mind.
Its a point of view. Partying all night and sleeping half the afternoon is definitely not an indicator for productivity. PC objections aside.
You're probably right. I was literally about to fall asleep for the night and I wanted to make a short comment that might encourage people to read the essay. I hope the cheekiness didn't annoy too many people!
That's really interesting. Is there any way to get ahold of your friend's master's thesis?
Is progressive enhancement still possible nowadays? Considering how many millennials choose JavaScript frameworks for most of their projects I suppose not. It is very rare for me to find a website that works without JavaScript enabled either because the website in itself is written with JavaScript (which by the way doesn't sounds like a good idea, try that with Lynx) or because they are using analytic services as dependencies for the rest of the code.
Ah, right. How is that different from the secure enclave? Less isolated, perhaps?
> My intention was to warn the ones that read this and say, oh i gotta do all of this for every piece of software that I write, which will undoubtedly lead to overly complex code when a simple solution would have worked just as well.

No that is not true at all.

I am writing a crud app to be used by 1 person, some manager of a widget factory. I say "my perf goal is to have page loads in 10 seconds or less". How will that make my code more complex? If anything it will make my code MORE simple, as I can relax all kinds of constraints like "making 72 database queries per page is generally bad".
Because they stopped at step one (make it work) or two (make it right). Or the first of my three (borrowed from Joe Armstrong), make it work, make it beautiful.

It's not simply that they failed to plan for performance, it's that after making it work -they never measured and removed obvious bottlenecks-.

Most pieces of software don't need high performance. Drawing some widgets on screen just isn't that demanding. But it -does- require you to go back afterwards and remove places you introduced inefficiencies. You don't need to code in C and optimize against cache misses for that; you just need to take time after things work to make them not suck, and thats something a lot of software development doesn't take the time to do.
The Two Types of Mastery
People already pay strippers just to talk to them
Traffic lights. Left-turn lanes.
Unless I open the url with chrome.

WELCOME TO THE FUTURE OF THE OPEN INTERNET /s
How to format the pre html tag in Umbraco for code blocks
I've been using Swagger Codegen for the past few months, working on client SDKs in Ruby, Python, Java, and JavaScript.

The biggest thing that impressed me was how active the community was. My pull requests were responded quickly, probably fastest compared to other open source projects I contributed to in the past.
There are roughly two diverging diamonds within ~30 miles that I'm aware of.

Its utterly insane to break the "Right-side driving" rule. I know people who have literally driven on the wrong side of the road through a diverging diamond.

Perhaps it is "theoretically" safer once everyone knows how the hell it works (I mean, yeah, now that I know I need to drive on the LEFT side of the road through a diverging diamond... it makes sense). But jeez, it takes some getting used to.

----------

I worry about tourists and newbies who will also drive on the "right" side, and completely break the diverging diamond. Fortunately, the "better" diverging diamond that I'm aware of is only a 3-way intersection, and there are very tall walls that "blind" you to the fact that you're driving on the left side. It works very well.

The 4-way diverging diamond: where you drive on the wrong side of the road for an extended period is simply insane... at least the first time you go through it.
Its a good middle of an essay.

The first half of the article is a rephrasing of the organizational strategy of focusing hard on things closer to you (in time, priority, physically, financial, whatever) and intentionally fuzzier on things far away but remember to at least glance at everything once in a while. Its that strategy dis-integrated into seemingly unrelated parts without referencing the whole, although I was able to identify the whole. I'm too lazy to look up the dude who originally wrote that, probably wrote it more eloquently than I did; none of this paragraph is my idea.

The second half of the article isn't integrated or I can't recognize what was dis-integrated to make it. The problem of doing whatever's necessary paragraph isn't a purity problem or personal problem or usually everything turns out OK, but is often a code smell problem, which can be counteracted at least partially by the be organized enough paragraph, just comment the code as smelly and list it as needing rewriting in the TODO and hope it runs until it can be perfected. Likewise having deadlines and I can do a lot are dis-integrated. There probably is a theme to the second part that was dis-integrated that I can't identify.

I guess both complaints boil down to it needs a wrapper. An intro like "heres how to break down and concretely apply two wide ranging theoretical and vague organizational strategies (names here) that help me (insert the rest of the intro explaining why its important to do so here)" And a summary/conclusion of the highlights and if you liked this here are some google terms/references etc. Its "why" and "how" are well written and correct, its just missing its "what".

Its the meaty middle of a good essay, although an intro and conclusion (and references) would have been nice additions.
Depends on the project!

Asking stakeholders is good. Often then will have no idea, or say something generic like "make it fast".

Try to pin them to something more concrete.

"So how about adding this new feature makes X happen no more than 5% slower than it currently does"
If I'm remembering correctly it first went live to some early adopters with 1.6.1 and it is using 1.8 now. We obviously want to track the latest releases as fast as we can because they bring new features we're interested in.

I would need to ask some of the teams that tried converting larger projects specifically what they found that they felt was important. I'm certain TS would find some bugs in any sufficiently large project, but I'd have to go dig up data to know roughly how many or how serious they were. Just because there was a technical quality issue with the code doesn't mean that the vanilla JS version of it wasn't producing the actual desired result. It's hard to gather numbers for that type of thing. It's very similar to the let-down a lot of people feel with using static analyzers on mature, battle-tested C++ code for the first time. It will certainly find some nits, but most likely they were not that important to begin with.
Well, it's not without precedent https://www.amazon.com/Tribes-We-Need-You-Lead/dp/1491514736
As a General who above all should know this better than anyone, he's a disgrace...

If watching the pundit shows has taught me anything, it's that there are few classes of public figures more venal, hawkish, shameless, or blatantly self-serving than the military brass. It's a miracle they can convince anyone to follow their orders.
But the best way to learn is often to write some code.
Because this entire Mantra is horrible advice. All 3 need to be in the spec, and all 3 need to be coded for.
WATSI: Get 10x matching
What Every Software Developer Must Know About Unicode and Character Sets
Exactly. Completely ignoring performance considerations until after you got everything working right potentially means a substantial or complete rewrite of much of the code.
That's all well and good, but still "make it work" should always come before "make it fast". For example the code I'm writing right now in my other window is terribly inefficient, quite naive and may very well have to be re-written, but I don't care at the moment. All I care about right now is: Is what I'm trying to do actually practically possible in the general case. If so what approach will give the best/good enough results. And finally, if I manage to do what I'm trying to do, will this particular approach offer a better solution to the higher level problem I'm dealing with than my other approach.

Once I've answered "yes" to all those questions then I can think about heading back and trying to make it fast. Writing really high performance code that doesn't solve the problem you have or give you the results that you need is, of course, a waste of time.
Not a personal finance discussion but tying up large amounts of cash in a depreciating asset is almost always the worst possible use of it.
Memoization works amazingly and can be very easy to implement, but it's not always that applicable.

In my experience, I just don't hit that many pure functions that don't do things like touch the database (which can change out from under the function), or are called enough with the same arguments that memoization is actually worth it.

But when it does work, it's like magic. I do a lot of work in javascript now, and it's great being able to wrap a function in a single line `memoize` function and instantly improve performance.
From a data analysis perspective (which seems like some of her rules are related to), my number one rule that I always try to follow is to: work with the data, not with the tools. It can be really easy to go down the rabbit hole of messing about with the perfect tool for your analysis and end up with no results.

Optimization is important so far as you need it. If I can launch a bunch of aws instances to get a single-run job done in an hour, then I'll throw hardware at the problem instead of worrying about my code. I care about the analysis results, not necessarily how performant my method is.

If I'll need to run the analysis multiple times or I plan to publish it as a tool, then thats another story.
Power Monitoring Equipment
Thanks a lot!

We spend the crowdfunded money on the ex parte reexam PTO fees + lawyer fees (for preparing the filing) + rewarding the prior art searchers. As we're doing an ex parte, it's pretty cheap compared to an inter partes. The IPR one would be >$100k, while ex parte's minimum costs are about $16k. Ex parte has less success probabilities than an inter parte, but the fact that it's so cheap helps scaling the process so we can get rid of stupid patents at a good pace :)
OP here. Although it is very often for me to call out Western-centric viewpoint on English forums, this time I tend to agree with people from Romania or other ex-communist countries :D.

At least for me, it's more like a communist thing with Chinese flavor than a Chinese thing with communism flavor.

Actually it is more complicated than it appears. As you can see, the whole urbanization process of China happens after communist took power. Many rules in the cities are new, and it's hard to say that the rules take places because of Chinese culture or because of communism, usually both.

One thing that is certainly communism-related is that, because of planned economy and a very restricted market, some very basic things were on a shortage and you need "guanxi" for that. My mom recalls that 40 yrs ago ladies wanted to marry butchers (or the one who sells pork), just because they got more power due to the position they were on. You see Radu mentioned that people get extra half bread due to relations. My parents used to need ticket to buy rice and pork etc. That's where you need some "guanxi" to do basic things. Also, to go to hospitals one needs some "guanxi" because medical resources are limited (and price where controlled). Should it be a free market, private hospitals would be built and shortage would fall.

TL;DR: Because communist countries government grab so much power in their hands, "guanxi" plays a more important role than it used to be.

The importance of a relatively free market should never be underestimated. And Chinese people certainly needs a smaller government. Even today, the market is not as free as it could be and the government is still taking too much power (they made a lot of progress with that power though). It's a much bigger government than any democrats would imagine, bigger than a big government in American common sense!
Not before each change but before any major new initiative or refactor. Having those numbers up front is the only way to make appropriate trade offs.

Having this conversation with stakeholders often educates them on the costs of performance as well. Getting 100% of responses sub 200ms is frequently orders of magnitude more expensive than getting 99% of them there, and stakeholders usually get that fast when you show them budget info.
Is it because you have done all the interesting stuff or because you got distracted with something else (or had to stop working on it) and you don't feel like working on it again?