skysight-inc/HackerNews huggingface dataset:
I'm possibly a bit of a dinosaur in my thinking, but of the three "2000s" areas outlined -- social, mobile, cloud. Cloud will have the longer legs (it is basically open, scalable timesharing). Mobile is broad and has a lot of avenues, but social really seems to basically fall back to "advertising". All three of these areas are dominated by software.

70s (well more 80s) to 2000ish, the valley was a healthy mix of software and hardware. HN seems to focus mostly on the software aspect of recent times, there are still hardware companies out there. The peaks that get attention, popular investment, and trigger the large growth help the valley, but a balance of disciplines, technologies, and platforms (hardware/software), really do help the valley.

An area trying to be "the next silicon valley" that ignores the unsexy things happening in low industrial areas in Fremont or Alamaden Valley aren't ever going to be the same. Yes, we are known for the wild successes, but there are a lot of little no names that have helped companies big and small (that became big) here along the way.
Deciphering bad bug reports is absolutely a waste of your time as a developer, but that doesn't imply that the user is mistaken. In nearly all cases, the user is correct in sensing a bug but incorrect or inarticulate in their description of it.

It's almost always a good idea to understand what's behind the report. It's just that somebody in a different role should be doing most of that work.
The Unity-oriented stuff are good examples. The Stack Exchange sites came to my mind as well, though I was hesitant to count web apps.
First off, this is awesome.

With enough focus and effort you could really turn this into a stellar product that I would use daily.

I manage my most of development through GitHub. Unfortunately, the processes around getting user input and bug reports, communicating changes and updates back, etc. all suck. Usually, you have to marry a thousand-and-one services together and thereby die by a thousand cuts, or setup some customized process (manual, with automation eventually).

Having that all tie in/around GitHub would be such a time saver, and would reduce a lot of duplication of effort.

---

For example, I want to:

1. Setup a milestone.

2. Create issues for features, bug fixes, and re-factoring that needs to happen.

3. Communicate this to users.

4. Tie in user feedback.

5. Develop the product, providing releases on some schedule.

5. Rinse and repeat until the milestone is reached.

6. Release. That means tagging, running CI to generate for all target platforms (native, woo!), and getting a Github release put together.

7. Communicating and delivering that to end users.

---

I can achieve this with a hodgepodge solution, as I mentioned before, but one service would be killer.
Fixing 5 requires the elimination of districts and restructuring across a popular vote.

At the scale of the US Federal government, this would require some form of automation to help inform voters of which candidates are on their short list (given preferences they've expressed). Ideally this calculation could be performed on computing hardware that the end user owns and trusts (be that a cell phone, or a RISC-V system with a fully open stack from layout through firmware to OS; this BTW is the only type of hardware that I would consider to be audit-able for inclusion in an assisted /paper trail/ (for recounts and etc) instant tally at close voting system.)
Outgrowing Postgres and Migrating to DynamoDB
The Story of the Greatest Shopping Technology That Never Was (2011)
I'm also excited to see Jafar Husain's Falcor:

https://www.youtube.com/watch?v=hOE6nVVr14c

It's a different implementation of the same concept.
and how is HTTPS protecting us against that? if you took over that IP address you can initiate a valid HTTPS session using the compromised server's identity and communicate with the monitoring service happily reporting fake data over HTTPS. I don't see your point. The question here is btw. is it worth X amount of dollar to protect this service with a secure channel? Sometimes the answer is yes, sometimes it is no.
I think if I split the cleaner node into two nodes, the standard solution has to change (not sure if there is one or not). It prevents the qubit needed to encode the information for the receiver from being in the same place as the qubit needed to decode the information from the sender, so no re-encoding.

┌───────┐
| |
| A ==> S
| || |
| || |
| vv v
| B ──> C
| |^╲ |
| | ╲╲ |
| | ╲╲ |
| v ╲vv
└>D────>R

Spot any solutions?
VMware - Palo Alto, CA - Full-time Data Architect for Product Analytics

We are looking for a Chief Data Architect to lead the architecture and design of our Data Analytics Infrastructure.

If you have experience building end-to-end back-end data infrastructure (ingestion, modeling, processing) that uses scale-out architectures to deal with large amounts of data and numerous access patterns, we would love to have you in our team!

You will design v1.0 data infrastructure for product usage analytics with the most appropriate technologies to suit existing and to-be-discovered customer use-cases. Knowledge of Hadoop and Hadoop-related projects, NoSQL and MPP databases is very important, and so is a passion for building great software systems.

http://vmware.jobs/palo-alto-ca/chief-software-data-architec...
Well, you can set the expiration period for the reflog. If I remember correctly you can set it to "never". You can also disable alteration and removal of branches on a remote git repo. It's really all about knowing your tools.

Then again, in my experience, if you manage to remove data or alter data which should not be removed or altered, and don't pick up on that before after the reflog expiration period, then you have bigger problems.
MS Office 2016 Pro Plus ISO Beta Version Activator Download
I really doubt that's true, just because it's too early for it. There are approximately zero used Tesla batteries available right now. The fleet is just too new. Maybe in another ten years.
Top Startups to Watch Out For
I've always found that switching jobs is easier than getting a proper pay rise.

I have found that to be the case as well. Using a combination of skillful salary negotiation, leveraging counteroffers (use sparingly), and hopping between companies, I have averaged 19.5% yearly salary increases for the past 10 years. Obviously this is not sustainable, since my current salary level limits the number of positions I can take without taking a pay cut.

For those who are curious, it took 6 companies over those 10 years, with 1 career change from teacher/manager to programmer. During that time, the largest year to year jump was 38% (2nd was 37%), the longest time spent at a company was 3 years, the shortest was 3 months. I used the counteroffer trick twice, once quitting and once staying.
I think you are better concentrating on natural prebiotics, by eating lots of fruit and vegetables. Apples in particular are meant to have very good prebiotic properties.
Company: Postmates

Location: San Francisco

Visa: offer visa transfers and green card sponsorships

Roles: Software Engineers (backend, front-end, Android, iOS, data, generalist)

Job Descriptions: check out our website at https://postmates.com/jobs

About the company:
Founded in 2011 and located in San Francisco right next to Caltrain, Postmates is transforming the way local goods move around a city by enabling anyone to get any product delivered in under one hour. Our revolutionary urban logistics and on-demand delivery platform connects customers with local couriers, who purchase and deliver goods from any restaurant or store in a city. With the largest on-demand delivery fleet in the country, we currently operate in 22 cities across the country and continue to expand each month. We are well-funded by Spark Capital, Founders Fund, and Matrix Partners (full list below), and our Series B was raised earlier this year. We also just announced major partnerships with Starbucks and Chipotle.
URLs submission on popular social media sites
Clang has, for some time now, supported the MSVC ABI.

Here is their implementation of name mangling: http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/AST/Micros...

Here is their implementation of record layout: http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/AST/Record...

Here is their implementation of vtable generation: http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/AST/VTable...

Here is their implementation of RTTI: http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/CodeGen/Mi...

Here is their implementation of C++ throw metadata: http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/CodeGen/Mi...
What is your complaint about? They have a feature available but costs money which you just don't want to pay?

Counting on them to just "be nice" and do it for you anyway isn't really a valid option, nor something to base your objection on. If you don't like the service and aren't happy with the price then move on to someone else.
Were they in violation of GPL with anything? I can't find credible reference.

I know that they identified the USB/DVD tool and re-released it under GPL.

http://www.zdnet.com/article/microsoft-admits-its-gpl-violat...
This is what happened in my last negotiation, where $X was a 30%-ish raise. They didn't bat an eye, and made an offer of exactly $X. I asked them, "Could we make that $(X + .06*X) and they did.

Negotiate.
Unless done badly, it does.

Transpiling to C gives you the opportunity to emit code that is straightforward clean and fast C for most operations, which avoid an abstraction overhead.
In the original post Patrick already touched on the Japan case, but one thing I'd add is that one of the pieces of paperwork you must hand to your new employer is your final tax slip from your previous employer showing how much tax you have paid in the current year. From there it's trivial to calculate your previous salary.

There are ways around it but it seems most people go with "my base was XX.... and that's one of the reasons I'm out there looking to change jobs."
...this move would de-emphasize the importance the skill of negotiation, which would be a detriment to the company.

And it would benefit the employees of the company, who are disadvantaged because they only negotiate salary every now and then vs the hiring manager who does it all of the time, and who also has insider information on what the company is willing to pay and what everyone else in the same position is earning.

For an employee, knowing that your company, and probably your manager, reduced your income simply because they could is not very good for morale and loyalty to the company.

...some arbitrarily made rubric...years worked, which is a terrible standard

Totally agree with you there. Structured pay tables have to be based on more meaningful metrics than seniority and job title. I got glass-ceiling by that for a long time because I didn't want to switch from development to management, and my company (CTO and his toadies) didn't want to let me join the Architects group.

...engineers and business development people devalue each others work...Each side can find a justification on why they are being under-compensated while the other over-compensated.

That's true, but the business development people tend to be more highly compensated, work fewer hours and more regular schedules, and have much more political power within the organization. It'd be better if there were objective metrics for measuring everyone's value that both sides could understand, so they don't devalue each other. Everyone doesn't have to get paid equally in order for everyone to get paid fairly, and if a startup can cultivate a culture where everyone feels they're being treated fairly, they're going to be a great place to work.

Interviews reward people who can handle stress and negotiate.

Also people who are good at "faking it until they make it" and other techniques that work well for interviewing but not so much for doing the job. I don't think taking the salary negotiation out of the interview would reduce the stress level much, or the interviewers ability to judge how the interviewee handles stress.

You're going to want a leader on the engineering team to negotiate with the strategy makers to find an equitable solution.

No, you want a leader on the engineering team and a leader with the strategy makers to collaborate on finding the best solution for the company's needs. There should be no negotiation involved at all. This is mathematical constraint-solving, not deal-making.
But that's not how this works. By saying that he can't disclose, he's disclosing the existence of the program. It's entirely possible that the program's existence was classified. The NSA's existence was classified for many years and I believe the "Groom Lake Facility" (aka Area 51) might still be. Everyone knows it exists, but the government won't admit it.

He can't address it beforehand if the admission of its existence is classified. By addressing it beforehand and saying "you can't ask me this question" he indicates its existence.
Co-founder and CTO of HelloSign here.

Sorry to hear that OP's bug reports weren't taken seriously. Good tech support is a must for mission critical APIs.

At HelloSign we take great pride in our API and our tech support. Rather than outsource support or rely on less technical people, we have our developers directly support the API they built. So when you give our API a try, I encourage you to check in with one of our developers by visiting our public HipChat room (https://www.hipchat.com/gq4BMFKt1) or emailing them directly at apisupport@hellosign.com. And that's available to all customers no matter what pricing tier they’re on (including free).

Take a look at our API documentation here: https://www.hellosign.com/api/documentation

We’ve had a lot of API customers switch over to us from EchoSign’s API due to reliability issues. I have a lot of respect for EchoSign and their original CEO Jason Lemkin, but I do think the API was an afterthought for them. At HelloSign we think it’s the future and are committed to having the best-in-class API.

I also wanted to touch on your point about wanting to work with "a company with a soul". This is something I also look at when making buying decisions. I’ve found a company's Glassdoor reviews to be an effective barometer of how well a company treats its employees and, by extension, how its employees treat the customers. That’s one (imperfect) way to measure "soul".

Happy to answer any questions anyone on HN might have.
>Despite this coming from a large group of scientists with top-notch credentials, that was immediately doubted by almost the entire physics community

You make it sound like the scientists reporting it didn't doubt it.
I've been trying to solve this problem since 1975. I just glanced at the linked page, yes it is indeed the same problem, but I don't want to know the answer, I want to solve it myself.

I'm pretty sure I know how it's done now, but I haven't had the headspace to deal with it yet.
Yes, but a rebase re-applies every commit to the new base. So you solve conflicts one commit at a time, instead of solving every conflict in a single merge commit.

It's easier to remember the intended behaviour when the code changes are as small as possible, and when you have a (hopefully) good commit message to look at.
Macbook Pro for me. It sits on my desk in clamshell mode with two external monitors and a mechanical keyboard plugged into it, running a couple VM's, my docker container cluster, my editors, and browser tabs, my music and Slack, and never a noticeable slow down. I rarely even hear the fan. When I want to go portable I can disconnect and go for many hours with no worry about battery.

Honestly I think most modern laptops are more than powerful enough for development work. The only thing that matters to me is keyboard, because unless you are buying a cheap budget laptop it will have more than enough power for whatever you want. And when it comes to keyboard I just use an external keyboard anyway so whatever it is plugged into is fine for me.

The only reason I absolutely must have a Mac is for running X Code and building ios apps, because I'm not going to be running a hackintosh for that.
FYI - I enjoyed a podcast recently on GraphQL/Relay -
http://devchat.tv/js-jabber/152-jsj-graphql-and-relay-with-n...
FTA:

> ... the solution is to reinvent Adobe: to change the system from within. If Customer Success could talk directly to Product Engineering, then the bugs would get fixed, and the volume of complaints would go down, making everyone’s lives easier.

That process is enormously beneficial. I run an open source project, and spend a good chunk of my day answering low-level tech support questions. These are often "where is the ANY key". But a high percentage of them are people with real issues. I listen, fix the issues, and give feedback.

The result is enormous customer satisfaction. They get responses (and fixes) in 15 minutes. Their previous commercial solution would be 6 months, if they were lucky.

Shortening the feedback loop is a well-known engineering principle. But apparently not known enough in software companies. For systems with negative feedback, low latency is very positive.

More companies should have engineers deal with customer issues.
Ginsberg's Theorem (Thermodynamics Parody)
"the official or advertised price of a hotel room, on which a discount is usually negotiable."
Sadly true. That's why I'm not using Firefox on android despite using it on the desktop. They never got the right algorithm for font inflation (that's how they call it).

HN displays ok in Opera Android but mostly because Opera can reflow text on zoom. That fixes almost everything.
If you're asking from a personal standpoint: I would imagine that you'd want to reduce your debt, cut your expenses and increase your personal liquidity.
Thank you! I fond the sneak peeks of number theory, algebra, probability, combinatorics and graph theory I've had so far to be quite enjoyable. But keep in mind my run with geometry hasn't gone past Euclid (the illustrated version of the Elements edited by Taschen) and I'm still in the dark about other fields (I'm using Professor Gowers' The Princeton Companion to Mathematics for direction).
I learned my lesson about this once. I accepted an offer at a company who wanted 10 years of my salary history.

10 years.

So I provided it to them, and one of the companies (who was out of business) could not verify my salary (Pay stubs were not enough, they had to talk to someone).

After this they said they may have "adjust the offer accordingly" and it would most certainly be less because the offer was based on my stated salary at the time.

As most of you are probably guessing, I declined their offer and withdrew myself. Ever since then when they ask my current salary, I don't give it to them.
The way I see it there are two sides to the hype coin: frothing believers and curmudgeonly skeptics. Both are simple minded and shallow. Both really come out of the woodwork for stuff like this.

BTW the reason SpaceX is more exciting than SLS is VTVL reusability.
What books can I read to, at the very least, attempt address the questions in your 3rd paragraph, given how unique every business is? Isn't anything you find a book on sales or marketing so abstract that it's 2 or 3 layers of assumptions before you can talk about projections? How does one begin a career in SaaS sales / marketing? What makes for a good "portfolio piece" in that domain?
for the longest time i was kind of unnerved by how quickly previous employers said yes during negotiation, so I pushed my price up much higher hoping to have a better footing.

so far they've all said yes to what I considered very high.
I was really hoping to see more support for OS X API's, personally I'm a lot more interested in porting my Mac desktop app to Windows desktop than any iOS project.
Location: San Francisco
Remote: possibly
Willing to relocate: yes
Technologies: HTML/CSS, JavaScript, Ember.js, Meteor.js, MongoDB, Node, Git, Photoshop, Illustrator, UX
Résumé/CV: http://pickettg.me
Email: gpickett00@gmail.com

Working doing front-end freelance work in SF at the moment, looking for either more freelance work or something full-time. Looking to work primarily doing front-end work with JavaScript. Willing to learn any programming language or framework and relocate
Microsoft HoloLens and the danger of mismanaged expectations
This is a perfect example of why the open source programming model (licensing concerns aside) is superior to closed source when it comes to any mission critical program. You cannot let your entire business rely on a single company's buggy software.
SEEKING WORK
Location: Cracow, Poland;
Remote: yes
Willing to Relocate: no

iOS Developer with 5 years experience; also PhD student researching optimization techniques. Technologies: iOS, Android basics, Java, C++, Julia, Python, JavaScript, Lua, Prolog, Couchbase Lite, parse.com.

Email: mateusz.slazynski@gmail.com
www: home.agh.edu.pl/~mslaz
CV on linkedin: https://www.linkedin.com/pub/mateusz-%C5%9Bla%C5%BCy%C5%84sk...
The headline doesn't do the problem justice. This is a big deal. Here's a snippet:

"after 248 days of continuous power, all four
(generator control units) will go into failsafe
mode at the same time, resulting in a loss of
all AC electrical power regardless of flight phase."

The current workaround is to totally shutdown and restart.
Ask HN: E*trade account for non-us citizen
I'm going to develop a trading application for Etrade, but I live in Russia, so Etrade doesn't allow to create an account for me.

Is it possible to find somebody who could rent me an account for development of my application? If it is, where could I do it?
As far as I understood It's legal enough until I don't trade for real money from these account.
Sauerkraut is a good option if you like actual food.
Thank you, I guess trying won't hurt, nobody has ever regretted learning anything after all. As for feeling discouraged, being stupid (in various degrees) is part of the learning process I believe. Couldn't say I'm learning anything otherwise.
I will try Haskell alongside Python to see how it goes.
The obvious importance of gut bacteria is the health-news flavor of the month, but I don't know. There are definitely two sides to this debate. On the other side some very smart people with nothing to sell (probiotics/prebiotics/tests) argue for a relatively sterile gut. They say feeding gut bacteria with fermentable fibers/starches in general generates LPS and other stressful toxins.

Some lab experiments definitely bear out this idea. Animals with sterilized guts fed sterile diets live way longer, and are stronger/healthier.

Like I said I don't know, but I advise extreme caution on this stuff where there's any tangential connection to probiotics/prebiotics/tests.
Those rates make me go wat. I make $20/hr. :(

But can we apply this to the skills we'll need for starfighters.io? It's very easy to point to money (or even companies) lost by data breaches and say "I can help you prevent this", but the money you save may be whatever they pay for breach insurance or it may be literally everything they own. Case studies and deliverable targets (+millions of dollars from SEO and stuff) are really great when they're positive, but how do you negotiate this when you're selling protection against income loss?
Seriously, unless you're deeply passionate about the vision of the company you're working for, it's super important to keep tabs on the market and leave companies that are (for lack of a better term) taking advantage of you. Unscrupulous employers, especially traditional scrooge-mcduck-business-entrepreneurs, will try to squeeze you as hard as they can while paying you as little as they can (a good rule of thumb for spotting these men and women is that they're in their business just to make money, not to chase some "nobler" vision). So it's critical that you get out as soon as you can not only because it'll be better for your financial and emotional well-being, but also so that you don't lower the market wage average of your profession and wind up hurting all the other people in your industry.