HN user

jessepollak

1,600 karma

head of engineering, consumer @ coinbase

http://github.com/jessepollak http://jessepollak.com hello@jessepollak.com

[ my public key: https://keybase.io/jessepollak; my proof: https://keybase.io/jessepollak/sigs/otR518zU2vEMBVsPkTxSLFsrP3Ok4tGs_p-Gfhms0YU ]

Posts86
Comments170
View on HN
blog.coinbase.com 6y ago

Coinbase Incident Post Mortem: April 29 and May 9, 2020

jessepollak
2pts0
blog.coinbase.com 6y ago

Coinbase Incident Post Mortem: June 25–26, 2019

jessepollak
127pts28
blog.coinbase.com 6y ago

What Are Coinbase's Engineering Principles?

jessepollak
2pts0
blog.coinbase.com 7y ago

On becoming a senior technical leader

jessepollak
2pts0
github.com 8y ago

Show HN: Calendarculator – A clt to count the hours your team spends in meetings

jessepollak
1pts0
news.ycombinator.com 9y ago

Ask HN: What steps should we take before open sourcing our business?

jessepollak
2pts1
blog.instant2fa.com 9y ago

Never spend more than 37% – the golden rule of security spending

jessepollak
1pts0
blog.instant2fa.com 9y ago

The best time to integrate two-factor authentication

jessepollak
1pts0
blog.instant2fa.com 9y ago

How to 2FA Everything (Part 2)

jessepollak
3pts0
blog.instant2fa.com 9y ago

What is DDOS and why was Twitter down all day?

jessepollak
1pts0
blog.instant2fa.com 9y ago

How to protect your account when SMS is the only 2FA option

jessepollak
2pts0
blog.instant2fa.com 9y ago

How to 2FA Everything, Part 1

jessepollak
9pts0
money.cnn.com 10y ago

Cooking for Oakland: How this tech startup gives back

jessepollak
1pts0
medium.com 10y ago

Don't force people to understand how the Internet works

jessepollak
51pts30
www.theatlantic.com 10y ago

Why I Quit Ordering from Uber-For-Food Startups

jessepollak
17pts3
www.dailydot.com 10y ago

Startup open-sources its diversity policies so others can copy them and iterate

jessepollak
2pts0
medium.com 10y ago

Clef Cooks 100 Dinners

jessepollak
1pts0
medium.com 10y ago

A practical use for NamedTuples

jessepollak
3pts0
medium.com 11y ago

You can't insure your relationships

jessepollak
1pts0
medium.com 11y ago

Building a better developer experience with React

jessepollak
1pts0
medium.com 11y ago

Imagine a time-interactive movie

jessepollak
1pts0
medium.com 11y ago

Dynamic tooltip text with CSS only

jessepollak
1pts0
blog.getclef.com 11y ago

Be better today than yesterday

jessepollak
1pts0
medium.com 11y ago

Lesson #1: Use Ordered Lists

jessepollak
4pts0
www.pcg-random.org 11y ago

PCG, a Family of Better Random Number Generators

jessepollak
1pts0
medium.com 11y ago

The Handstand Theory

jessepollak
2pts0
knowingourselves.tumblr.com 11y ago

Everything's amazing and nobody's happy (part 1)

jessepollak
1pts0
jessepollak.github.io 12y ago

Show HN: Card – An interactive CSS3 credit card form

jessepollak
376pts112
markhudnall.com 12y ago

The question isn't "which is better?" as much as "how do I survive?"

jessepollak
3pts0
ryhan.org 12y ago

Better voice commands using head-tracking and proximity sensing [video]

jessepollak
22pts2

All of them were cross-trained to be React Native engineers. Many of them are now working full time in React-land doing product engineering and some of them are working on lower level native infrastructure. We saw very little attrition and have emerged as a stronger, unified client engineering group (across mobile and web).

We did consider Flutter, but (1) we already had a very strong javascript talent base that we wanted to leverage; (2) at the time when we made the decision, Flutter was still relatively early in its lifecycle.

That said, we've spent a lot of time talking with teams using Flutter and we think it's awesome!

Hi all - I support all Retail engineering at Coinbase and was one of the folks who helped shepherd this change through from inception to rollout.

I'm happy to answer any questions that folks have - just thread here, and I'll either answer or pull in our team to give more detail.

Coinbase (YC S12) | Remote, San Francisco, New York, London | Onsite | https://www.coinbase.com

Digital currency will bring about more innovation, efficiency, and equality of opportunity in the world by creating an open financial system. We can use this new technology to help good ideas spread faster, reduce the inefficiencies that legacy payment networks impose on the world, and provide access to financial services to several billion people in the developing world.

I've personally been here for 3 years and love it. Tons of autonomy, lots of really challenging problems, and a super mission aligned employee group.

We're particularly interested in folks who are interested in building a world-class Javascript platform across React and React Native. Also, we just went fully remote-first (focus on US-remote hiring for now), so would love to hear from folks who are interested in that!

See all our open roles at Coinbase here: https://coinbase.com/careers

Tech Stack: Go, Ruby Rails, React (web), Swift (iOS), Kotlin & React Native (Android)

If you're interested in chatting more, feel free to shoot me an email at jpollak@coinbase.com. Looking forward to talking!

Coinbase (YC S12) | San Francisco, New York, London | Onsite | https://www.coinbase.com

Digital currency will bring about more innovation, efficiency, and equality of opportunity in the world by creating an open financial system. We can use this new technology to help good ideas spread faster, reduce the inefficiencies that legacy payment networks impose on the world, and provide access to financial services to several billion people in the developing world.

I've personally been here for 3 years and love it. Tons of autonomy, lots of really challenging problems, and a super mission aligned employee group.

We're particularly interested in folks who are interested in building a world-class Javascript platform across React and React Native.

See all our open roles at Coinbase here: https://coinbase.com/careers

Tech Stack: Go, Ruby Rails, React (web), Swift (iOS), Kotlin & React Native (Android)

If you're interested in chatting more, feel free to shoot me an email at jpollak@coinbase.com. Looking forward to talking!

Coinbase (YC S12) | San Francisco, New York, London | Onsite | https://www.coinbase.com

Digital currency will bring about more innovation, efficiency, and equality of opportunity in the world by creating an open financial system. We can use this new technology to help good ideas spread faster, reduce the inefficiencies that legacy payment networks impose on the world, and provide access to financial services to several billion people in the developing world.

I've personally been here for 3 years and love it. Tons of autonomy, lots of really challenging problems, and a super mission aligned employee group.

To learn more about who we are, our engineering culture, and whether this is the right place for you, read our Key Values profile: https://www.keyvalues.com/coinbase

See all our open roles at Coinbase here: https://grnh.se/8a8a01cf1

Tech Stack: Go, Ruby Rails, React (web), Swift (iOS), Kotlin & React Native (Android)

If you're interested in chatting more, feel free to shoot me an email at jpollak@coinbase.com. Looking forward to talking!

Coinbase (YC S12) | San Francisco, New York, Chicago, London | Onsite | https://www.coinbase.com

Digital currency will bring about more innovation, efficiency, and equality of opportunity in the world by creating an open financial system. We can use this new technology to help good ideas spread faster, reduce the inefficiencies that legacy payment networks impose on the world, and provide access to financial services to several billion people in the developing world.

To learn more about who we are, our engineering culture, and whether this is the right place for you, read our Key Values profile: https://www.keyvalues.com/coinbase

See All Open Roles at Coinbase here: https://grnh.se/8a8a01cf1

Tech Stack: Ruby, Rails, Go (Backend) React, Flow, styled-components, Mobx (Frontend), Swift (iOS), Kotlin (Android)

If you're interested in chatting more, feel free to shoot me an email at jpollak@coinbase.com. Looking forward to talking!

Personal opinion, not the company: I think it's very cool. I've been watching them since they launched and have been impressed with their consistent progress. I love using it as an example of financial experimentation and success: they launched at the top of the bubble and have been able to keep stability even as crypto has gone through a massive crash! Pretty amazing.

Hi all — head of engineering for the consumer product at Coinbase here (iOS, Android, coinbase.com).

Happy to answer any questions that people have — also, just wanted to make a plug that we're hiring. If you're interested in building an open financial system for the world, shoot me a note at jpollak@coinbase.com. Especially interested in iOS & Android engineers!

Coinbase | Senior Software Engineer, Site Reliability Engineer, Security Engineer | San Francisco, London | REMOTE, VISA | coinbase.com

We are hiring engineers to help us create an open financial system for the world. Specifically, I'm hiring both frontend and backend engineers to build Coinbase.com and the APIs that power the Coinbase mobile apps. Come work on digital currencies like Bitcoin and Ethereum every day!

About us:

* We use React, Mobx, Flow, webpack, and styled-components on the frontend.

* Our APIs are currently powered by Rails with a MongoDB backend, but we're investing heavily in decomposing the monolith into services written in statically typed languages.

* We're exploring GraphQL for future APIs and are hiring two people to lead our APIs team.

If you're interested, email me at jpollak@coinbase.com. I'm also more than happy to answer questions on here (about Coinbase in general or the roles).

NOTE: A spammer posted this same post below, not sure why.

Coinbase | Senior Software Engineer, Site Reliability Engineer, Security Engineer | San Francisco, London | REMOTE, VISA | coinbase.com

We are hiring engineers to help us create an open financial system for the world. Specifically, I'm hiring both frontend and backend engineers to build Coinbase.com and the APIs that power the Coinbase mobile apps. Come work on digital currencies like Bitcoin and Ethereum every day!

About us:

* We use React, Mobx, Flow, webpack, and styled-components on the frontend.

* Our APIs are currently powered by Rails with a MongoDB backend, but we're investing heavily in decomposing the monolith into services written in statically typed languages.

* We're exploring GraphQL for future APIs and are hiring two people to lead our APIs team.

If you're interested, email me at jpollak@coinbase.com.

I think this is a fair criticism and I agree that I might have used this comparison in a simplified way to make my point, but I think the primary thesis still holds: when building a React app, you necessarily need to make a very large number of choices that you don't need to make when building Ember.

This isn't because React is bad, it's because React is just the view layer! If we look at it this way, we can re-examine that list as:

* language

* view

* data modeling

* routing

* network connections

* functional utilities

* build

* styling

* testing

And, with React, when you have just a view layer, if you want to build an advanced application, you likely need to add on a bunch of other layers to get everything working. I hear you about being able to "just use React", but I also think that's a an oversimplification the other way: how many applications on the web today are built with only the view layer and none of the others?

After evaluating all the decisions we made in the past when building a React app, we decide to trust someone else to make them for us :)

p.s. the original title was "Choosing Ember of the React ecosystem in 2016" but I ended up shortening it :)

Absolutely! I would say that with Ember + ember-data, the framework conforms to a pattern where data is represented as models on the frontend, which can be updated and persisted to the server. These updates happen through a CRUD / REST API (in our case we conform to JSONAPI) and are generally triggered in a controller (or a route that contains logic and acts similar to a controller in a traditional MVC framework).

In the React ecosystem, I think there's been a pretty stark departure from that general pattern with things like redux and GraphQL, so while we love it, compared to what we'd been using , it felt a little behind.

Does that make sense?

Hey everyone - OP here! This was a really fun blog post to write and I think I learned a bunch in the process: if you have any questions, would be happy to answer!

Yeah, at our current size + team composition we don't feel like we have the knowledge/experience to do remote work well. With that informing our decision making, we've decided to prioritize other things (that have different tradeoffs).

I think as we keep growing this will definitely change. Would love to learn from someone like you who's obviously been super successful at doing remote well :)