hazz

GoCardless (YC S11) | London | DevOps, Data, Backend and Frontend Engineers | Onsite | Full-time | Visa

GoCardless is building a payments network for the internet. Since 2011 we've been focused on simplifying Direct Debit for small and medium companies (who previously had no access to it) and we're now expanding to serve the largest companies (think newspapers, utilities) and connect with existing payment systems in countries all over the world. We already support the UK and Europe and are aiming to expand to more countries over the next year.

As an engineering team at GoCardless we care most about stable, reliable, understandable code. We rely on testing and code review and a culture of frequent constructive feedback. We define and manage our own roadmap and run projects in whatever way works best for us.

Our stack: Rails, Angular, Postgres, Elasticsearch, Docker, Chef. We also have a bit of Go and Python knocking around.

We love learning new things and contributing back to the community. We open source everything we can[1] and regularly host meetups and hackathons at our wheelchair-accessable office in Angel. We have a weekly bookclub within the team and give internal (and external) talks about things that interest us.

Interview process: an intro call, one coding challenge, then a couple of onsite interviews (pair programming and some chats - no whiteboards!)

For more info and to apply: https://gocardless.com/jobs. If you've got any questions, drop me an email (it's in my profile).

[1] Notable examples are Statesman (https://github.com/gocardless/statesman) and Coach (https://github.com/gocardless/coach)

GoCardless (YC S11) | London | DevOps, Data, Backend and Frontend Engineers | Onsite | Full-time | Visa

GoCardless is building a payments network for the internet. Since 2011 we've been focused on simplifying Direct Debit for small and medium companies (who previously had no access to it) and we're now expanding to serve the largest companies (think newspapers, utilities) and connect with existing payment systems in countries all over the world. We already support the UK and Europe and are aiming to expand to more countries over the next year.

As an engineering team at GoCardless we care most about stable, reliable, understandable code. We rely on testing and code review and a culture of frequent constructive feedback. We define and manage our own roadmap and run projects in whatever way works best for us.

Our stack: Rails, Angular, Postgres, Elasticsearch, Docker, Chef. We also have a bit of Go and Python knocking around.

We love learning new things and contributing back to the community. We open source everything we can[1] and regularly host meetups and hackathons at our wheelchair-accessable office in Angel. We have a weekly bookclub within the team and give internal (and external) talks about things that interest us.

Interview process: an intro call, one coding challenge, then a couple of onsite interviews (pair programming and some chats - no whiteboards!)

For more info and to apply: https://gocardless.com/jobs. If you've got any questions, drop me an email (it's in my profile).

[1] Notable examples are Statesman (https://github.com/gocardless/statesman) and Coach (https://github.com/gocardless/coach)

GoCardless (YC S11) | London | DevOps, Data, Backend and Frontend Engineers | Onsite | Full-time | Visa

GoCardless is building a payments network for the internet. Since 2011 we've been focused on simplifying Direct Debit for small and medium companies (who previously had no access to it) and we're now expanding to serve the largest companies (think newspapers, utilities) and connect with existing payment systems in countries all over the world. We already support the UK and Europe and are aiming to expand to more countries over the next year.

As an engineering team at GoCardless we care most about stable, reliable, understandable code. We rely on testing and code review and a culture of frequent constructive feedback. We define and manage our own roadmap and run projects in whatever way works best for us.

Our stack: Rails, Angular, Postgres, Elasticsearch, Docker, Chef. We also have a bit of Go and Python knocking around.

We love learning new things and contributing back to the community. We open source everything we can[1] and regularly host meetups and hackathons at our wheelchair-accessable office in Angel. We have a weekly bookclub within the team and give internal (and external) talks about things that interest us.

Interview process: an intro call, one coding challenge, then a couple of onsite interviews (pair programming and some chats - no whiteboards!)

For more info and to apply: https://gocardless.com/jobs. If you've got any questions, drop me an email (it's in my profile).

[1] Notable examples are Statesman (https://github.com/gocardless/statesman) and Coach (https://github.com/gocardless/coach)

GoCardless (YC S11) | London | DevOps, Data, Backend and Frontend Engineers | Onsite | Full-time | Visa (full-time only)

GoCardless is building a payments network for the internet. Since 2011 we've been focused on simplifying Direct Debit for small and medium companies (who previously had no access to it) and we're now expanding to serve the largest companies (think newspapers, utilities) and connect with existing payment systems in countries all over the world. We already support the UK and Europe and are aiming to expand to more countries over the next year.

As an engineering team at GoCardless we care most about stable, reliable, understandable code. We rely on testing and code review and a culture of frequent constructive feedback. We define and manage our own roadmap and run projects in whatever way works best for us.

Our stack: Rails, Angular, Postgres, Elasticsearch, Docker, Chef. We also have a bit of Go and Python knocking around.

We love learning new things and contributing back to the community. We open source everything we can[1] and regularly host meetups and hackathons at our wheelchair-accessable office in Angel. We have a weekly bookclub within the team and give internal (and external) talks about things that interest us.

Interview process: an intro call, one coding challenge, then a couple of onsite interviews (pair programming and some chats - no whiteboards!)

For more info and to apply: https://gocardless.com/jobs. If you've got any questions, drop me an email (it's in my profile).

[1] Notable examples are Statesman (https://github.com/gocardless/statesman) and Coach (https://github.com/gocardless/coach)

GoCardless (YC S11) | London | Frontend, Backend, SRE, Data Engineer | Onsite | Full-time & Interns | Visa

GoCardless is building a payments network for the internet. Since 2011 we've been focused on simplifying Direct Debit for small and medium companies (who previously had no access to it) and we're now expanding to serve the largest companies (think newspapers, utilities) and connect with existing payment systems in countries all over the world. We already support the UK and Europe and are aiming to expand to more countries over the next year.

As an engineering team at GoCardless we care most about stable, reliable, understandable code. We rely on testing and code review and a culture of frequent constructive feedback. We define and manage our own roadmap and run projects in whatever way works best for us.

Our stack: Rails, Angular, Postgres, Elasticsearch, Docker, Chef. We also have a bit of Go and Python knocking around.

We love learning new things and contributing back to the community. We open source everything we can[1] and regularly host meetups and hackathons at our wheelchair-accessable office in Angel. We have a weekly bookclub within the team and give internal (and external) talks about things that interest us.

Interview process: a couple of phone screens, one take home test, then a couple of onsite interviews (pair programming and some chats - no whiteboards!)

For more info and to apply: https://gocardless.com/jobs. If you've got any questions, drop me an email (it's in my profile).

[1] Notable examples are Statesman (https://github.com/gocardless/statesman) and Coach (https://github.com/gocardless/coach)

GoCardless (YC S11) | London | Frontend, Backend, SRE, Data Engineer | Onsite | Full-time

GoCardless is building a payments network for the internet. Since 2011 we've been focused on simplifying Direct Debit for small and medium companies (who previously had no access to it) and we're now expanding to serve the largest companies (think newspapers, utilities) and connect with existing payment systems in countries all over the world. We already support the UK and Europe and are aiming to expand to more countries over the next year.

As an engineering team at GoCardless we care most about stable, reliable, understandable code. We rely on testing and code review and a culture of frequent constructive feedback. We define and manage our own roadmap and run projects in whatever way works best for us.

Our stack: Rails, Angular, Postgres, Elasticsearch, Docker, Chef. We also have a bit of Go and Python knocking around.

We love learning new things and contributing back to the community. We open source everything we can[1] and regularly host meetups and hackathons at our office in Angel. We have a weekly bookclub within the team and give internal (and external) talks about things that interest us.

Interview process: a couple of phone screens, one take home test, then a couple of onsite interviews (pair programming and some chats - no whiteboards!)

For more info and to apply: https://gocardless.com/jobs. If you've got any questions, drop me an email (it's in my profile).

[1] Notable examples are Statesman (https://github.com/gocardless/statesman) and Coach (https://github.com/gocardless/coach)

GoCardless (YC S11) | London | Frontend, Backend, SRE, Data Engineer | Onsite | Full-time

GoCardless is building a payments network for the internet. Since 2011 we've been focused on simplifying Direct Debit for small and medium companies (who previously had no access to it) and we're now expanding to serve the largest companies (think newspapers, utilities) and connect with existing payment systems in countries all over the world. We already support the UK and Europe and are aiming to expand to more countries over the next year.

As an engineering team at GoCardless we care most about stable, reliable, understandable code. We rely on testing and code review and a culture of frequent constructive feedback. We define and manage our own roadmap and run projects in whatever way works best for us.

Our stack: Rails, Angular, Postgres, Elasticsearch, Docker, Chef. We also have a bit of Go and Python knocking around.

We love learning new things and contributing back to the community. We open source everything we can[1] and regularly host meetups and hackathons at our office in Angel. We have a weekly bookclub within the team and give internal (and external) talks about things that interest us.

Interview process: a couple of phone screens, one take home test, then a couple of onsite interviews (pair programming and some chats - no whiteboards!)

For more info and to apply: https://gocardless.com/jobs. If you've got any questions, drop me an email (it's in my profile).

[1] Notable examples are Statesman (https://github.com/gocardless/statesman) and Coach (https://github.com/gocardless/coach)

GoCardless (YC S11) | London | Frontend, Backend, SRE | Onsite | Full-time

GoCardless is building a payments network for the internet. Since 2011 we've been focused on simplifying Direct Debit for small and medium companies (who previously had no access to it) and we're now expanding to serve the largest companies (think newspapers, utilities) and connect with existing payment systems in countries all over the world. We already support the UK and Europe and are aiming to expand to more countries over the next year.

As an engineering team at GoCardless we care most about stable, reliable, understandable code. We rely on testing and code review and a culture of frequent constructive feedback. We define and manage our own roadmap and run projects in whatever way works best for us.

Our stack: Rails, Angular, Postgres, Elasticsearch, Docker, Chef. We also have a bit of Go and Python knocking around.

We love learning new things and contributing back to the community. We open source everything we can and regularly host meetups and hackathons at our office in Angel. We have a weekly bookclub within the team and give internal (and external) talks about things that interest us.

Interview process: a couple of phone screens, one take home test, then a couple of onsite interviews (pair programming and some chats - no whiteboards!)

For more info and to apply: https://gocardless.com/jobs. If you've got any questions, drop me an email (it's in my profile).

GoCardless (YC S11) | London | Frontend, Backend, SRE | Onsite | Full-time

GoCardless is building a payments network for the internet. Since 2011 we've been focused on simplifying Direct Debit for small and medium companies (who previously had no access to it) and we're now expanding to serve the largest companies (think newspapers, utilities) and connect with existing payment systems in countries all over the world. We already support the UK and Europe and are aiming to expand to more countries over the next year.

As an engineering team at GoCardless we care most about stable, reliable, understandable code. We rely on testing and code review and a culture of frequent constructive feedback. We define and manage our own roadmap and run projects in whatever way works best for us.

Our stack: Rails, Angular, Postgres, Elasticsearch, Docker, Chef. We also have a bit of Go and Python knocking around.

We love learning new things and contributing back to the community. We open source everything we can and regularly host meetups and hackathons at our office in Angel. We have a weekly bookclub within the team and give internal (and external) talks about things that interest us.

Interview process: a couple of phone screens, one take home test, one onsite interview (pair programming and some chats - no whiteboards)

More info: https://gocardless.com/jobs.

If you've got any questions, let me know (email's in my profile).

They're actually available in stable behind a feature flag (chrome://flags/#enable-native-notifications).

Similar item linking to the blog post: https://news.ycombinator.com/item?id=10895994

Firefox doesn't trust the cert yet. The application to be added to the root store is here https://bugzilla.mozilla.org/show_bug.cgi?id=1204656

This is a repost, original article here: https://medium.com/product-notes/the-mystery-of-the-power-ba...

In this case the strike was actually carried out by attack helicopters, not the drone. The main point of the article is to highlight the poor communication between the various different groups involved in the operation and the overall ignorance of everyone involved, despite many hours of surveillance by the drone.

cached version: http://webcache.googleusercontent.com/search?q=cache:www.iti...

As I understood it, this was more in response to academics' frustration that he did not properly define operators he went on to use in his derivations. I can sympathise with this - mathematical proofs are difficult enough to follow without having to guess the action of the operators involved.

Would it be helpful to tag this with [sound] or something? The music autoplay took me by surprise.

I would say in comparison to storing it on the server, storing the encrypted private key in Keychain probably offers a lot more security. An attacker would need direct access to the device and would need to either a) know the user's passphrase, b) be able to fool TouchID or c) be able to bypass Keychain's security.

However if iCloud Keychain is enabled then this opens up the attack surface a lot more.

Although according to the article it is risking a €100,000 fine on top of €40,000 fine given to the driver. That could rack up pretty quickly if it were on a per-violation basis.

The last update on the News page[0] is dated "June 13, 2011", so it seems not. A shame, it's such an interesting project.

[0] http://www.nablaman.com/relay/progress.php

90-95% of adults had it at some point. Most people develop immunity to it and so it doesn't survive in them. I'd say the most successful virus in humans would be the common cold, given how frequently we seem to get it, although it's more of a massive family of virii.

Here's the paper in question: http://arxiv.org/abs/1411.4849

This is the first smart watch I've seen that actually looks good. It's clearly aiming to look as much as possible like a traditional watch when not actively being used.

It does look huge on the woman's wrist on the second slide/page/section thing. Big watches tend to be a men's fashion thing, so I wonder if this will present problems.

The heart rate feature seems really out of place and useless. What use is a recent history of your heart rate? Presumably there are plans to integrate more features into the health part of things, because at the moment it looks a lot like a "because we can" feature.

This appears to be a Swift wrapper for SQLite 3, not some sort of open source version of the Swift language, as the title implies.

I would love this, but the file sizes would be insane. We'd be talking hundreds of megabytes (possibly gigabytes?) per song. Unless each track was MP3 encoded first, but I'd imagine you'd have trouble mixing tracks together from lossy sources.

https://simplysecure.org/ is the project that Google is supporting, which seems to be an open consultancy that works with OSS crypto/security/privacy projects to make them easier to use.

This looks like a really cool piece of kit, but sadly it was introduced with an unwatchable video.

"Our technology fundamentally enhances human capability"

No it doesn't. You've made a HUD that fits in a motorcycle helmet. You haven't created Iron Man.

The statement is then shortly followed by some obnoxious dubstep. It's a shame because it completely put me off looking further at what could be a great product.

Specifically, lightweight, short-distance personal transportation is something we’re interested in.

Doesn't this already exist, in the form of the bicycle?

One advantage might be that you could have all the materials delivered in one go from a single supplier (a concrete manufacturer), instead of having multiple deliveries from different places for the different materials (brick, concrete, cement, rebar, etc).

Determined to pursue the idea further, Craven contacted Dunnett’s widow and purchased the man’s patent for a sum of less than £20 (about $30 USD).

This is slightly misleading. If that was the actual price he paid, it was the equivalent of about £500 today.