skysight-inc/HackerNews huggingface dataset:
It would be nice if they made it even easier for users on hosted services who can't necessarily change robots.txt so you could opt out on a per-page basis. But I don't think anyone expects Genius to act in good faith.
Director of iOS and Mac Engineering
Sometimes the scaffolding should be left in place to help show others how to build things; other times, it was put up and taken down so many times that the learning from the first few attempts isn't worth it.

I would probably be much happier not squashing stuff if you were able to bisect cleanly to points between branch merges. I don't think that's even theoretically possible; which means that when you're bisecting it's quite possible to pick up half-baked mid-branch points that you have to recognise for the broken rubbish they are - lots of false positives there occasionally, and makes bisect a lot less useful. On a repo with nice squashed commits, you tend to be able to narrow down to the feature very quickly - of course those commits then tend to be bigger etc., but I find that less of an issue.
Wow this is a disaster waiting to happen. They will never generate enough profits to support this type of funding.
> Has Facebook ever been hacked to this degree?

Yes, security researchers have reached FB servers in the past few months.

> Has Google ever been hacked to this degree?

Yes, by Mainland Chinese agents a few years ago.

I know of similarly large networks that are currently owned.

And almost everybody has an IPMI problem, whether they realize it or not yet.

(Silicon Valley engineer here.)
People keep saying that, but I can't remember the last time Hipchat was down.
>"Next week we play, if Mark Zuckerberg was running Linux."

I prefer the game "Crucify Mark Zuckerberg for following Google's lead".

Although every day is that game around here :)
Which regulations?
Location: San Francisco, East Bay

Remote: No

Willing to relocate: No

Résumé/CV: https://www.linkedin.com/in/spencerochs

Github: https://github.com/Eochs/

Email: slochastic@gmail.com

I am a full-stack software developer with a background in statistics, machine learning, and databases. On the frontend I am proficient with Javascript, React, Backbone, D3, and Node.js. On the backend I have extensive experience with Python, Django, Numpy, Scipy, Sklearn, Pandas, and MRjob. I have designed and built MongoDB, Neo4j, Redis, MySQL, and Postgres databases. I have a passion for engineering at all levels of the stack, as well as a keen interest in the analysis of data.
I've experienced the same issue from multiple service providers, including but not limited to Google, Akamai, Cloudflare, and more.

My Linode IP address was assigned to me years ago. I do not use it maliciously, do not share it with other people, and have never used it for tor. Yet find myself regularly blocked for no logical reasons when I proxy my web-request through it.
The demo/blog page can use some animated gif(s).
To put it another way, the garage weekends step only makes sense if you're never planning on taking investment in the first place. Bootstrapping requires garage weekends (or enough of a nest-egg that engineer-you can work full-time for visionary-you.) The whole point of venture capital is to skip that part.

Importantly, a startup with enough sweat put into it that it's now executing on a business model instead of searching for a viable business model is no longer a startup; and if that's the only thing a VC is funding, then that person is not actually a VC, but rather a private-equity investor.

(And you could go further, and point out that the whole concept of "private equity" was just for the sake of startups with market risk; and that, having validated their market and eliminated such risk, companies should—according to the spirit of the law—immediately do their IPO. These "venture capitalists"—really just plain-old "capitalists" at this point—would then be forced to compete with every other schlub who wants a piece of the company.
Thank you very much, I would love to hear your suggestions.
I don't think so. It seems like it was not because of lack of technology that failed a startup like escape dynamics but rather unwilling investors who were concerned about near term financial gains. Also, ground based for microwave driven IMHO is not the way to go if you are looking for reduced cost per kg per launch. No offense to the team, but they should be looking at orbital based techniques for similar power transfers - relyin on reduced atmospheric interference and much stronger power generation from direct sunlight.
Containers as Disruptive Technology for the Oil and Gas Industry
Updated to the new title from the article
Actual interactions with faculty and other students are what the university provides. Watching lectures and reading books isn't the same thing as "getting your hands dirty" with other people in the same room who are interested (or are experts) in the same topic.
Breakdown of U.S. tech IPOs in 1Q '16
[online Meetup] Going Cloud-Native with Navops Launch and Docker
Keep it lean. You aren't ready for Scrum
I'm not certain, but the existing manufacturers haven't yet figured out the best way to make their composite rods more "grippy". Seems like you can get them with a spiral groove or with a spiral ridge. So they haven't been around long enough for one form to win out over another.

Basalt fiber was also classified as a Soviet military secret for a while, so I'm thinking that applications useful for civilians, like concrete rebar, have probably been around since the 1990s.
WayUp (formerly Campus Job - YCW15) - https://www.wayup.com/joinus/

WayUp is the largest marketplace for college students to find part-time jobs, internships, and full-time entry level jobs for graduating students. Everyone remembers their first job. And now, we’re helping everyone get their first job. We democratize hiring by enabling all companies, no matter how big a recruiting team you have (or don't), to easily reach amazing students all over the country. You can read more about us at http://press.wayup.com.

We are one of the quickest-growing companies from our batch (we launched a little over a year ago and we're already 32+ people!), and we're growing out our engineering team and looking for great hackers who love getting features in the hands of users. We're absolutely obsessed with our users and making the experience of finding a job better, and you should be too. We raised our Series A and we're looking for all types of roles:

- Senior Engineering Lead (Python, previous leadership experience - help us scale our team and develop great engineering processes)

- Javascript developer (We use Angular, prior experience is a plus but not required)

- Front-end developer (Especially skilled with CSS and responsive web development)

- Don't see what you're looking for? Reach out anyway!

We're based in New York City and we're tons of fun--we work with college students all day long :) Come join us! https://www.wayup.com/joinus/
> It means that the code review process is more important that the code writing process.

If that were true, the optimal solution is PRs with individual commits that all pass testing. I find it much easier to review a series of small changes for logical correctness than mashing them together into a single PR. Github recently added this as a feature, so I'm not in a completely invisible minority there.

And then, when the review is over, having discreet commits makes git bisecting down to the commit that broke the system more granular.
To quote Uncle Albert and Bert:

> I always say, there's nothing like a good joke.

> No, and that was nothing like a good joke.
Nylas | https://nylas.com/ | San Francisco, CA (Mission) | Frontend (JS), Backend (Systems+Ops)

Hi! We're Nylas. We build N1, the extensible, open source email client, and the infrastructure powering it. We're looking for fronted application engineers (React, Electron, JS), designers, backend systems engineers, & infrastructure/operations engineers.

We recently launched N1, have accumulated over 16K stars on GitHub, and are looking for core application engineers to design an extensible platform around email, calendar, and contacts. You'll not only use modern web tech to build a better email experience, you'll design the developer platform to power the next generation of email apps. See more about N1 here: https://nylas.com/N1 & code: https://github.com/nylas/N1

We have more data for a single user than in most startups' entire database. We're scaling heavily and if you have experience with automated deployments, debugging running systems, release engineering, and on-call schedules, but are still comfortable writing code, we're for you. :)

We take pride in the diverse culture we've built and are looking for more than raw technical talent: https://www.youtube.com/watch?v=z7sHc4P4zPg

== We're particularly looking for folks who ==

* Take personal pride in their work and value autonomy and ownership
* Want the chance to step up and lead a team
* Put the work before ego. We've got each others' backs, and we want you to be with us on that

== A bit more about us ==

* Our backend is built on Python, Flask, gevent, nginx, MySQL, AWS, and Debian. We've been careful to keep our architecture componentized.
* N1 uses javascript (ES6), React, Flux, SQL for offline caching, Electron, and no jQuery
* Tons of our code is open source. Check it out: https://github.com/nylas
* We're a small team
* We have a paid vacation policy & value personal responsibility and ownership. Benefits include free

Lyft to & from the office, full health, dental, vision, and lunch every day. Some remote work / work-from-home is OK too

Apply at https://nylas.com/jobs or ping me directly (mg@nylas). I'm Michael, one of our co-founders. We're a diverse team, and encourage applications from all backgrounds.
Squashing entire pull requests that change multiple things into a single commit is a bad idea, yes. But uploading and asking for review on such wide-reaching pull requests is a bad idea in the first place.

Using fast-forward without squash is also a bad idea in many cases: the string of commits may contain multiple points that don't actually build or pass tests, even if the final commit in the chain fixes all that. There's no point in landing those broken commits, and doing so will confuse bisection tools.

Fast-forward with squash, and enforcing reasonably sized code reviews as a matter of culture, is the best of all worlds in my opinion.
I say start looking for a new job, as well. Late pay is a prelude to a nonexistent job.
I wish DuckDuckGo would change their name and branding. I can't take anything they do seriously.
I understand the point of view that it's useful to see what "actually" happened. But the other way to think about it is like this: at some point, when a developer in the future wants to understand how #master evolved over time, should the burden of linearizing the history rest with that developer (making sense of a complex graph), or with people who make changes to #master when they make them?
Monetizr: add advertisements to open source R packages
Reminds me of the art style in Ridiculous Fishing.

https://www.google.com/search?q=Ridiculous+Fishing&tbm=isch
They're not full of little lies. Projects insist on squash-before-merge to help developers keep their sanity.

Imagine working on a fast-changing block of code with 20 or so other people concurrently. If all 20 of those peoples have patches submitted to master for review, and all of those patches have multiple commits each, then every time one gets merged, the others will have to rebase to its changes and fix conflicts for _every single commit_ while the fast forward plays out. It's a horrible experience. It prevents desirable code from getting in as contributors drop out due to the browbeating.

Squashing commits can be the difference between tediously fixing something once vs. tediously fixing it 20 times. No one needs to know that you changed your mind about calling that struct "ConfigOpts" before it was ever introduced upstream.
I was about to share this on hipchat at work until I realized it's April 1st. Very well written April Fools post!
I've been using DuckDuckGo for several years, but sadly their search doesn't really help for technical topics. I let them have first crack at the answer, and then usually have to add !g to let google have the next crack.

The underlying problem is what they do when a search contains multiple words - 3 or more especially. DDG starts ignoring some of the words, but usually that is what matters. For example search for [usb type c resistor] and the DDG results treat the "resistor" part of the search as a small amount of what is being searched, with many results not that directly useful. As a human we know that [usb type c] is very common, and adding the [resistor] part is actually the meat of the query. Google gets that and gives better results, although they aren't miles apart.

The pattern is the user adds more terms to make the search more specific, while DDG then seems to use them to make the search more general. For technical stuff you really did want the specific! That aside DDG has been slowly but surely getting better over the years.
> It's the one thing I hate about Android. The UIs of Google
> apps have gotten consistently worse over the years, mainly
> because they've been prioritizing aesthetics over
> functionality/ease of use.

Care to elaborate on this with a few examples? I have the opposite complaint. They seem to be focussing on ease of use precisely at the expense of functionality. I'd rather stuff was a little more complicated, because it would give me more control over stuff. Note that I don't want it complicated for the sake of complexity. But I've noticed a increase in "adding features makes stuff complicated" and joke memes about "just make it an option". Well, programming - proper programming - IS hard, but it's worth it because you get a better product.
If I feel like the history of a branch is important, I add a git tag to the branch head before rebasing. I have a naming convention for these tags.
Then I usually do a rebase -i on to the main branch.
Agreed and particularly unsettling given the NSA's precedents; how do we know Slack isn't simply siphoning data to them via secret frontdoor collaboration or unknown backdoor (or combination thereof [1]).

[1] https://www.washingtonpost.com/world/national-security/nsa-i...
This is a ubiquitous business model that will succeed where evernote failed.
For someone with fast network, I don't mind with one more click. It's about same to click on "show more". But well, no harmful at all.

I expected the cheatsheet also linking to useful help page, then it'd be super cool!

also, if i type in 'mysql data types', it won't show anything.
https://duckduckgo.com/?q=mysql+data+types
On a given site, not necessarily, but on some sites that cloudflare is protecting, pretty much always would be my guess... cloudflare doesn't know you're not the spammer/bot/malicious actor using the same exit node... it only knows that you don't have any cookies, and that means you look a lot like the bad guys coming from the same IP.

One could setup an IDENT-like service that delivers a hash for the source's route, and that would enable better scoring, but also could be used as a tracking measure... you can't have one without the other.

Even then, it would take either the user allowing cookies, or the TOR system to change their exit nodes.
Show HN: Material Management
Production-Ready Application Rollouts Using Deployment Objects in Kubernetes 1.2
Let me start with, I agree 100%. And then comes the "but".

The public policy prescription often made in order to achieve this goal is to bring manufacturing back. Unfortunately (?) in advanced economies manufacturing is no longer a steady source of plentiful blue-collar jobs.

I think that's what the parent comment was getting at with "there's no rule" - if you encourage the manufacturing sector, there's no rule that makes it create jobs when economic imperatives drive it to greater automation.

Jobs that are available to people without much education, savings, or assorted social capital are absolutely necessary to the stability of our society. I just don't think manufacturing can get us those in a country with developed-country living standards.

EDIT: Fixed lots of phone-keyboard typos.
Meet Tesla's Model 3
TokBox Engineer here. We set out to make a high quality starting point for anyone who wants to include embedded RTC in their next app (or crazy idea). Part of that is solving for the client-side concerns, like an easy toolchain, rich APIs for customizability, and some helpful code that shows the best practices our combined experience with the platform has given us (like above, but stay tuned for more!).

But there are definitely more parts, TURN/STUN for network traversal is just the beginning. The OpenTok platform behind this sample app adds dynamic optimizations (like audio fallback), archiving (recording) capabilities, RESTful APIs for eventing and control, etc. Just standing up a STUN/TURN server isn't going to solve the hard problems it takes to make something that can eventually go to production.

EDIT: spacing, clarity
«Have you ever tried following a change in a repo that came from an unsquashed PR?»

I have a self-congratulating black belt in source code archeology. With the right tools, most of which are on GitHub, even, such as good commit range diffing, smart uses of tags and branches, and knowing how to navigate the DAG from merge commits (more reason to -no-ff) you have a lot of power in your hands.

«What's truly meaningful IMO is a git log that reads like a product change log»

I appreciate that point of view, but I don't share it. A product change log, I feel, is a bit of marketing/PR that needs some time, love, and editing; I find a git log is for catching snapshots of raw progress and more often useful in seeing what your co-developers are up to, as they are working.
Musician sues Royal Opera House over ruined hearing
The torrent is not very good, and anyway there aren't really any seeds anymore. It's better to get it from the Internet Archive https://archive.org/details/archiveteam-geocities This script makes downloading more convenient: http://blog.geocities.institute/archives/3209
I know that I probably swear in church since git is the current de facto standard for version control but this shows that gits usability is way too low. Why do I have to invest so much time to understand the inner workings of a tool that should just help me collaborate with my coworkers?
I've given up on understanding git and use gitflow and the built in tools in Intellij Idea for all my branching/merging/committing needs.
Instead of asking for race/ethnicity, just say that the shirts are available in fit variations A, B, C, etc., and show photos of several models of all races each modeling the variation that fits that model best.

Leave it to the customer to notice that the majority of white models are wearing "A", the majority of black models are wearing "B", and so on and guess that if they don't know otherwise they have the best chance of getting a good fit by going with the variation that is best for the majority of models that look like them.

This still lets customers have the best shot at getting a great fit, and furthermore if it turns out wrong for a particular customer it is easier for them to realize they need to try another variation next time.

If I ordered a shirt and told the company I'm white and it did not fit well, it would not occur to me to go back and tell them I'm black on my next order, because I probably would not even be connecting race with fit.

With an A, B, ..., system, on the other hand, if my "A" shirt didn't fit right it would immediately occur to me that maybe the "B" shirt would be better.
This, along with !bang syntax and respect for privacy is what makes DDG my favourite search engine.

I really love typing "Maxwell's equations !w" or similar if I know I want the Wikipedia page for it.

Although the search results aren't always perfect (I still use Google occasionally, especially for non-English queries) these features are truly killer.

Learned some !bang shortcuts and it saves me time every single day. The cheatsheets are good too and having StackOverflow answers pop up at the top is also a great way to quickly get the right info.
I don't blame you. Git has terrible usability.
This assumes the builders and buyers of houses are on the same page. Instead builders generally go up market and lower income buyers are stuck with older homes. Over time the U.S. economy is suck with aging BMW's instead of civics.

You often see the same disconnect between efficency's and 1BR apartments.

PS: Even really cheap things are missing. Such as a drain in a kitchen / bathroom incase of a leak or overflow. Ductwork in the walls for cables. Insulation tends to be half assed unless required for code, because it's not visible and builders are not suck with energy bills. Let alone something like solar hot water heaters.
Plus, it's all probably subject to discovery if you get sued, even assuming it doesn't get hacked.
I joined a startup and it's been a month they haven't paid me, what can i do?
I joined a startup and it's been a month they haven't paid me, what can i do?

I have a full-time contract.
I was told I'd be paid on the 30th of March, and the co-founder called me saying they're having "financial delays".

Prior to getting hired, I did asked them what was their financial runway and the co-founder told me a year and a half.

What would you do in my situation?

I'd need your opinion,

thank you!

EDIT #1:
I am a full-time employee, not a contractor.
The thing is, I never asked when would be my first paycheck, so I assumed it would be every 14/15 days like it mostly is everywhere. So I contacted the "HR" lady, which is a new hire as well, and she told me I'd get paid on the 30th since my direct deposit isn't setup.
I told her i could set it up right now, and she said they are waiting to move to a new HR system, then they'll get in touch with me (it did not contact me)
Also, I had to contact them otherwise I wouldn't have heard from anyone, it could have kept on going forever.

I'm not sure, but it seems that other new hires have been in this situations for months... Do you think i was duped into getting hired and work for free?
Because this is a quite advanced feature, and creating an interface for it is inherently hard. IIRC, the IDEA interface for interactive rebase ends up looking exactly the same as the text-mode one.
Show HN: Budding new file format
We've moved all the logic from the rolling update on the client side to the server, as well as building in rollback and versioning. AMA!

Disclosure: I work at Google on Kubernetes
Except tell the individuals apart and so you can't limit it to 1,000 individuals. You can't just let some in if you can't tell them apart. There is no door that works that way in this case.

It's best to imagine it's a walk-up bar rather than one with a door.
Surely if you're using software you should be capable of operating it properly? That's probably what might getting people into trouble. If you can't figure out how to send an email properly then you're flagging up to potential employers that you're a bit of a muppet. I'd not want to compound that with a lawsuit which tells potential employers that you're also a humourless cretin.
One thing I've learned in my career: Whenever there is a failure, it's almost always caused by more than one mistake. The root-cause could be someone not paying attention, but if that mistake can be disastrous, you shouldn't be relying on that one-point of failure. If "finding someone to blame" is the solution to a problem, your org has failed in more ways than one.

I've had mixed experiences, but I find the orgs that set up roadblocks to prevent single-mistakes from causing issues are much better off.