skysight-inc/HackerNews huggingface dataset:
I'm honestly surprised that you're surprised - it's hard to judge what makes the problem difficult if you don't include landing. There's lots of ways to get something to 'jump' (like these toys [1]) that aren't too useful.

This isn't meant to be a criticism of your work, but an explanation of the impression it made in me. If it had been presented as "here's a new approach to jumping with these advantages", I'd have been impressed. Billing it as "the most agile jumping robot ever" while not being able to land it is setting your audience up for disappointment. My touchstone for jumping robots is that Boston Dynamics robot that can jump onto a building, and then I saw yours needing safety nets to jump a meter - you just don't want to set me up for that comparison. On the other hand, your video did get me excited to see where you go in the next few years - I definitely do want to see chain jumps exectued, even in controlled evironments.

[1] https://s-media-cache-ak0.pinimg.com/originals/2e/87/10/2e87...
To expand on this, OpenKeychain wants you to use the camera on your phone to scan a QR code on your friend's phone.
That one looks good. Thank you!
I find this attitude on code reviews to be extremely demotivating, especially on code bases where I am not the primary committer or lack overall responsibility for the system being changed. It completely distracts from the code under review, and it only requires a small amount of social/organisational ill health to be abused.

Even if you believe that the next committer should clean up, it can require quite a big context switch - either the clean up explodes into quite a big task and you have to question the trade-offs being made in doing it now, or it doesn't have full focus and becomes risky and/or no real improvement.

I don't happen to believe that the next committer should clean up in most of these situations. Minor things, sure, you should do it (but don't side-track the review with it!). In my experience, people who already couldn't be bothered to do it or clean up later use a new commit as an excuse to get their work done for them. I've often seen people criticising tangential code issues in review who were responsible for the original commit. The question becomes - if it's such a minor issue for me to clean up, why wasn't it a minor issue for you to clean up? If it's bigger, how did it pass review in the first place?

My view is that extraneous cleanup should be proportional to the original change at most - and not discussed in code review of unrelated changes. If a particular area of the code sees sufficient churn to accumulate more and more debt, everybody will know and talk about it, it will be clear that some specific refactoring is necessary, and more importantly it will be evidence that small cleanup is worthless (high churn) and a better architecture is valuable (high churn). A given team may have high tolerance for technical debt and thus never do this work. But then they are screwed anyway, why create noise at every review just hoping that someone else solves it?

Remember, there's also a good chance that the mess stays the same as it always was, sitting there passively. And there's a chance that the cleanup introduces unanticipated problems, especially if it's legacy code with no/less testing.
HackMyResume does Word, PDF, ....

http://please.hackmyresume.com/

But it is a Node app.
>>I have to say I'm really disappointed and this is a huge blow to people that invest in startups offering hardware.

Buyers need to start demanding Open Source Software and Open Hardware...

With out that, you will always be screwed
Well if you're not providing a service to others, then you shouldn't be the ones to look into it. But if you're providing a service to users and they tell you it's down then you should. It might be that your ISP has a misconfigured route that is flapping and sometimes causes errors in some locations. Or a netmask is wrong somewhere and certain ip address can't be accessed. It might not be a temporary thing. And you if it's your ISP fault they might be able to fix it.

You've seem to think that you have to investigate the issues. On the contrary, you bump it up to your isp to investigate. If your ISP is regularly having these issues then it might be time to change ISPs to one with a better peering agreement.
I used to be the kind of guy who started a lot of things, but never finished them. I got angry at myself, and built a project with the sole goal of finishing it. The challenge of “just get it done” really put me in the right mindset. Since then I’ve started finishing what I started. Here’s some tips.

If you’re going to try a new to you tech, only use 1 new to you thing at a time. There is nothing wrong with using a technology that’s old. In fact, that’s the best way to finish something. Old technology is googleable, stable, and usually has libraries for everything you want to do. New tech might let you do in 3 lines what old tech will do in 20… but getting those 3 lines of code to work might take more time than just writing the extra code. The next point, elegance does not matter. NO ONE cares about your project. They aren’t going to review the code, so why spend time doing something elegantly? Just get it done.

As mentioned in the article, you really have to realize your limits. At work, when you have a large team, the definition of MVP can expand. When it’s just you, you REALLY need to think about what value you’re building. I’m constantly asking myself “is this thing I’m going to spend today on actually going to be the difference between my product being useful and not working at all”. “Is there a way I can get away with faking, or doing this thing manually”. If you only have a few users, you might not need to automate right away.

One more personal preference, I don’t talk about what I’m working on with friends and family until I’m near done or done. For a few reasons, first if you talk to other engineers, they’ll discourage you. When you propose an idea to another engineer, they’re shoot it down pointing out minor flaws. I used to think, oh that’s useful… they’re preventing me from going in the wrong direction. Upon reflection though, I’m not sure the advice I’ve gotten has always been “useful”, it has made me give up on ideas. Maybe I’m weak willed, but this is what I need to see my ideas get done. If you really believe what you’re building will work, the only person worth talking to are your future customers, if your future customer isn’t interested… that’s actually worth something.
http://archive.is/i2uno - If you received "The website encountered an unexpected error. Please try again later." instead of the article here's a mirror that can be viewed without running javascript from brightcove and newrelic tracking domains.
Only trademark. Copyrights aren't lost by not defending them (this is a very common misconception for some reason).
It was a long wait, without the benefit of a cryo-chamber, but worth it. Vindication is far and away the best of the series for me. I suppose it'll be another year or so before the next is out.
No... it definitely has not.
PostGraphQL: PostgreSQL meets GraphQL
For those curious, you can still buy the Pebble 2 online via BestBuy, Walmart, Amazon, etc.

Did the Pebble Time 2 ever get completed? Did anyone receive one? I was really looking forward to it...
It's business 101 that the retail price should cover all production costs, including R&D, otherwise you are in shortfall from day 0.
I've had my Pebble Time (1) for about 18 months now, sad to hear this.

No other smartwatch can boast 4-5 day battery life.
I'm actually surprised that Google hasn't been more involved in micro-grid technology. One company here in town basically runs on its own grid with a combination of renewable energies and electricity they generate on their own:

http://www.oati.com/about/microgrid-technology-center

The main difference between the OATI Microgrid Technology Center and other commercial office buildings is that OATI will generate its own electricity as the primary source of power. The building is powered by:

- Natural Gas turbines: 600kW Capstone C600 natural gas burning microturbine. Paired with absorption chiller and heat exchanger for CCHP

- Solar: 150kw rooftop solar array, with additional expansion array planned

- Wind: 24kW of vertical axis wind turbines

- Electricity storage: 231kWh, at 125kW Ensync battery rated power and energy

- Generator: 1500kW of diesel backup generator

- Utility connection: Connected to local utility Xcel Energy
"page businesses"?
I note this from Pebble's developer blog, suggesting that a Fitbit-targeting successor to Pebble's app SDK may be a big part of the plan:

"Although this chapter in Pebble’s developer story is closing, our team and ethos have found a new, welcoming home at Fitbit. We can’t wait to have you alongside us for this next adventure. Third-party Pebble developers have a massive opportunity to drive how a Fitbit developer ecosystem will take shape. We hope you’re as excited about seizing this opportunity as we are.

Over the coming months we will be working closely with our new friends at Fitbit, building the foundation for the next great wearable experiences. We want you—our fantastic developer community—to keep playing a crucial role in our success. More information will follow soon, so stay tuned!"

https://developer.pebble.com/blog/2016/12/06/developer-commu...
Minor nit - the iPhone 7 doesn't have a physical "home button" - it's a force-sensitive area with haptic feedback.
Its really sad to see Pebble going under. I really feel for the founders and employees. Unlike other commenters here I dont think there is obvious way this could have been avoided. Certain markets/companies do require a specific scale of investments/growth/market-penetration to be sustainable. Wearables/Smart-watches have proven to be a very difficult market and I pepole behind Pebble should be commended for risk taking.
I would love to see a full-federated email-like (as opposed to chat-like) system built on top of Matrix.
Love my Pebble. Has almost everything I wanted in a watch. Found it a pity that on the marketing front, Pebble never seemed to get top of mind (or anything near there). My current's watch's display is starting to shred. Debating buying a second watch while they are still available. Downloaded the SDK and will grab the tutorials. Hopefully Fitbit will keep this information around.
Lecun has identified a real problem for AI -- the need to understand the real world, the link between intelligence and prediction over time. But the tools he is using are not the right ones.

Deep conv nets were not designed with prediction over time in mind. Here's one reason: Deep convolutional nets do not handle dynamical information from their lowest layers. By design, conv layers and pooling layers immediately begin discarding spatial information that could be used for building up predictions.

In contrast it is possible to start with recurrent/feedback networks at the very first layers of the network. These initial layers can begin building up predictions at the pixel, color, and lighting level (example: our recent preprint[1]).

My colleague, who as some of you know enjoys blogging, wrote a more thorough post in response to LeCun's recent CMU lecture on the same topic as these slides[2].

[1] https://arxiv.org/abs/1607.06854

[2] Blog: "A few comments on the Yann LeCun lecture at CMU, 11.2016" http://blog.piekniewski.info/2016/11/21/yann-lecun-cmu-11-20...
> They could've said "reach out to Fitbit instead".

Which would be even more of a dick move because Fitbit will tell you to go pound sand because they aren't responsible.
Sad to see the failure of a truly alternative product.
Hiring a diverse development team: A practical guide
Citizen buying pebble would have been so incredibly awesome. This is about the worst possible ending imaginable for pebble. Sad day.
The NSA Can See Everything You’re Doing with Your Phone on a Plane
I'm really surprised at this comment - I can't recall the last time I had my CV in Word format. At least over 5 or so years ago. And even then, I think it was voluntarily on my part: I don't think anyone's ever requested Word format from me.

Have you carried out any research/surveys for Resume Fodder to find out what percentage of people are encountering this?

Edit: I'm in Ireland, so maybe this is a US thing, but I've always thought we were a bit behind here in terms of trends of software usage.
Yup. I actually bought the Pulse which was their forgotten pre-Pebble failure.

It arrived as a useless brick that I, and most other recipients, never even got to show the time.
Despite the fact the article suggests it's not the probably cause, this does make me abstractly wonder if there could be some sort of virtue in firing a clay house. In modern times we'd probably go with concrete if we were going to go that route, but ceramic is more available back then. Then again, getting good kiln temperatures from a neolithic fire could be a challenge. Although depending on how you constructed your clay house it might just be possible to fire it with a fire from the inside and retain enough heat to fire the house. Though possibly you're designing a house from the get-go that won't have adequate airflow.

Anyone familiar enough with ceramics to comment on it? (Bearing in mind I do fully expect this to be impractical on the grounds that nobody seems to do it. I'm more interested in the process of intellectually kicking the idea around than the probably-trivially-easy act of shooting it down.)
>Making battery life a priority in a world of WiFi-enabled pressure cookers.

I literally wear my Time Steel for 23 hours and 45 minutes per day. The only time it's charging and not on my wrist is when I'm in the shower, and over the course of a regular day it never drops below 80%. If I'm going away for a weekend I don't even have to bother with the charger.
No, Pebble is bankrupt and winding down operations. FitBit is buying some parts and offering jobs to the software people. This is not an acquihire. The designers and hardware people are not joining FitBit. The owners get nothing. Some of Pebble's creditors will likely also get nothing since the software/IP sale doesn't cover Pebble's debts.
I agree entirely. It's very rare that something fits a niche so nicely, while the competition misses it by miles.
I have the same feeling about my simple sigma bike computer (though at least there's more options in that niche).

I will use my pebble as long as it continues to work, then it'll get retired to my shelf of tech fails. Most of which failed FAR more spectacularly.
I also think that writing idiomatic code is important. I have seen a few Python apps written in a Java style. It negates many of the benefits of using Python.
Well, I heard part of it is more a company issue with John Carmack (who supported the game's spiritual successor on Twitter) than a business one. After all, the same ZeniMax also supported Brutal Doom (a Doom mod) for the Game Awards and was fine with numerous other Doom fan projects. And this game itself has been going fine for about 10 years.

They'll say it's an IP ownership thing, but a lot of people are more convinced it's a personal grudge thing.
Resume generators are getting a little trope-ish. Personally, I just use jsonresume's schema more or less to keep all my employment information. I don't like their generators, too heavy and esoteric, personally. I just use the JSON file.

My website is generated with a static website builder, hugo, and uses wkhtml to generate an optional pdf. It just pulls a subset of what I want to display from the exhaustive, version controlled json file. My entire website pulls contact information, name, location, social media profiles etc information from that one json file. It separates content and presentation and I keep it all in one file. If I wanted two versions of the information, I just change the html document and what I pull.
You're correct, I was distracted by some posts in this chain that seemed to be talking about using the key for encryption, not identification.

So the primary threat would be impersonation by the trusted party, which would erode the trust pretty quickly. I'm still a bit wary of this approach - do you think we'd manage to keep the keys from also being used for message encryption?

Where I live, there's actually a system somewhat like this in place - banks etc. can provide identity verification to websites upon request. You log in to the bank's system with your account and one-time pad they provide, and the bank tells you what information it will pass on to the requester. It seems pretty decent, and might actually be better than the USB key approach.
It's a shame that it took a threat of a lawsuit for it to be released as open source. This wasn't a game that was ever charged for, so I see no reason it shouldn't have been released like this 15 years ago. There's actually a weird culture in roguelikes (and similar ASCII games) of not releasing the source, and using opaque, non-open development processes. NetHack was open source but only recently switched to an open development process recently, and may other popular entrants in the genre such as ADOM and Dwarf Fortress are closed source entirely.
And of that $40 million, they still owe their creditors something like $27 million. So for investors/founders, they're all looking at <1/4 of their investment cash value.
Good comparison. I'd be interested in a comparison with Rancher, too. Looks promising to me.
Think more about the machine/platform not "think more" in absolute terms.
Wrong strategy, they will OCR any doc type you send them, even paper.

Better to just have an explicit conversation with the recruiter agreeing to your ethical/personal boundaries. Based on their response you'll probably get a good clue whether or not they respect that.

There are ethical recruiters but as with any group of people you have to sort out the good ones.
I have a first gen Apple Watch after having the Pebble Steel and I was very much considering going back to Pebble, this is very sad news.
> Keep Salaries Secret

This is something that's actually an offense that can get you fired at my company. Their justification is "to reduce gossip".
I believe it stands for Byte Subtraction Diff, or something like that. As I remember, something like Bentley McIlroy diff is used to identify identical runs, and where there are short runs of bytes separating two runs that are identical between the two files, the bytewise subtraction of the short run is stored.

The key observation is that when performing updates, large runs of machine code will be identical, with only relative offsets and absolute addresses changing. Code changes tend to shift huge pieces of binary code in parallel (by the same offset), so the bytewise subtraction expresses these shifts as many repeats of the same bytewise difference, which is then more easily compressed by zlib DEFLATE (or maybe another compressor... I forget the details).
Hmm, the documentation seems to be updated to show 3.6 in the dropdown but it's not on the release page yet.
You know, Pebble has garnered one of the best group of loyal customers I know of: well-off techies.

Had they came to the community and said, "hey we are losing sales and we need everyone to pitch in $10 / year for software support (maybe a web interface for fitness or something) I guarantee a few hundred thousand people would have done it.

Had they shared a coupon with the community (i.e. email add campaign, or add on watch - "buy one, get one half off" for christmas they would have probably had a large bump in orders. Although I recognize this would be a mild annoyance, I can also guarantee they would have sold plenty of units.

This simply seems like poor management and it's frustrating because it's the best smart watch I can find at the moment. It does exactly what I want, is cheaper than the competition, and is dead simple to use.

WTF pebble, you had the product people loved - you just didn't market it well.
NewTrackon: Tracking the Trackers
Personally I think it's a fad and not long for this world.
We don't do that here.
inherited a grails codebase from a team who mostly hated groovy/java, and tried to recreate rails/ruby in almost all the code. all external supporting libraries and tools were ruby, and it had more than a few "groovy sucks because it's not ruby" comments scattered around. Apparently just the top CTO guy there liked grails, started the project, brought on people, but they all hated it. and built a massive monstrosity that was neither idiomatic ruby, groovy or java. :/
Totally this. I'd gladly pay double for Time 2 if it meant the platform will grow sustainably.

> Sometimes I think there is a secret cabal conspiring so we can't have nice things ;-). The same one that decided that cell phone batteries have to be non-removable, touchscreens glossy, and wearables either mini-smartphones or bluetooth-step-counters.

I feel that all the time. Of course it's not a secret cabal, just the free market promoting get-rich-quick schemes and making it harder for sustainable businesses and actually useful products to survive.
Run the command `traceroute bad.horse` or Windows `tracert bad.horse`
You can't innocently be part of someone else's bad actions. Amazon is doing bad things to the market and wantonly destroying lives.

It's their choice to align with an entity seeking monopoly control of a market, and using their status to arbitrarily ruin lives.

These people are materially supporting that entity, so they're fair game for fallout from retaliation.
No, I was asking what I typed. It wasn't a cleverly veiled challenge to derive what I could have meant from first principles.
(for Mac)
You can see it in action and send a message here: http://lights.seb.ly/
Fitbit only bought Pebble's software assets and brought over just under half their people.
Yah I agree. K8s install has been the bane of the projects existence.
I'm devastated. I remember being so excited when the first kickstarter happened, but I was broke and couldn't buy one. Then finally after years of waiting and following them with interest, my wife bought me a Pebble Time for our anniversary. That was 2 months ago and now the future of this amazing device on my arm is completely up in the air. And what is the alternative? Some over-priced, under-featured piece of garbage fitbit? No thanks.
These people either work with very large codebases or have enough experience to understand that the average developer is careless enough to risk safety just for a little bit of convenience.

I'm personally keen on using % on vi or clicking on the braces for selecting scope in Eclipse and ACME. I also find them aesthetically appealing much like Lisp parenthesis.
Apple secretly acquired a Finnish company to help it map indoor spaces
Help Build the Open Guide to Startup Fundraising
It's not about how far, but how fast it is going. The bandwidth of that wagon is about how fast those tapes pass a given point of travel. How they are arranged inside the vehicle is critical. Tapes moving at 100 km/h side by side have more instantaneous or "burst" bandwidth than tapes moving at 100 km/h in a single file.
I wonder in 3,000 years (after a loss of many records) if they'll be debating a "Burned Man Theory", and trying to figure out why some weirdos kept setting up and burning a man every year in the middle of nowhere.
Where is the world's most 'godless' city?
My Pebble Time is brilliant... after an LG G, Moto 360, I settled on my Time being a perfect balance if functionality and usability. I was one of the first Time 2 backers and this really sucks to put it mildly. The Time 2 was going to fix my VERY few issues with the Time. In general they struck the perfect balance in a wearable for me and I was really excited about the future (Time 2, Google Assistant integration, etc). I rarely get truly sad about hardware announcements but this one is really disappointing.
I'm not sure if this even makes sense here.
I know how heartbreaking that must be for the founders, but at least they're going out the classy way. I'm sure we'll hear from them again.