Looks like this has been fixed.
HN user
emilong
Sounds like a great idea. Or maybe make the bar a link to the relevant story.
Looks like the actual article only mentions spiders rather than all arachnids, but I wonder what the total would be if they tallied mites' consumption as well?
Is this the ARES you mean? http://www.aresnorthamerica.com/
Love that they call it the ‘Sisyphus Railroad’.
_.get() is the killer feature of lodash.
Having never heard of Aurelia before, I was curious how this compared to React and found this interview with the creator/lead, Rob Eisenberg, with his thoughts:
https://medium.com/hashnode-insights/rob-eisenberg-on-aureli...
Also includes his comparison to Angular.
Haus | https://haus.com/ | San Francisco, CA | ONSITE | FULL-TIME
We’re a small, well-funded, early stage startup tackling the $50B+ market of residential real estate looking to bring on our third engineer.
Node backend, React + Redux + ES6 + etc frontend. We're looking to hire an experienced full stack engineer who is excited about a collaborative, inclusive environment to produce high-quality code. Learn more about our technical thoughts and approach on our eng blog here: https://engineering.haus.com
https://haus.com/job?id=245327
You can see the requirements in the link above, but here are a few non-requirements:
* Identification with a particular gender, race, or national origin.
* Sharing the same hobbies or beliefs as the other members of the team.
* A certain level of activity on a Github account.
* A minimum reputation level on StackOverflow.
Such an instance is sometimes called, simply, a bar.
Kinda funny that a product that was only officially announced today already has a vernacular. :)
This is a nice, non-trivial, but not too big project in react and redux:
Anyone have a good summary of the language feature changes & APIs (either standards or standards track) that are in the version of V8 that ships with Node 7 vs Node 6?
Is there a security statement about this? I don't immediately see any dangerous operations, but code sharing should always be suspect. If this catches on, it won't be long before someone asks for something that would open vulnerabilities.
All that being said, this is a really interesting approach and having a language for shared, declarative logic is often useful.
Haus | https://haus.com/ | San Francisco, CA | ONSITE | FULL-TIME
We’re a small, well-funded, early stage startup tackling the $50B+ market of residential real estate looking to bring on our third engineer.
Node backend, React + Redux + ES6 + etc frontend. We're looking to hire an experienced full stack engineer who is excited about a collaborative, inclusive environment to produce high-quality code.
https://haus.com/job?id=245327
You can see the requirements in the link above, but here are a few non-requirements:
* Identification with a particular gender, race, or national origin.
* Sharing the same hobbies or beliefs as the other members of the team.
* A certain level of activity on a Github account.
* A minimum reputation level on StackOverflow.
The example given in the readme (API pagination) seems better suited to an observable or stream to me, but it left me curious about applicability to other use cases with Promises.
One is retries on failure or timeout. The other is waiting for something to execute a certain number of times. The latter is something I've used only in tests, but it might have other uses I'm not thinking of. I've implemented both of these in the past with recursion, which is great, but scares some folks, esp when mixed with promises.
Haus | https://haus.com/ | San Francisco, CA | ONSITE | FULL-TIME
We’re a small, well-funded, early stage startup tackling the $50B+ market of residential real estate looking to bring on our third engineer.
Node backend, React + Redux + ES6 + etc frontend. We're looking to hire an experienced full stack engineer who is excited about a collaborative, inclusive environment to produce high-quality code.
https://haus.com/job?id=245327
You can see the requirements in the link above, but here are a few non-requirements:
* Identification with a particular gender, race, or national origin.
* Sharing the same hobbies or beliefs as the other members of the team.
* A certain level of activity on a Github account.
* A minimum reputation level on StackOverflow.
If you haven't run into this on a recent build of Chrome, just try hitting backspace a couple of times and you'll get a toast telling you how to go back. On Mac, that's ⌘+←.
This is lovely!
It does however make me reflect that I would do something like this on my "day off" too. And by "this," I mean I would feel the need to create something, post something, or otherwise turn my relaxation into some kind of output.
Recently I've tried actively not creating and just allowing myself to relax without being conscious of it.
I should note that I'm not presuming anything about the author. Writing may well be their way of relaxing. I just wanted to share a self-realization that I hope may be helpful to others.
Is anyone aware of other, non-automotive applications being discussed? I might have missed it in the article but it seemed like they only alluded to any. Construction? Maybe even aerospace?
TL;DR the tolerance in length of pool lanes doesn't allow for thousandth of a second timing resolution. That is, one swimmer's lane might be shorter within the margin of error that allows them to finish faster by a few thousandths of a second.
This appears to me to the raw sample data https://www.epa.gov/sites/production/files/2015-09/ucmr-3-oc...
The UCMR3_All.txt file inside looks to have a fairly nice, denormalized set of samples with location names, dates, and detections.
Haus | https://haus.com/ | San Francisco, CA | ONSITE | FULL-TIME
We’re a small, well-funded, early stage startup tackling the $50B+ market of residential real estate looking to bring on our third engineer.
Node backend, React + Redux + ES6 + etc frontend. We're looking to hire an experienced full stack engineer who is excited about a collaborative, inclusive environment to produce high-quality code.
https://haus.com/jobs/software-engineer/
You can see the requirements in the link above, but here are a few non-requirements:
* Identification with a particular gender, race, or national origin.
* Sharing the same hobbies or beliefs as the other members of the team.
* A certain level of activity on a Github account.
* A minimum reputation level on StackOverflow.
To be fair, I also have unfavorable reactions when faced with mask-wearing people holding dead crows. ;)
Excellent question! I'm not sure I could do much better, tbh. Maybe something like, "New theory suggests turtles shells used for digging before protection." Not nearly as succinct, to be sure, but less click-baited. The current title certainly got me to click through...
My original comment really was one of curiosity and theophrastus's link to Teleology above hit on exactly the thought process that I was wondering about.
It's always interesting to me when evolution is framed in terms of "why" something happened rather than "this mutation was more suited to the environment at the time." In this case, sounds like shells were good for digging, now are good for protection. I suppose such headlines are well-suited to our current popular understanding of evolution. (Also... I like turtles.)
To what size of aircraft can a motor like this scale? Or perhaps more importantly, motor + batteries? To put it another way, is this technology likely to scale to an aircraft transporting 4 or more people anytime soon?
Just some similar stuff in the asciinema, but I'm thinking that's also just for illustration. Thanks for the clarification!
This is the kind of magic that got me excited about programming in the first place.
I remember being in high school and one day, after class, a friend of mine mentioned that the best programmer we knew had once written a breakout clone with ANSI "graphics." We found him and he said he didn't have the source any more, but we asked him how he did it. He then proceeded to rewrite the whole thing, in Pascal, in about an hour, this time adding animations. Thanks antirez for bringing back that feeling (and, oh yeah, for redis too ;))
PS. the "Low level terminal handling" is gold here.
Just curious how you decide the line between what is handled by ShutIt and what's handled in the shell?
For example, from the example on the home page:
# Ensure git is installed. This handles different distros gracefully.
shutit.install('git')
Awesome and very powerful abstraction! Vs the next lines... # If the directory does not exist, we create it
if not shutit.file_exists('/opt/shutit',directory=True):
shutit.send('mkdir /opt/shutit')
Why not just: shutit.send('mkdir -p /opt/shutit')
There are a few other examples where I was wondering how you decided to do some operations in ShutIt vs delegating to shell. In fact, some entire examples look simpler to me in shell that you could just send. Does using the ShutIt native commands make things more testable?The period of 2004 to the 20-teens will be viewed as the era of... the lean startup.
Does this mean that the success of lean approaches will not extend to next cycle? I.e. that they're only applicable to the current "bits-based" businesses?
Explaining something in a way a toddler can understand sounds a lot like writing code to me. Computers have only as much context as they have libraries/instruction sets and you have to "explain" the rest in those terms.
No idea on the accuracy of this, but this article claims there's a company (http://www.neuvokascorp.com/) making basalt rebar at the same price as steel: http://cleantechnica.com/2014/11/06/neuvokas-basalt-rebar-li...