Myxt | SF and/or Remote (PST +- 6 hours) | Looking for Software Engineers | https://myxt.com We’re an early team of 5 (maybe 6 when you read this) who are attempting to make a big music service. Myxt is building an application and suite for managing music files, workflows, listening, reviewing, payment, sharing, and annotation for digital creators and their collaborators and close-knit fans.
We're currently live on all platforms and release updates several times a week. Product development is communal and everyone in the company leads projects, tests releases, and engages with users and partners.
Previously among our team we started Google Reader and helped build the early success of companies like Stripe and Twitter.
We're backed by Accel Ventures in SF. We’re looking for people who love working on complex technical solutions for creative makers and especially for engineers like us who like having a huge impact on product development.
You can email us at jobs@myxt.com and we'll get back to you right away. (No recruiters please.)
Tech stack: Typescript, Solid JS, Flutter, GraphQL, Hasura, ffmpeg, Firebase, PostgreSQL, Dart, and more
Myxt | SF and/or Remote (PST +- 6 hours) | Looking for Software Engineers | https://myxt.com
We’re an early team of 5 (maybe 6 when you read this) who are attempting to make a big music service. Myxt is building an application and suite for managing music files, workflows, listening, reviewing, payment, sharing, and annotation for digital creators and their collaborators and close-knit fans.
We're currently live on all platforms and release updates several times a week. Product development is communal and everyone in the company leads projects, tests releases, and engages with users and partners.
Previously among our team we started Google Reader and helped build the early success of companies like Stripe and Twitter.
We're backed by Accel Ventures in SF. We’re looking for people who love working on complex technical solutions for creative makers and especially for engineers like us who like having a huge impact on product development.
You can email us at jobs@myxt.com and we'll get back to you right away. (No recruiters please.)
Tech stack: Typescript, Solid JS, Flutter, GraphQL, Hasura, ffmpeg, Firebase, PostgreSQL, Dart, and more
Myxt | SF and/or Remote (PST +- 6 hours) | Looking for Software Engineers | https://myxt.com
We’re an early team of 4 (maybe 5 when you read this) who are attempting to make a big music service. Myxt is building an application and suite for managing music files, workflows, listening, reviewing, payment, sharing, and annotation for digital creators and their collaborators and close-knit fans.
We're currently live on all platforms and release updates several times a week. Product development is communal and everyone in the company leads projects, tests releases, and engages with users and partners.
Previously among our team we started Google Reader and helped build the early success of companies like Stripe and Twitter.
We're backed by Accel Ventures in SF. We’re looking for people who love working on complex technical solutions for creative makers and especially for engineers like us who like having a huge impact on product development.
You can email us at jobs@myxt.com and we'll get back to you right away. (No recruiters please.)
Tech stack: Typescript, Solid JS, Flutter, GraphQL, Hasura, ffmpeg, Firebase, PostgreSQL, Dart, and more
Myxt | SF/Remote | Looking for Software Engineers | https://myxt.com
We’re a very small team attempting to make a big music service. Myxt is building an application and suite for managing music files, workflow, listening, reviewing, payment, sharing, and annotation for digital creators and their collaborators and close-knit fans.
We’re a small founding team (2 people) with a working product and we release updates several times a week. Product development is communal and everyone in the company leads projects, tests releases, and engages with users and partners.
Previously, among our team we started Google Reader and helped build the early success of companies like Stripe and Twitter.
We're backed by Accel Ventures in SF. We’re looking for people who love working on complex technical solutions for creative makers. We’ve built the first version of the application but we’re still very early in its lifecycle and so we’re looking for engineers like us who like having a huge impact on product development.
Myxt | SF/Remote | Looking for Software Engineers | https://myxt.com
We’re a very small team attempting to make a big music service. Myxt is building an application and suite for managing music files, workflow, listening, reviewing, payment, sharing, and annotation for digital creators and their collaborators and close-knit fans.
We’re a small founding team (2 people) with a working product and we release updates several times a week. Product development is communal and everyone in the company leads projects, tests releases, and engages with users and partners.
Previously, among our team we started Google Reader and helped build the early success of companies like Stripe and Twitter.
We're backed by Accel Ventures in SF. We’re looking for people who love working on complex technical solutions for creative makers. We’ve built the first version of the application but we’re still very early in its lifecycle and so we’re looking for engineers like us who like having a huge impact on product development.
Actually, mehrdata, I think you might be reading a lot more into my statements than are actually present. While cultures evolve, I feel lucky we were able to make Reader within Google. I think that its being at Google made it a better product.
When asked if I would build it in today's Google my answer was "no" given that Google is clearly uninterested in this project at the moment. Seems kinda obvious, really.
I feel that epistasis more accurately guessed at the unpublished feelings I've had. The following are all things I think simultaneously right now...
Google is a great company
Google makes great things
Google is not interested in pursuing Reader
Communication around Reader's value (or how to improve it) within Google was unclear
There may be confusion for inventor-types within Google on how to proceed in today's Google, though that's possibly remedied by better communication internally
I'm glad you liked Reader. No need to guess about my actual thoughts about the past since I can summarize: Thanks to a great company with great people, Google Reader was made into a service that was many times better than I ever could have built alone in my apartment. There's no way to know if that success could have been achieved somewhere else. Everyone working on Reader knew it could have been cancelled at any time. It wasn't cancelled for a long time. I'm glad we got to experiment with the idea and the experience.
Thanks for your reply. I'm glad you cleared this up. I'm sorry if I read too much through your statements.
The last feeling you mentioned is totally aligned with I was trying to say: to emphasize if you are an inventor type, you'd want to evaluate the risk of serving at the pleasure of the king carefully; it isn't necessarily a bad value proposition, but it certainly carries the risk of getting derailed or axed. Same goes for people who sell their companies to others; you cannot expect them to move forward with your initial vision.
Wait. When asked if you would build it in Today's Google, your answer would be no, because Google is clearly uninterested in this project at the moment. :). I mean really, if Google is uninterested, it's Google who effectively said No isn't it?
Er, no. At the risk of getting all Primer on this, the hypothetical situation posed allowed for a history where Reader was never invented but somehow magically I retained the knowledge of how Google would have evolved in the (hypothetical-to-them) event Reader had been launched there.
Given that knowledge, I certainly wouldn't choose to build it in today's Google given I'd be armed with data suggesting it would not be supported. This point, while kind of mindless and diverting, doesn't seem very useful, though.
Actually, there's a bunch of causality minefields here; we should both be concerned that we could inadvertently violate Novikov's self-consistency principle. My conclusion is for us to back away slowly from the thread – I don't want either of us to accidentally become our own grandfathers.
Small correction: Actually, I've long asserted that Google's infrastructure and talent are key reasons that Reader was successful. I think that neither in the interview, nor the article, did I suggest that – though I could be mistaken.
Previously among our team we started Google Reader and helped build the early success of companies like Stripe and Twitter.
We're backed by Accel Ventures in SF. We’re looking for people who love working on complex technical solutions for creative makers and especially for engineers like us who like having a huge impact on product development.
You can email us at jobs@myxt.com and we'll get back to you right away. (No recruiters please.)
Tech stack: Typescript, Solid JS, Flutter, GraphQL, Hasura, ffmpeg, Firebase, PostgreSQL, Dart, and more